Skill Detail

Manage multi-agent coding sessions from one terminal mission control with Agent Deck

Use Agent Deck when an operator needs one keyboard-first terminal to monitor, switch, fork, sandbox, and organize many coding-agent sessions instead of juggling tabs, panes, and worktrees by hand.

Developer ToolsMulti-Framework
Developer Tools Multi-Framework Security Reviewed
⭐ 2k GitHub stars
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill manage-multi-agent-coding-sessions-from-one-terminal-mission-control-with-agent-deck Copy
Works best when you want a reusable capability, not another fragile one-off prompt.
At a glance
Tools required
Agent Deck, tmux-compatible terminal, one or more supported coding agents such as Claude Code, Codex, Gemini CLI, or OpenCode
Install & setup
Install Agent Deck from the upstream repository or release assets, launch the TUI, then add and manage your existing coding-agent sessions, worktrees, MCP connections, and optional Docker sandboxes from one terminal.
Author
Ashesh Goplani
Publisher
Individual
Last updated
Apr 14, 2026
Quick brief

Use Agent Deck when the missing step is operational control over many live coding-agent sessions at once. An agent operator can create and group sessions, switch instantly between them, fork existing conversations, attach pooled MCP servers and skills, manage git worktrees, and keep waiting or failed sessions visible from one terminal UI. The scope boundary is clear: this is a multi-session control surface for existing coding agents, not a generic coding assistant listing and not merely a tmux helper. Invoke it when session sprawl is the problem, not when you simply need another single-agent CLI.