primeline-ai

Claude Tmux Orchestration

Name: Claude Tmux Orchestration
Author: primeline-ai

AI community

SOURCE https://github.com/primeline-ai/claude-tmux-orchestration

Description

Claude Code tmux orchestration — spawn full AI sessions as parallel workers with heartbeat monitoring and file-based coordination

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

Claude Code tmux Orchestration - Parallel AI Sessions with Full Context

**Spawn full Claude Code sessions as workers**, coordinated through a bash heartbeat and file-based state. Attach to any of them mid-run and take over by hand.

[![Blog Post](https://img.shields.io/badge/Deep_Dive-primeline.cc-blue)](https://primeline.cc/blog/tmux-orchestration) [![Free Guide](https://img.shields.io/badge/Free_Guide-3_Pattern_System-green)](https://primeline.cc/guide)

![claude-tmux-orchestration](assets/hero.png)

Status: read this before you clone

**Built March 2026. Reviewed 2026-07-31 against current Claude Code. Still runs, but the reason to use it has changed.**

This was built when subagents could not do much. Since then Claude Code absorbed most of it. Per [Anthropic's subagent docs](https://code.claude.com/docs/en/sub-agents), subagent frontmatter now accepts `maxTurns`, `hooks`, `mcpServers`, `skills`, `memory`, `effort`, `background` and `isolation`, and each subagent runs in its own context window.

So the original pitch - "subagents are crippled, use full sessions instead" - is no longer true. **Try subagents first.** They are one file instead of a bash control loop.

Original claim (March 2026)	Status today
Subagents cap at ~25 tool calls	False. `maxTurns` is a frontmatter field.
Subagents get no hook events	False. `hooks` is configurable per agent; hook events carry `agent_id`.
Subagents cannot reach MCP servers	False. `mcpServers` is configurable per agent.
Subagents share the parent context window	False. Each runs in its own.

What this still buys you

Three things survive, and only three. If none of them matter, use the native tools.

A session you can attach to. tmux attach, watch it work, interrupt it, answer its question by hand, let it continue. No lost context. When a long autonomous run goes sideways at minute 40, taking the wheel is worth the whole control loop.
**Full session lifecycle.