teammode

What problem does it solve?

Codex-only team orchestration: run a named team of cooperating Codex threads with durable, script-managed state. MUST USE when the user asks Codex to create, run, coordinate, inspect, archive, or delete a team of threads/sessions, or to work on something as a team in parallel. The main session is always the leader; members are defined by a concrete part, ownership area, or perspective - never a vague job role; a bundled cross-platform script writes the .omo/teams state plus an auto-generated member field manual. Use a team when the work is not perfectly isolated but parallelizing helps, or when a task still needs exploration under a clear goal; use plain subagents when scope is perfectly isolated or the goal is ambiguous. Triggers: team mode, teammode, make a team, run as a team, team of agents, coordinate threads, parallel Codex threads, archive the team, delete the team.

Core Features & Use Cases

• Create and manage named teams of Codex threads with a single leader.
• Maintain durable on-disk state for teams, including per-member focus, lens, and deliverables.
• Support lifecycle operations: init, add-member, bind-thread, archive, and delete with atomic persistence of team.json and guide.md.

Quick Start

Initialize a team with the team.mjs CLI, then add members and bind threads to begin coordinated work.