Individual skill
teammode
Codex-only team orchestration: run a named team of cooperating Codex workers with durable, script-managed state. MUST USE when the user asks Codex to create, run, coordinate, inspect, archive, or delete a team of agents/threads/sessions, or to work on something as a team in parallel. FIRST inspects the active tool surface (checking tool_search for deferred tools) and tells the user the route: native MultiAgentV2 agents (flat spawn_agent with task_name) when available, Codex App threads as the fallback, or a plain-subagent split when neither set exists. 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; 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.
plugins/omo/skills/teammode/SKILL.md
Source commit 49104cf38aa10f0a55aabf33aa675118d2873fc1
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 3, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 3,880
- Repository last updated
- Nov 5, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- ai-agents Repository topic
- claude Repository topic
- claude-code Repository topic
- cli Repository topic
- codex Repository topic
- developer-tools Repository topic
- lazy Repository topic
- oh-my-openagent Repository topic
- omo Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 21,216 bytesSKILL.mdcore · 21,216 bytesSKILL.mdcore · 21,216 bytesSKILL.mdcore · 21,216 bytesSKILL.mdcore · 21,216 bytesSKILL.mdcore · 21,216 bytesSKILL.mdcore · 21,216 bytesSKILL.mdcore · 21,216 bytesSKILL.mdcore · 21,216 bytesSKILL.mdcore · 21,216 bytesSKILL.mdcore · 21,216 bytesSKILL.mdcore · 21,216 bytesSKILL.mdcore · 21,216 bytesagents/openai.yamlasset · 43 bytesscripts/team-guide.mjsruns · 11,357 bytesscripts/team-state.mjsruns · 18,969 bytesscripts/team-transport.mjsruns · 2,251 bytesscripts/team-worktree.mjsruns · 4,860 bytesscripts/team.mjsruns · 15,681 bytes
Read excerpt
# Teammode
Run a named team of cooperating Codex workers under one leader, with durable state on disk.
This is a Codex-only workflow. It never depends on an external terminal runner - it
coordinates through Codex's own collaboration tools plus a bundled state script, on ONE of
two transports chosen up front: native MultiAgentV2 agents, or Codex App threads as the
fallback.
## 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