codex-cli 0.3.4 published WASM uses outdated socket ABI constants

[WellDunDun]

Summary

@agentos-software/codex-cli@0.3.4 fails to connect to ChatGPT when used with @rivet-dev/agentos@0.2.20 / @rivet-dev/agentos-core@0.2.20. The published codex-exec WASM artifact passes Linux socket constants to the current host_net WASI ABI.

Environment

• macOS arm64, Node 25.8.1
• AgentOS / core 0.2.20, Codex CLI package 0.3.4
• Actor server/client session flow; also reproduced in a separate core VM session
• Valid ChatGPT device-login credentials, no API key
• ACP adapter from repository revision 0f2c8319f802dd31d43645eed88198522b8dc82a (software/codex/src/adapter.ts), because the separately published CLI artifact does not register an agent

Reproduction

1. Install the versions above and the repository's Codex ACP adapter.
2. Make the package executable and its directories traversable by the guest user. Supply a dedicated, guest-readable Codex home containing valid ChatGPT login credentials.
3. Set forced_login_method = "chatgpt" and cli_auth_credentials_store = "file" in that home's config.
4. Open a Codex session and send a simple prompt.

Session creation succeeds, but the prompt fails:

stream disconnected before completion: socket error: connect(chatgpt.com:443) failed: errno 23

The runtime's errno 23 is EHOSTUNREACH. Host HTTPS, guest JavaScript HTTPS, and guest IPv4 DNS/TCP tests succeed. A fresh actor reproduces the same error.

Artifact evidence

SHA-256 of the extracted, unmodified bin/codex-exec:

fd3c6ce268e7c952dedc1aa7df637bc26d1a2b2c7a9180130bed8cf99d86b993

Disassembly immediately before call 9 <host_net.net_socket>:

10e29c: i32.const 2
10e29e: i32.const 1
10e2a0: i32.const 0
10e2a2: local.get 2
10e2a4: i32.const 48
10e2a6: i32.add
10e2a7: call 9 <host_net.net_socket>

Current repository toolchain/crates/libs/wasi-http/src/lib.rs uses AF_INET=1 and SOCK_STREAM=6. The runner's HOST_NET_AF_INET=1, HOST_NET_AF_INET6=2, and HOST_NET_SOCK_STREAM=6 agree. The published artifact still passes 2,1.

Confirmation

For diagnosis only, I verified the hash and instruction bytes, then changed the two constants to 1,6 without changing credentials, endpoint, runtime, or adapter. Two actor server/client prompts returned the requested response using the ChatGPT subscription. This is not proposed as a shipping binary patch.

Could you rebuild/publish the Codex CLI artifact from the corrected source and add an artifact-level network smoke test? It looks like the source correction exists but has not reached this published binary. I can provide a PR if the release/build path needs a change.

[WellDunDun]

A clean documented-example reproduction exposes an earlier packaging problem, separate from the WASM ABI report above.

Fresh install, no overrides, postinstall patches, custom adapters, source-built executables, or modified runtime:

• @rivet-dev/agentos@0.2.20 (its own rivetkit@2.3.10)
• @agentos-software/codex@0.2.7 (re-exports @agentos-software/codex-cli@0.3.3)
• macOS arm64, Node 25.8.1
• server copied byte-for-byte from examples/codex/server.ts at 0f2c8319f802dd31d43645eed88198522b8dc82a
• published engine on isolated loopback ports

The documented sessions.open({ agent: "codex" }) fails before authentication:

unknown agent type "codex": no projected /opt/agentos/pkgs/codex package with an agent.acpEntrypoint — pass its package to AgentOs software

The installed @agentos-software/codex/dist/index.js only re-exports the CLI descriptor. Its manifest contains registry metadata but no agent entrypoint. Is there a published package/version intended for the current Codex agent quickstart? We are not treating our custom adapter/build as the supported integration.

For comparison, the unchanged published Claude example returns real subscription responses when provided the documented ANTHROPIC_AUTH_TOKEN session environment option. A saved .credentials.json alone returned “Not logged in.”