Teammode

Run a named team of cooperating Codex threads under one leader, with durable state on disk. This is a Codex-only workflow. It is inspired by the lifecycle concerns in the Yeachan-Heo/oh-my-codex team skill, but it does not copy that runtime model and never depends on an external terminal runner - it coordinates through Codex's own thread tools plus a bundled state script.

When to use a team (and when to use plain subagents instead)

Use a TEAM when EITHER holds:

• the work does NOT split into perfectly isolated pieces, but doing it in parallel is clearly more convenient - members will need to see and react to each other's findings; or
• one task still needs exploration, yet its GOAL is already clear - parallel investigation under a fixed objective.

Use plain subagents ($ulw / multi_agent_v1.spawn_agent) - NOT a team - when EITHER holds:

• the work IS perfectly isolated, so there is no coordination cost worth paying; or
• the GOAL is still ambiguous, where one mind should resolve direction before any fan-out.