Codex sessions

Interactive Codex conversations support live steering, command approvals and model changes on subsequent turns. Selecting Astra after a Sol turn applies Astra to the next interactive turn while preserving the conversation. Build workflow phases and background completions use the noninteractive CLI path and do not offer live steering.

A Codex command approval shows Accept and Deny. Accept all appears only when Codex offers approval for the session. The displayed command is read-only because this provider cannot change it through the approval response. Stop cancels pending requests. Unsupported approval request types are rejected rather than silently approved.

When Codex asks to write files, the approval card shows the proposed change as a diff, with its reason and a warning when it asks for session-wide write access under a folder. A sandbox permission ask shows the folder and what it wants, and Accept grants exactly that. An ask whose diff never arrived is refused, never approved blind.

First-party memory and Planboard tools are bound to the selected project. Planboard writes run on the host. Workspace-write also grants the Git metadata paths needed to stage and commit in a checkout or managed worktree. Plan mode remains read-only.

If Codex reports already has an active writer, the error identifies the holder where available. Solenta uses private lock directories and can release a holder it identifies as its own; an outside owner must finish or close before retrying. The session is retained, worker notices wait, and a blind Retry loop is suppressed. Eject and Reclaim are the explicit controls for moving session ownership.

Astra and other image-capable Codex models receive images as native inputs. Spark is text-only: its attachment controls still accept files and folders, but reject images. Tool-result images are kept in the transcript. The context ring uses current usage separately from the session's cumulative token totals.