Zc277584121 Cc Tmux Worktree Orchestration
cc-tmux-worktree-orchestration is a Claude Code plugin for the Build phase that orchestrates parallel development using tmux and git worktrees with Claude Code.
by zc277584121 · github.com/zc277584121/cc-tmux-worktree-orchestration
Orchestrate parallel Claude Code sessions with tmux panes and git worktrees so you can build multiple features or experiments without branch collisions.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install zc277584121-cc-tmux-worktree-orchestration@zc277584121/cc-tmux-worktree-orchestrationBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:zc277584121/cc-tmux-worktree-orchestration") and the paste-ready config with skillselion.get_install_config("plugin:zc277584121/cc-tmux-worktree-orchestration").
What it does
cc-tmux-worktree-orchestration is a Claude Code plugin for solo builders who want true parallel development: separate git worktrees paired with tmux so multiple Claude Code agents (or you plus agents) can work on different branches in isolated directories without stepping on each other. Instead of serializing every feature through one working tree, you spin orchestrated environments—useful when you are building a main line while running a risky refactor or bugfix in parallel. The listing emphasizes orchestration, worktrees, and tmux rather than application code generation, so expect shell-oriented setup and conventions you must adapt to your machine. It suits intermediate builders comfortable with git worktree workflows and terminal multiplexing on macOS or Linux. It does not replace CI, code review, or merge conflict resolution; it reduces local context-switch cost before you ship. Verify tmux and git versions and read the repo’s creation commands before automating agent launches.
Highlights
- Combines tmux session management with git worktrees for parallel development setups
- Targets Claude Code agents working in isolated worktree environments simultaneously
- Orchestration-focused plugin (parallel-development, worktree, tmux keywords)
- Helps create multiple dev environments without constant branch checkout churn
- Single-plugin marketplace entry (pluginCount: 1) from cc-tmux-worktree-orchestration
Why builders use it
Running one repo and one branch at a time blocks solo builders who want several Claude Code agents working on different tasks in parallel.
After install, you can stand up orchestrated tmux plus git worktree environments so parallel Claude Code development sessions stay isolated and easier to manage.
At a glance
- Type - Plugin in DevOps.
- Adoption - 0 installs, 1 stars, 0 votes.
FAQ
Who is cc-tmux-worktree-orchestration for?
It is for developers who run Claude Code locally and want tmux plus git worktrees to manage multiple parallel coding environments.
When should I use tmux worktree orchestration?
Use it during build when you are splitting features or experiments across branches and need separate directories and terminal sessions for each Claude Code agent.
How do I add cc-tmux-worktree-orchestration to my agent?
Install the zc277584121/cc-tmux-worktree-orchestration Claude Code plugin, ensure tmux and git worktree support on your machine, then follow the repo commands to create and attach orchestrated environments.
Comments
Share how you use zc277584121-cc-tmux-worktree-orchestration, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.