Seed standalone Codex container defaults #723

New issue

Closed

opened 2026-07-24 19:17:25 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-24 19:17:25 +00:00

Owner

Problem

aos --role <role> acompose -- codex projects the selected persona into an ephemeral HOME but does not write the container-boundary Codex defaults that Ward supplies. Codex can therefore treat the mounted /workspace/<repo> as untrusted and prompt for permissions inside a Docker boundary that AOS already controls.

Change

Write an ephemeral Codex config.toml only for the Codex layout.
Mark the exact mounted workspace path as trusted.
Set approval_policy = "never" and sandbox_mode = "danger-full-access" because the AOS container is the security boundary.
Preserve AOS's model-opaque contract. Do not copy Ward's model, reasoning-effort, or verbosity tuning.
Preserve harness-specific isolation. Other layouts receive no Codex config.
Document the defaults and cover escaping plus workspace-path behavior with focused tests.

Acceptance

A Codex AOS launch sees /home/aos/.codex/config.toml with the three container-boundary defaults.
The generated TOML safely quotes the mounted workspace path.
Claude, Goose, and OpenCode layouts remain unchanged.
Focused AOS tests and applicable repository validation pass.

## Problem `aos --role <role> acompose -- codex` projects the selected persona into an ephemeral HOME but does not write the container-boundary Codex defaults that Ward supplies. Codex can therefore treat the mounted `/workspace/<repo>` as untrusted and prompt for permissions inside a Docker boundary that AOS already controls. ## Change * Write an ephemeral Codex `config.toml` only for the Codex layout. * Mark the exact mounted workspace path as trusted. * Set `approval_policy = "never"` and `sandbox_mode = "danger-full-access"` because the AOS container is the security boundary. * Preserve AOS's model-opaque contract. Do not copy Ward's model, reasoning-effort, or verbosity tuning. * Preserve harness-specific isolation. Other layouts receive no Codex config. * Document the defaults and cover escaping plus workspace-path behavior with focused tests. ## Acceptance * A Codex AOS launch sees `/home/aos/.codex/config.toml` with the three container-boundary defaults. * The generated TOML safely quotes the mounted workspace path. * Claude, Goose, and OpenCode layouts remain unchanged. * Focused AOS tests and applicable repository validation pass.

coilyco-ops referenced this issue from a commit

2026-07-24 19:30:58 +00:00

feat: seed Codex container defaults

coilyco-ops closed this issue

2026-07-24 19:30:58 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilyco-flight-deck/agentic-os#723

No description provided.

Rows
Columns