team

Coordinate multiple OMX task workers across tmux-backed sessions.

Updated Apr 23, 2026

Search Tags:#orchestration #tmux #parallel #lifecycle #workers #team #omx

Ready to run

npx skills add https://github.com/wmasfoe/notch-pet --skill team-wmasfoe

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: team
Source: https://github.com/wmasfoe/notch-pet/tree/main/.codex/skills/team
Command: npx skills add https://github.com/wmasfoe/notch-pet --skill team-wmasfoe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates multi-agent OMX workflows by orchestrating Codex and Claude workers in a tmux-backed team runtime, providing durable state, structured inbox/mailbox communication, and lifecycle management across multiple panes.

Core Features & Use Cases

Orchestrates multiple worker sessions in split tmux panes for parallel OMX tasks.
Manages team state, worker identities, inbox/outbox messaging, and task lifecycles via the .omx/state/team directory.
Enables repeatable startup, monitoring, and cleanup of coordinated teams in complex environments.

Quick Start

Launch a coordinated OMX team with the omx team command and monitor the resulting leader and worker panes.

Frequently Asked Questions about team

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

FAQPage Schema

How do I coordinate multiple parallel agents in tmux for OMX tasks?▼

Parallel agent execution in tmux is managed by launching durable worker processes across split panes with the omx team command, which handles startup, shared state, and mailbox communication for reliable OMX task coordination.

How does mailbox communication work for tmux-backed parallel workers?▼

Mailbox communication provides structured inbox and outbox messaging between leader and worker agents, persisting team state and worker identities within the .omx/state/team directory to coordinate task lifecycles and track progress reliably.

Do I need tmux installed to run parallel OMX worker sessions?▼

Yes, tmux is required because it provides the durable split panes necessary to launch, monitor, and coordinate multiple worker sessions for scalable parallel execution of OMX tasks.

What is the best way to manage agent lifecycle and cleanup for parallel tasks?▼

Managing agent lifecycle reliably requires enforcing a defined state protocol with API-based mutations, ensuring repeatable startup, progress tracking, and automated cleanup of coordinated teams in complex execution environments.

Can I orchestrate both Codex and Claude workers in the same tmux team runtime?▼

Yes, you can orchestrate both Codex and Claude workers simultaneously in the tmux-backed team runtime, coordinating their multi-agent OMX workflows through shared state artifacts and structured mailbox messaging.

What are the limitations of coordinating parallel workers via shared state directories?▼

Coordinating parallel workers via shared state directories can introduce synchronization bottlenecks in complex environments, as all API-based mutations and lifecycle management depend on the .omx/state/team directory for reliable worker coordination.