Agent Deck logo

Agent Deck

CommunityPopular
asheshgoplani
agent-deck

agent-deck, the terminal session manager for AI coding agents. Use when the user mentions "agent-deck", "session", "sub-agent", "MCP attach", or "git worktree", or needs to create, start, message, read, fork, restart, or supervise agent-deck sessions; launch child sessions or consult another CLI through agent-deck; attach MCPs to a session; manage groups, profiles, accounts, or worktree sessions; set up conductors or watchers; configure config.toml; or troubleshoot agent-deck. Not for in-conversation subagents, plain git worktrees, or plain tmux.

Overview

Publisherasheshgoplani
Repositoryagent-deck
Skill nameagent-deck
Stars
1.1K
Forks
192
Bundled files
36
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 36 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by asheshgoplani on GitHub. Read the source before you install it.

Installation

Install the Agent Deck AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/asheshgoplani/agent-deck/tree/main/skills/agent-deck
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/asheshgoplani/agent-deck.git /tmp/agent-deck
mkdir -p .claude/skills
cp -r /tmp/agent-deck/skills/agent-deck .claude/skills/agent-deck
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Agent Deck in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Agent Deck on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Agent Deck is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Agent Deck

Run agent-deck --version for your installed version. This skill targets v1.16.11+; most patterns work back to v1.7. See Backward Compatibility for what needs ≥1.16.11.

Scripts

Helper scripts live in this skill's scripts/ folder. Resolve them from the base directory shown when the skill loaded, not from the user's project:

bash
SKILL_DIR="/path/shown/in/base-directory-line"
$SKILL_DIR/scripts/launch-subagent.sh "Title" "Prompt" --wait

Plugin installs resolve to ~/.claude/plugins/cache/agent-deck/agent-deck/<hash>/skills/agent-deck/; a repo checkout resolves to <repo>/skills/agent-deck/.

Essential Commands

CommandPurpose
agent-deckLaunch interactive TUI
agent-deck add -t "Name" -c claude /pathCreate session
agent-deck launch . -c claude --account <name>Create and start a session under a named account slot
agent-deck session start/stop/restart <name>Control session
agent-deck session send <name> "message"Send message
agent-deck session send <name> --message-file <file>Send message from file (- = stdin); no shell quoting. Also on launch/session start
agent-deck session output <name>Get bounded, ANSI-clean last response (JSON/quiet/copy preserve full source)
agent-deck session children --jsonChild sessions' live status + asserted completions (non-blocking, read-only)
agent-deck session current [-q|--json]Auto-detect current session
agent-deck session fork <name>Fork Claude/OpenCode/Pi/Codex/Oh My Pi conversation
agent-deck mcp listList available MCPs
agent-deck mcp attach <name> <mcp>Attach MCP (then restart)
agent-deck statusQuick status summary
agent-deck open report.htmlShow an HTML report to the user in the macOS app Browser panel (works from remote sessions too)
agent-deck add --worktree <branch>Create session in git worktree

Status: ● running | ◐ waiting | ○ idle | ✕ error

Every other command and flag is in cli-reference.md.

Rules

  1. Flags before arguments: session start -m "Hello" name, not name -m "Hello". A flag that seems ignored is almost always in the wrong position.
  2. MCPs on request only: attach one when the user asks, then session restart it; attaching alone does not load it. --global writes Claude's config for every project; the default writes the session's .mcp.json.
  3. Leave other sessions to work: read another session with a single session output or session children call rather than a polling loop, which can interfere with the target.
  4. State only the task in a child's prompt. Every session agent-deck launches already carries its identity (session id, title, parent, core commands, completion sentinel; $AGENTDECK_IDENTITY_FILE for custom --cmd), so a prompt need not explain who the child is or how to reach its parent. Opt out with --no-identity or [launch] inject_identity = false; gemini also needs its identity folder trusted (documentation/HARNESS_IDENTITY.md).

Configuration

$XDG_CONFIG_HOME/agent-deck/config.toml (default ~/.config/agent-deck/config.toml; legacy ~/.agent-deck/config.toml still honored). Every option is in config-reference.md.

Where to Look Next

Read the matching reference before acting on anything beyond the commands above.

When the task involvesRead
What agent-deck and each session's CLI (claude, codex, gemini) can do; choosing the -c tool for a childcapabilities.md
Sessions messaging each other, send delivery guarantees, output, children, inbox drain, handoff, send pitfallssession-communication.md
Launching a sub-agent (launch-subagent.sh), retrieval modes, worker prompt conventions, the ===AGENTDECK_DONE=== completion sentinel, consulting Codex or Gemini, root-level peers (-no-parent)sub-agents.md
Fanning out several children and supervising them non-blockinglyfleet skill
Conductors (conductor setup), Telegram/Slack channels, watchers (webhook, GitHub, ntfy, Slack)conductors.md, then documentation/WATCHERS.md for custom watchers
Context inspection (session context), worktrees, scratch sessions (try), runtime health (health, dead letters, remote update --from-build), recall hints and search, session sharing, switching a session to another Claude accountsession-workflows.md
Self-improvement (transcript mining), goals (goal-driven worker autonomy), trust-but-verify for completion claimsautonomy.md, then self-improvement.md or goal.md for the deep dive
Using agent-deck as a daemon supervisor (it is not one), known gotchas and workarounds (--no-wait Enter fallback, text file busy, -c "claude <subcommand>", config drift, channel subscription, Telegram conductor topology, v1.9.x findings), and what needs a deck newer than 1.16.11gotchas.md
TUI keys, dialogs, search, and layouttui-reference.md
A session in error, MCPs not loading, diagnostics, getting help, or filing a bugtroubleshooting.md
Docker sandboxed sessionssandbox.md
Durable session hints and tags, the cross-harness transcript index, recall context --into current, federated search, the recall MCP serverrecall skill
Exporting or importing a session for another developersession-share skill
User-level vs pool skills, attaching and detaching skillsdocumentation/SKILLS.md
Fixing agent-deck itself and opening a PR.github/skills/agent-deck-contributor/SKILL.md in an agent-deck checkout; it mirrors the PR intake gate and runs tests sandboxed

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Agent Deck AI skill do?

agent-deck, the terminal session manager for AI coding agents. Use when the user mentions "agent-deck", "session", "sub-agent", "MCP attach", or "git worktree", or needs to create, start, message, read, fork, restart, or supervise agent-deck sessions; launch child sessions or consult another CLI through agent-deck; attach MCPs to a session; manage groups, profiles, accounts, or worktree sessions; set up conductors or watchers; configure config.toml; or troubleshoot agent-deck. Not for in-conversation subagents, plain git worktrees, or plain tmux.

Why use Agent Deck on TypingMind?

Because you install it once and use it with any model. Agent Deck is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Agent Deck in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/asheshgoplani/agent-deck/tree/main/skills/agent-deck. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Agent Deck?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Agent Deck?

As many as you like. As long as a model supports skills, you can use Agent Deck with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Agent Deck AI skill free?

Yes. It is published on GitHub by asheshgoplani under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇