Julian lechnerandClaude Sonnet 5
e88d27ac43
Recorded why it is not configured: it does not appear in the current documented Codex schema, only in upstream issue titles describing an internal/experimental flag. [agents].enabled already covers enabling multi-agent tools; the schema's separate [features].multi_agent toggle would be redundant alongside it. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2.5 KiB
Configuration
Codex receives a generated global AGENTS.md, agent TOML files, skills, rule files, and a config.toml adapter with workspace sandboxing, interactive approval boundaries, automatic approval review, enabled sub-agents, and a five-thread concurrency limit (max_concurrent_threads_per_session, the current canonical key; the legacy max_threads alias is not emitted). Claude Code receives a generated global CLAUDE.md, agent Markdown files, skills, and settings.json with the auto permission mode, explicit Agent permission, and a five-operation tool/sub-agent concurrency limit. The exact installed locations are resolved from the user profile at install time; no machine-specific absolute path is stored in the repository.
Claude's rule loading differs from Codex's by design: general.md is the only rule shipped as a plain, always-applied file (its text is also embedded directly in CLAUDE.md). Every technology- or situation-specific rule in shared/rules/ is instead generated as a skill under skills/rules/, driven by adapters/claude/rule-skills.tsv (rule file, skill name, trigger description). Only a skill's name and description are ever permanently in context; Claude loads the full rule text only when it invokes the skill. Codex is unaffected — it keeps receiving every rule as a plain file and is told to load the matching one by path, exactly as before.
Codex's current configuration schema has no agents.max_depth or other agent-recursion-depth key. The only max_depth-shaped setting in the schema is network_proxy.glob_scan_max_depth, which bounds glob-pattern expansion for the network proxy feature and is unrelated to agents; Claude Code's settings likewise expose no comparable key. The repository does not emit either as an invented key.
[agents].enabled = true (set explicitly, matching its own documented default) is the current, documented way to enable Codex's multi-agent tools. A separate [features].multi_agent toggle exists in the schema but is not set here, since [agents].enabled already covers it and setting both would be redundant. multi_agent_v2 does not appear in the current documented schema at all — it surfaced only in upstream issue titles describing an internal/experimental flag — so it is deliberately not configured.
Client settings remain thin adapters. Shared semantics remain in shared/.
User plugins are managed separately through adapters/plugins.tsv and the client-native plugin commands. They are not copied into generated/ because each client owns its plugin cache and authentication state.