Skill Detail

Coordinate parallel terminal coding agents and worktrees with Pane

Use Pane to manage multiple terminal-based coding agents, git worktrees, remote sessions, files, git state, and approval prompts from one local or self-hosted control surface.

Developer ToolsMulti-Framework
Developer Tools Multi-Framework Published
โญ 478 GitHub stars โฌ‡ 5.7k/wk npm
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill coordinate-parallel-terminal-coding-agents-and-worktrees-with-pane Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
Pane desktop or Remote Pane, git, one or more terminal-based coding agents, and optional npm, pnpm, or installer paths.
Install & setup
Install Pane with curl -fsSL https://runpane.com/install.sh | sh on macOS or Linux, irm https://runpane.com/install.ps1 | iex on Windows PowerShell, or use the npm installer with npx –yes runpane@latest. Open Pane, connect the CLI agents you already use, then create sessions so Pane can manage terminals and git worktrees.
Author
Greenfield
Publisher
Company
Last updated
Sep 23, 2026
Quick brief

Use Pane when an operator is running several CLI coding agents across repositories and needs a controlled terminal workspace for parallel branches, worktrees, prompts, files, git state, approvals, and remote access from desktop or phone. Pane fits Claude Code, Codex, Cursor Agent, Aider, Goose, OpenCode, and other terminal-first agents because it does not require agent-specific plugins.

How it works

What this skill actually does

The repeatable workflow is concrete: install Pane, connect repositories and the CLI agents already in use, create panes or sessions, let Pane provision git worktrees, monitor and switch between agent terminals, pass context across panes, inspect files and git state, handle approval prompts, and clean up or rebase branches from the same control surface. Invoke it instead of manually juggling terminals and git worktree commands when parallel coding-agent work needs branch isolation and visibility. The scope boundary is operator coordination for existing CLI agents and git worktrees, not a generic terminal emulator, IDE, SDK, or coding-agent product listing.