Coordinate Codex threads as a named team with durable on-disk state.
npx skills add https://github.com/code-yeongyu/lazycodex --skill teammode
Please help me install this Agent Skill. Skill: teammode Source: https://github.com/code-yeongyu/lazycodex/tree/main/plugins/omo/components/teammode/skills/teammode Command: npx skills add https://github.com/code-yeongyu/lazycodex --skill teammode
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.
Initialize a team with the team.mjs CLI, then add members and bind threads to begin coordinated work.
High-intent search queries and answers about installing and using this skill.
You can coordinate parallel Codex threads by initializing a named team where the main session acts as the leader and members are assigned concrete ownership areas. The team state is managed durably on disk.
Use a team of agents when work is not perfectly isolated but parallelizing helps, or when a task needs exploration under a clear goal. Use plain subagents when scope is perfectly isolated or the goal is ambiguous.
Durable state management for Codex orchestration persists team data on disk using atomic writes to team.json and guide.md. This maintains per-member focus, lens, and deliverables across sessions.
Yes, you can bind a thread to a team member using the bind-thread lifecycle operation. Members must be defined by a concrete part or ownership area rather than a vague job role.
You can archive or delete a team using the script-managed team lifecycle operations. The bundled cross-platform script enforces these actions with atomic persistence to ensure clean state removal.
Yes, team orchestration supports per-member worktrees. The durable on-disk state tracks these worktrees alongside per-member focus and lens data within the team.json file.
KangJiSseokAllocate iBank team members into tb_user_team and tb_team_admin tables.
lpjhelderCoordinate multiple workers on a shared task list via tmux-based orchestration.
jokken79Dispatch independent debugging tasks to separate agents for parallel execution.
YeaChan05Coordinate OMX agents in a tmux-based shared task environment.
