Codex
Public Made by Adomby adom
Codex in Adom Hydrogen: ecosystem setup, dock dashboard and live engineering demos.
9fee13e
27d ago
Codex Bridge 0.1.2 candidate: crr setup regression checks
Date: 2026-09-08. Issue: adom/codex #1.
Target and boundaries
- User-selected crr resolved to
ConfRoomROG, Windows, AB 2.1.78. - Calls used
--target ConfRoomROG --ai-thread codex-crr-fixes; responses identified peerConfRoomROGover the mesh. - No Codex Desktop package, Codex processes, native auth cache or Codex bridge existed before this test. Existing unrelated apps and bridges were preserved.
- arav-rog is being used by Caleb. No calls were sent to it.
Changes and verification
- Explicit agreement acceptance now supplies both
--accept-source-agreementsand--accept-package-agreements. Without consent, neither is supplied. - WinGet remains noninteractive and selects the exact official Store ID
9PLM9XGG6VKS, not a name search. - Installer results include program and exact args, even on spawn failure. Post-install inventory failures retain installer diagnostics and advise checking status before retrying. Unrelated failures no longer masquerade as consent gates.
- Launch issues one activation and retries observations after transient inventory failures. It retains diagnostics and never reports success without a window.
- 19 Linux tests passed (18 unit plus one HTTP integration test).
- 17 Windows unit tests passed natively on crr, including synthetic launch polling recovery, Store argument construction, Windows credential ACL/preservation, native RPC correlation, redaction and UAC guidance. The temporary test executable was removed afterward.
- Linux and Windows-target Clippy passed with warnings denied; Windows x64 release cross-build passed.
- AB discovered and ran the development-pinned candidate on crr, port 58496. Deployed executable and manifest hashes matched the local build.
Live install boundary
codex_desktop_install {} stopped at the actual Microsoft Store package-agreement
gate. Nested result was success:false, errorCode:blocked_on_user, WinGet exit
-1978335167; output named ChatGPT, publisher OpenAI and Store ID 9PLM9XGG6VKS.
The exact non-accepting argument list was returned. Desktop remained absent.
Agreement acceptance for crr is pending. No agreements were accepted and no auth cache was transferred. Successful installation, first launch/sign-in, actual desktop chat and plugin operations have NOT yet been retested on crr. Its Store source did not block this attempt; the unused-source agreement case is covered by argument tests and the issue reporter's evidence, not a fresh-source live test here.
The original desktop_inventory_failed launch report has not been reproduced on
crr. Recovery is regression-tested with injected transient failures; the original
PowerShell failure's cause remains unconfirmed. Keep issue #1 open for live follow-up.
Candidate provenance
Bridge version: 0.1.2, development candidate only. No public runtime release,
auto-update manifest or container package publication was performed.
SHA256:
codex-bridge.exe: d7e6d720fee0f78186adb5cc030546b3c58ed0fd4bc3824f58d05f9c61f8fc5b
bridge.json: 51c9a1efa98b28c0306ae1af4baa5d90dd4ffe6fddf2443724d340d7b8478176
codex-bridge-windows-x64.zip: b07bd40b6c2e56037f3c0af07ac072fb590c7f402bbb24a809d3b5aca8f509b2
# Codex Bridge 0.1.2 candidate: crr setup regression checks
Date: 2026-09-08. Issue: [adom/codex #1](https://wiki.adom.inc/adom/codex/issues/1).
## Target and boundaries
- User-selected crr resolved to `ConfRoomROG`, Windows, AB 2.1.78.
- Calls used `--target ConfRoomROG --ai-thread codex-crr-fixes`; responses
identified peer `ConfRoomROG` over the mesh.
- No Codex Desktop package, Codex processes, native auth cache or Codex bridge
existed before this test. Existing unrelated apps and bridges were preserved.
- arav-rog is being used by Caleb. No calls were sent to it.
## Changes and verification
- Explicit agreement acceptance now supplies both `--accept-source-agreements`
and `--accept-package-agreements`. Without consent, neither is supplied.
- WinGet remains noninteractive and selects the exact official Store ID
`9PLM9XGG6VKS`, not a name search.
- Installer results include program and exact args, even on spawn failure.
Post-install inventory failures retain installer diagnostics and advise checking
status before retrying. Unrelated failures no longer masquerade as consent gates.
- Launch issues one activation and retries observations after transient inventory
failures. It retains diagnostics and never reports success without a window.
- 19 Linux tests passed (18 unit plus one HTTP integration test).
- 17 Windows unit tests passed natively on crr, including synthetic launch polling
recovery, Store argument construction, Windows credential ACL/preservation,
native RPC correlation, redaction and UAC guidance. The temporary test executable
was removed afterward.
- Linux and Windows-target Clippy passed with warnings denied; Windows x64 release
cross-build passed.
- AB discovered and ran the development-pinned candidate on crr, port 58496.
Deployed executable and manifest hashes matched the local build.
## Live install boundary
`codex_desktop_install {}` stopped at the actual Microsoft Store package-agreement
gate. Nested result was `success:false`, `errorCode:blocked_on_user`, WinGet exit
`-1978335167`; output named ChatGPT, publisher OpenAI and Store ID `9PLM9XGG6VKS`.
The exact non-accepting argument list was returned. Desktop remained absent.
Agreement acceptance for crr is pending. No agreements were accepted and no auth
cache was transferred. Successful installation, first launch/sign-in, actual desktop
chat and plugin operations have NOT yet been retested on crr. Its Store source did
not block this attempt; the unused-source agreement case is covered by argument
tests and the issue reporter's evidence, not a fresh-source live test here.
The original `desktop_inventory_failed` launch report has not been reproduced on
crr. Recovery is regression-tested with injected transient failures; the original
PowerShell failure's cause remains unconfirmed. Keep issue #1 open for live follow-up.
## Candidate provenance
Bridge version: `0.1.2`, development candidate only. No public runtime release,
auto-update manifest or container package publication was performed.
SHA256:
```text
codex-bridge.exe: d7e6d720fee0f78186adb5cc030546b3c58ed0fd4bc3824f58d05f9c61f8fc5b
bridge.json: 51c9a1efa98b28c0306ae1af4baa5d90dd4ffe6fddf2443724d340d7b8478176
codex-bridge-windows-x64.zip: b07bd40b6c2e56037f3c0af07ac072fb590c7f402bbb24a809d3b5aca8f509b2
```