codex-subagent-router/skills/codex-subagent-router/references/platforms.md

Runtime and Configuration

Use this reference for actual host/configuration diagnosis. This is not a prerequisite checklist for every task.

Separate four kinds of evidence

1. Official model documentation: product and API capabilities.
2. Local configuration: requested defaults, providers and role bindings.
3. Current child-tool schema: what this session accepts.
4. Tool results: what was created, observed, completed or interrupted.

Do not substitute one for another. A model available in an API or the task picker may be absent from child tools. A CLI success does not verify a Desktop child path.

Inspect only relevant configuration fields; never dump environment blocks, credential files or HTTP authorization headers. Resolve CODEX_HOME from the environment, falling back to the user's .codex directory; do not overwrite that environment variable.

Optional Codex defaults

For clients that support the documented keys, an example is:

# Example only; merge intentionally into the existing configuration.
model = "gpt-5.6-sol"
model_reasoning_effort = "medium"

[agents]
default_subagent_model = "gpt-5.6-terra"
default_subagent_reasoning_effort = "medium"
max_concurrent_threads_per_session = 3

This is not an automatic router, permission grant or universal host configuration. Never overwrite an existing config to install this example. Preserve user model/provider choices and verify the actual client accepts the keys. Per-agent configuration and host overrides may change resolution.

The official Codex configuration describes the child-thread limit as excluding the parent. A collaboration tool may expose a different active-slot count including the parent. Use that live tool's counting and release semantics; do not copy either number blindly.

When selecting a route, explicitly request model and effort with a compatible fork mode if supported. Check omitted-setting inheritance, custom-agent bindings and override restrictions. A prompt cannot implement an unsupported model switch.

Diagnosis and safe fallbacks

Resolve the executable actually used by the relevant client, inspect its help/schema and record its version when needed. Do not prescribe speculative CLI flags or launch model calls merely to print a marker. Use an authorized real task to verify child execution.

Missing role/sandbox/timeout fields mean working role, read-only scope and deadlines are contract limits only. Keep requested and observed identity distinct. A completed task with unknown model identity can be accepted for its output, but cannot satisfy an explicit identity-verification gate.

No close tool: retain the truthful idle/completed/interrupted state and follow the host's actual capacity behavior. No child tools: continue locally; do not launch another user-owned task or nested CLI as an unapproved substitute.

Configuration changes may require a fresh session or explicit reload. Writing a file is not evidence that the current session adopted it.

Sources

Checked 2026-09-14: Codex subagents, OpenAI model catalog. Recheck changed product/API facts before altering real configuration.