Coding agent

Send Codex a complete ticket. Get back a reviewable result.

Keep the brief, progress, pull request, cost, checks, and review on the card that requested the work.

Codex with Aestus

Keep the tool. Change what the team can see.

Each Codex session starts with the Workspace Memory brief and relevant cited claims available to that session. Personal, team, workspace, and organization claims keep their audience rules. At handoff, it can propose what it learned for human review.

Codex starts with a ticket that names the result and the proof needed for acceptance. It can inspect artifacts, report changed progress, and attach the pull request without copying status through chat. The card shows which coding runtime produced the run.

The current Codex adapter cannot stop inside a run for a native Aestus approval. Backend selection rejects Codex when policy requires that pause and asks for Aestus, Claude Code, or Pi instead. The page does not present an unsupported approval as completed.

An admin requirements file constrains Codex from the host it starts on, so its strength ends at whoever owns that host. Aestus Sandboxes puts the host under the organization instead: gateway mode keeps brokered keys outside the session, developer-subscription sign-in stays inside the encrypted snapshot, only named destinations answer a network call, and each refusal is written against the session for later reading.

Good first workflows

Add contract coverage
Ask for a small fixture-backed change and keep its proof with the pull request.
Refactor a stable interface
Name the behavior that cannot move, then review the patch against that boundary.
Prepare a review batch
Let Codex produce the patch while Aestus keeps review and merge as separate steps.

A complete Codex example, from trigger to proof.

The example names the people, task event, tool boundary, returned evidence, and acceptance state. The run row below it is a fixed product example, not customer data.

Example — fictional team and data. Not a live run or customer result.

Inside the connected tool

What the handoff looks like in Codex

Codex connects to the Aestus MCP server, opens the assigned card, and keeps each changed phase visible.

Example — fictional team and data. Not a live run or customer result.

Developer terminal

Live

codex
sandbox ready · policy "Engineering default" v7 · egress restricted
CodexReading src/billing/invoice.ts
CodexEdit src/billing/invoice.ts
Blocked by policy: api.unknown-host.dev
CodexRan tests · 41 passed

Example — fictional team and data. Not a live run or customer result.

Concrete workflow example

Tighten an audit export and return a reviewable patch

The evidence export must include the active policy hash without changing its stable column order.

TriggerAES-517 is assigned to Codex

1
Noah · Security
Defines the export contract on the card
Adds one fixture, the required policy hash, and the no-reorder constraint.
contract v3 · fixture attached
2
Codex
Claims the card and updates changed phases
Inspects the serializer and posts progress only when work moves to a new phase.
claim · progress: testing
3
Codex
Attaches the patch and verification result
The pull request includes the new fixture and the unchanged-column-order proof.
PR #203 · export suite passed
4
Noah · Security
Reviews and accepts the evidence change
Review remains a separate governed decision because this adapter cannot pause mid-run.
accepted · no native pause used

Example — fictional team and data. Not a live run or customer result.

Deterministic product example — not a production run

Tighten the run ledger test

Example run		Runtime	Outcome
EXAMPLE-CX-01	Codex	codex	Completed	$0.01	42.0s

Tokens in / out: 4,800 / 300
Failure code: —
Agent: coding-agent

Example source: lib/marketing/integration-run-examples.ts

Example run cost

$0.0140 in the deterministic product example

The complete checked-in example defines 4,800 input tokens, 300 output tokens, and a 42-second duration for this illustrative run. Your ledger replaces these values at runtime.

Set it up in four steps.

Follow the real Codex connection path. Provider steps link to the provider documentation. Aestus steps name the contract they follow.

01
Register the Aestus server
Add the hosted Streamable HTTP endpoint to the Codex MCP list.
codex mcp add aestus --url https://aestus.app/api/mcpRead the provider docs
02
Sign in to Aestus
Start the OAuth login for the saved server and approve the requested connection.
codex mcp login aestusRead the provider docs
03
Claim a card and return a result
Open the ticket with its artifacts, recall workspace context, and claim it before the first edit. Keep presence current, attach the pull request, add the final handoff, and move the card to review.
Aestus contract: docs/agent-ticket-workflow.md
04
Run it governed in early access
Aestus provides the sandbox CLI and setup path during early-access onboarding. It starts Codex remotely while your terminal stays local.
Aestus contract: docs/runbooks/aestus-cli.md

The boundary stays visible while the work moves.

See what Codex can do, where a person still decides, and what Aestus records for every governed run.

Where control lives

Measured capability limit

The current Codex adapter does not support native in-run approval pauses.

Unsupported work is rejected

Backend selection rejects Codex for approval-required work. Select Aestus, Claude Code, or Pi instead.

Review remains governed

Card transitions, pull request review, merge policy, evidence, and acceptance still stay under Aestus control.

What Aestus records

Model usage

Token counts and the resulting run cost remain visible beside the work.

Elapsed work

Wall-clock latency shows the total time from launch to terminal state.

Failure contract

Provider, sandbox, budget, check, and review failures use stable codes instead of free-form guesses.

Questions teams ask

Can Codex connect through MCP?

Yes. Codex can register the Aestus remote MCP endpoint and complete its OAuth flow.

Does Codex support Aestus approval pauses?

Not in the current adapter. Backend selection rejects Codex for approval-required work and asks you to select Aestus, Claude Code, or Pi.

Where does Codex run with Aestus Sandboxes?

For teams in early access, it runs on a remote machine your organization defines while the terminal stays on the desk. Review and merge stay separate governed workflow steps.

See all integrations See the security controls

Start with one Codex run.

Bring one real run. Map its actors, boundary, evidence, cost, and acceptance step.

Talk to us

Example — fictional team and data. Not a live run or customer result.

Concrete workflow example

Tighten an audit export and return a reviewable patch

The evidence export must include the active policy hash without changing its stable column order.

TriggerAES-517 is assigned to Codex

1
Noah · Security
Defines the export contract on the card
Adds one fixture, the required policy hash, and the no-reorder constraint.
contract v3 · fixture attached
2
Codex
Claims the card and updates changed phases
Inspects the serializer and posts progress only when work moves to a new phase.
claim · progress: testing
3
Codex
Attaches the patch and verification result
The pull request includes the new fixture and the unchanged-column-order proof.
PR #203 · export suite passed
4
Noah · Security
Reviews and accepts the evidence change
Review remains a separate governed decision because this adapter cannot pause mid-run.
accepted · no native pause used

Example run

Runtime

Outcome

EXAMPLE-CX-01

Codex

codex

Completed

$0.01

42.0s

Questions teams ask

Can Codex connect through MCP?

Yes. Codex can register the Aestus remote MCP endpoint and complete its OAuth flow.

Does Codex support Aestus approval pauses?

Not in the current adapter. Backend selection rejects Codex for approval-required work and asks you to select Aestus, Claude Code, or Pi.

Where does Codex run with Aestus Sandboxes?

For teams in early access, it runs on a remote machine your organization defines while the terminal stays on the desk. Review and merge stay separate governed workflow steps.

Send Codex a complete ticket. Get back a reviewable result.