claude-code-orchestra
AGENTS.md199 starsChanged 2 months agoMITView on GitHub
This file is the Codex-specific adapter. The common CLI-agent contract (response structure, handoff rules, cross-CLI subagent invocation, and the completion-verification guardrails) is the root AGENTS.md, which Codex loads automatically. Read that first. Codex operates as Tier 2 (sol) in the agent hierarchy. See .claude/rules/tiers.md for the full tier definitions. Source of truth: .codex/config.toml approval_policy is "never" and sandbox_mode is "danger-full-access", so Codex runs unattended with unrestricted filesystem and network access and no confirmation prompts. Callers doing analysis, review, or planning…
In this repository17 other files it gives its agents.
- .agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- catchupSkill
- checkpointingSkill
- codex-systemSkill
- context-loaderSkill
- design-trackerSkill
- featureSkill
- initSkill
- planSkill
- research-libSkill
- simplifySkill
- spikeSkill
- tddSkill
- team-executeSkill
- troubleshootSkill
- update-lib-docsSkill
The file
Files
AGENTS.md -- Codex Adapter
This file is the Codex-specific adapter. The common CLI-agent contract
(response structure, handoff rules, cross-CLI subagent invocation, and the
completion-verification guardrails) is the root AGENTS.md, which Codex
loads automatically. Read that first.
Codex operates as Tier 2 (sol) in the agent hierarchy. See
.claude/rules/tiers.md for the full tier definitions.
Model Configuration
Source of truth: .codex/config.toml
| Key | Value |
model | gpt-5.6-sol |
model_reasoning_effort | xhigh |
approval_policy | never |
sandbox_mode | danger-full-access |
Sandbox Discipline
approval_policy is "never" and sandbox_mode is "danger-full-access", so
Codex runs unattended with unrestricted filesystem and network access and no
confirmation prompts. Callers doing analysis, review, or planning should still
pass an explicit --sandbox read-only to avoid accidental writes during those
tasks. Completion verification (Sol Guardrails, root AGENTS.md section
"Guardrails (Completion Verification)") remains mandatory regardless of sandbox
mode.
Enabled Codex Skills
Skills are enabled by [[skills.config]] entries in .codex/config.toml that
point directly at the canonical implementations under .claude/skills/.
Nothing is copied into .codex/.
| Skill | Path |
context-loader | .claude/skills/context-loader |
design-tracker | .claude/skills/design-tracker |
Internal Context References
Codex may reference the following project paths as needed:
.claude/docs/DESIGN.md-- macro requirements and design decisions.claude/docs/research/-- research notes and findings.claude/rules/-- coding standards and delegation rules.claude/STATE.md-- active main agent and cross-session working state.claude/logs/cli-tools.jsonl-- Codex call history log
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.