Ask AI about Agent Deck
Option 1: Claude Code Skill (recommended for Claude Code users)
/plugin marketplace add asheshgoplani/agent-deck
/plugin install agent-deck@agent-deck-help
Then ask: "How do I set up MCP pooling?"
Option 2: OpenCode (has built-in Claude skill compatibility)
# Create skill directory
mkdir -p ~/.claude/skills/agent-deck/references
# Download skill and references
curl -sL https://raw.githubusercontent.com/asheshgoplani/agent-deck/main/skills/agent-deck/SKILL.md \
> ~/.claude/skills/agent-deck/SKILL.md
for f in cli-reference config-reference tui-reference troubleshooting; do
curl -sL "https://raw.githubusercontent.com/asheshgoplani/agent-deck/main/skills/agent-deck/references/${f}.md" \
> ~/.claude/skills/agent-deck/references/${f}.md
done
OpenCode will auto-discover the skill from ~/.claude/skills/.
Option 3: Any LLM (ChatGPT, Claude, Gemini, etc.)
Read https://raw.githubusercontent.com/asheshgoplani/agent-deck/main/llms-full.txt
and answer: How do I fork a session?
https://github.com/user-attachments/assets/e4f55917-435c-45ba-92cc-89737d0d1401
The Problem
Running Claude Code on 10 projects? OpenCode on 5 more? Another agent somewhere in the background?
Managing multiple AI sessions gets messy fast. Too many terminal tabs. Hard to track what's running, what's waiting, what's done. Switching between projects means hunting through windows.
The Solution
Agent Deck is mission control for your AI coding agents.
One terminal. All your agents. Complete visibility.
- See everything at a glance — running, waiting, or idle status for every agent instantly
- Switch in milliseconds — jump between any session with a single keystroke
- Stay organized — groups, search, notifications, and git worktrees keep everything manageable
Features
Fork Sessions
Try different approaches without losing context. Fork any Claude conversation instantly. Each fork inherits the full conversation history.
- Press
f for quick fork, F to customize name/group
- Fork your forks to explore as many branches as you need
MCP Manager
Attach MCP servers without touching config files. Need web search? Browser automation? Toggle them on per project or globally. Agent Deck handles the restart automatically.
- Press
m to open, Space to toggle, Tab to cycle scope (LOCAL/GLOBAL), type to jump
- Define your MCPs once in
~/.agent-deck/config.toml, then toggle per session — see Configuration Reference
Skills Manager
Attach/detach Claude skills per project with a managed pool workflow.
- Press
s to open Skills Manager for a Claude session
- Available list is pool-only (
~/.agent-deck/skills/pool) to keep attach/detach deterministic
- Apply writes project state to
.agent-deck/skills.toml and materializes into .claude/skills
- Type-to-jump is supported in the dialog (same pattern as MCP Manager)
Per-group Claude config
Agent Deck supports per-group CLAUDE_CONFIG_DIR and env_file overrides. Useful when a single profile hosts groups that should authenticate against different Claude accounts — for example, a personal profile hosting a conductor group pinned to ~/.claude-work while other groups stay on ~/.claude.
