Context
Codex loads the root AGENTS.md that gantry init writes. An optional .codex/config.toml sets project defaults such as the sandbox and approval policy. Do not duplicate RULES or MANIFEST in it; AGENTS.md links them.
Session bootstrap
Codex does not scan project hook folders, so use the shell wrapper:
scripts/gxt-pin-mission.sh .gitagent/missions/MSN-0001.<slug>.yaml
scripts/gxt-shell-agent.sh codex .gitagent/missions/MSN-0001.<slug>.yamlHeadless or in CI:
gantry runtime exec --mission .gitagent/missions/MSN-0001.<slug>.yaml -- codex exec "<task>"How strongly it holds
The interactive TUI and IDE extension are advisory; wrapped with gantry runtime exec or gxt-shell-agent.sh, Codex runs at the process boundary. Codex’s own sandbox and approval settings govern Codex itself. They are separate from OpenGantry’s edit roots and forbidden zones (Enforcement boundary).
The steps every tool shares are on Wire any agent.