team

Coordinate multiple agents in tmux with shared task lists and synchronized execution.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill team-kyrie66nb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team
Source: https://github.com/KYRIE66nb/codex-omx-public-config/tree/main/home/.agents/skills/team
Command: npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill team-kyrie66nb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate multiple agent sessions on a shared task list using tmux-based orchestration to enable parallel work with consistent state and centralized control.

Core Features & Use Cases

  • Orchestrates parallel agent sessions inside a single terminal workspace with a leader that coordinates tasks.
  • Maintains per-agent inbox/state, heartbeat signals, and cleanup workflows to recover from pane or worker issues.
  • Supports safe start/shutdown lifecycles and pane-recovery procedures for reliable long-running tasks.

Quick Start

Start a tmux leader session and launch worker panes for each agent to begin coordinated task execution.

Frequently Asked Questions about team

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate multiple Claude agents to run in parallel on a shared task list?

You coordinate multiple Claude agents in parallel by using tmux-based orchestration to manage a shared task list. A leader session launches worker panes for each agent to execute tasks concurrently while maintaining synchronized state.

What is tmux-based agent orchestration and how does it manage parallel execution?

Tmux-based agent orchestration coordinates parallel execution by running multiple agent sessions inside a single terminal workspace. It maintains per-agent state tracking and heartbeat messaging to ensure synchronized execution and centralized control.

How do I recover from a tmux pane failure during long-running agent orchestration?

To recover from a tmux pane failure during agent orchestration, the system uses defined lifecycle procedures and cleanup workflows. These safe recovery mechanisms restore worker panes and resume long-running tasks without losing the shared state.

Can I use tmux to orchestrate Codex agents for long-running automated workflows?

Yes, you can use tmux to orchestrate Codex agents for long-running automated workflows. The system supports safe start and shutdown lifecycles, per-worker state tracking, and heartbeat signals to ensure reliable execution.

Does tmux orchestration support startup verification and safe cleanup for agent workers?

Tmux orchestration supports startup verification and safe cleanup through a defined lifecycle. It maintains per-worker inboxes and heartbeat messaging to verify active workers and execute safe shutdown procedures when tasks complete.

Why do parallel agent sessions need heartbeat signals and per-agent state tracking in tmux?

Parallel agent sessions need heartbeat signals and per-agent state tracking in tmux to prevent desynchronization and worker failures. These mechanisms ensure centralized control over the shared task list and enable reliable recovery from pane issues.