Manage parallel coding agent sessions and worktrees with CCManager
Run Claude Code, Codex CLI, Gemini CLI, Cursor Agent, Copilot CLI, Cline CLI, OpenCode, Kimi CLI, and related coding assistants from one worktree-aware terminal manager.
npx skills add agentskillexchange/skills --skill manage-parallel-coding-agent-sessions-and-worktrees-with-ccmanager
npm install -g ccmanager and run ccmanager, or run without installing with npx ccmanager. Configure command presets and optional per-project .ccmanager.json settings when managing multiple assistants or worktrees.Use CCManager when an operator needs to supervise several coding-agent sessions across projects and Git worktrees without relying on tmux. The workflow is to launch `ccmanager` or `npx ccmanager`, create or select project worktrees, start the right assistant command, watch each session’s idle, busy, or waiting state, and use hooks, presets, copied session context, and `.worktreeinclude` files to keep parallel branches usable. Invoke it when normal product UIs or separate terminal tabs make it hard to see which agent needs input, preserve context across worktrees, or coordinate multiple repository tasks. The scope is multi-session coding-agent operations and worktree lifecycle management, not a generic SDK, model framework, or broad terminal replacement.
What this skill actually does
Inputs and prerequisites: Node.js, npm or npx, one or more supported coding-agent CLIs such as claude, codex, gemini, cursor-agent, copilot, cline, opencode, or kimi.
Setup notes: Install with npm install -g ccmanager and run ccmanager , or run without installing with npx ccmanager . Configure command presets and optional per-project .ccmanager.json settings when managing multiple assistants or worktrees.
Source and verification boundary: use https://github.com/kbwo/ccmanager as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.