Skip to main content
Codex reads AGENTS.md from the project, and cordango new writes one with the same content as CLAUDE.md. There’s nothing to configure.
1

Create the workspace

2

Start Codex in it

​
Sandbox settings

A Cordango workspace is a good fit for workspace-write. The whole authoring loop writes only inside the workspace, and the parts that reach the network are the four connected commands, which you’ll want to approve anyway.
That leaves cordango publish and cordango login asking before they touch an instance, which is the right default for a command that changes what a real workspace is running.

​
Starting prompt

​
Starting from nothing

​
Non-interactive runs

codex exec runs a prompt without the TUI, which makes the check loop scriptable:
Keep an exec prompt read-only unless you have a reason not to. An agent editing files with nobody watching is a fine way to find out that the aggregate you scoped it to was the wrong one.

​
Nested instructions

Codex reads AGENTS.md from subdirectories as well as the root. That’s useful in a workspace with several apps: a per-app apps/support/AGENTS.md can carry the business rules that only apply to that app, while the generated root file keeps carrying the Cordango workflow. Don’t restate the workflow in a nested file. Add to it.