# Teammode

Codex-only team orchestration: run a named team of cooperating Codex workers with...

- Repository: https://github.com/code-yeongyu/oh-my-openagent (70577 stars)
- Category: AI and agents
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add code-yeongyu/oh-my-openagent --skill teammode -g -a claude-code -y`
Codex: `npx skills add code-yeongyu/oh-my-openagent --skill teammode -g -a codex -y`
Cursor: `npx skills add code-yeongyu/oh-my-openagent --skill teammode -g -a cursor -y`
Gemini CLI: `npx skills add code-yeongyu/oh-my-openagent --skill teammode -g -a gemini-cli -y`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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
  a fixed objective.

Use plain fire-and-forget subagents (`$ulw` / one-off `spawn_agent` workers) - 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.

A team buys cross-member coordination at a real overhead cost; only spend it when coordination
is the thing you actually need.

## Pick the transport FIRST - then tell the user

Before creating any team state, decide which transport this session can run.
Inspect your active tool list and select:

The rest: https://github.com/code-yeongyu/oh-my-openagent/blob/HEAD/packages/omo-codex/plugin/components/teammode/skills/teammode/SKILL.md