Stage usable Codex auth for standalone acompose inference #900

New issue

Closed

opened 2026-08-05 18:32:39 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-05 18:32:39 +00:00

Member

Outcome

Make a standalone AOS acompose launch either stage usable Codex authentication or fail before launching the harness with a clear authentication diagnostic.

Observed on 2026-08-05

The earlier composition-path failure is fixed. This invocation now composes and verifies the role bundle, starts the container, and launches Codex in the selected workspace:

aos --role content --agent codex --auth acompose -- codex exec --ephemeral --sandbox read-only -

Codex then fails before inference on both WebSocket and HTTPS requests to api.openai.com/v1/responses:

401 Unauthorized: Missing bearer or basic authentication

No Ward surface is in this execution path because the launch does not use --warded. The failure is therefore at the AOS-owned standalone harness-auth or model-transport boundary.

Existing contracts

#652 established read-only Codex auth staging into ephemeral composed HOME.
#725 says acompose-checkin stages known Codex auth through the normal AOS path.
#899 verifies composition and harness startup with codex --version, which does not exercise authenticated inference.

Required behavior

When --auth=true selects Codex, resolve the currently supported host credential source and stage it read-only into the ephemeral harness HOME.
If AOS cannot find or stage usable credentials, fail clearly before Codex reaches the model endpoint.
Keep --auth=false available for deliberate unauthenticated commands such as version checks.
Never print credential material, authorization headers, or auth-file contents.
Keep this fix in AOS. Do not add a Ward dependency to the standalone path.

Acceptance

A test with synthetic Codex auth proves host discovery, read-only container projection, ephemeral HOME staging, and safe file permissions.
Missing, unreadable, or unsupported auth fails with a specific pre-launch diagnostic.
Existing unauthenticated smoke and version paths remain supported with --auth=false.
A public-safe standalone codex exec probe reaches inference successfully through the supported AOS command.
Documentation distinguishes harness startup from authenticated inference.
Repository validation passes through declared Ward verbs.

## Outcome Make a standalone AOS `acompose` launch either stage usable Codex authentication or fail before launching the harness with a clear authentication diagnostic. ## Observed on 2026-08-05 The earlier composition-path failure is fixed. This invocation now composes and verifies the role bundle, starts the container, and launches Codex in the selected workspace: ```text aos --role content --agent codex --auth acompose -- codex exec --ephemeral --sandbox read-only - ``` Codex then fails before inference on both WebSocket and HTTPS requests to `api.openai.com/v1/responses`: ```text 401 Unauthorized: Missing bearer or basic authentication ``` No Ward surface is in this execution path because the launch does not use `--warded`. The failure is therefore at the AOS-owned standalone harness-auth or model-transport boundary. ## Existing contracts * #652 established read-only Codex auth staging into ephemeral composed HOME. * #725 says `acompose-checkin` stages known Codex auth through the normal AOS path. * #899 verifies composition and harness startup with `codex --version`, which does not exercise authenticated inference. ## Required behavior * When `--auth=true` selects Codex, resolve the currently supported host credential source and stage it read-only into the ephemeral harness HOME. * If AOS cannot find or stage usable credentials, fail clearly before Codex reaches the model endpoint. * Keep `--auth=false` available for deliberate unauthenticated commands such as version checks. * Never print credential material, authorization headers, or auth-file contents. * Keep this fix in AOS. Do not add a Ward dependency to the standalone path. ## Acceptance * A test with synthetic Codex auth proves host discovery, read-only container projection, ephemeral HOME staging, and safe file permissions. * Missing, unreadable, or unsupported auth fails with a specific pre-launch diagnostic. * Existing unauthenticated smoke and version paths remain supported with `--auth=false`. * A public-safe standalone `codex exec` probe reaches inference successfully through the supported AOS command. * Documentation distinguishes harness startup from authenticated inference. * Repository validation passes through declared Ward verbs.

coilyco-ops added the

autonomy

live-collab

priority

labels

2026-08-05 18:32:46 +00:00

coilyco-ops referenced this issue from a commit

2026-08-05 18:52:10 +00:00

fix(aos): fail closed on unusable Codex auth, closes #900

coilyco-ops referenced this issue from a commit

2026-08-05 19:09:50 +00:00

fix(aos): project Codex auth from macOS Keychain, closes #900