pan start <id> — spawn a work agent for an issue in its own tmux session and workspace
pan start <id> — spawn a work agent for an issue in its own tmux session and workspace
npx skills add https://github.com/eltmon/panopticon-cli --skill pan-start复制此命令并粘贴到 Claude Code 中以安装该技能
Find, review, read, inspect, summarize, or compare Panopticon conversations. Use when the user references a pan.localhost/conv/<id> URL, a conversation ID (e.g. "conv 371", "conversation 108"), a fuzzy reference ("that GPT conversation", "the last Sonnet session"), or asks to review/read/look at/check/summarize/compare conversations. Maps conversation IDs to Claude Code JSONL session files and parses session content. Read-only.
pan handoff <conv> — agent-authored conversation handoff that spawns a new conversation
Write a vBRIEF spec (.pan/spec.vbrief.json) and continue.json directly — without launching the interactive planning agent. Use when the work is well-understood and the agent can author the plan from the issue body and codebase alone. Also use when you ARE the work agent and need to self-plan before implementing. Covers the full vBRIEF v0.5 schema, continue.json format, bead sizing rules, inspection gates, and the `pan plan finalize` handoff command.
List the issues in the Panopticon pipeline, grouped by phase (Ship · Review · Work · Plan) with their TITLES — the on-demand text form of what the dashboard shows. Two views: the default "resource" view mirrors the Command Deck project tree (issues with a live workspace/branch/agent/PR right now); `--phase` gives the "lifecycle" view that mirrors the Pipeline page (every issue by phase, including planned-but-not-started work). Use when the user asks "what's in the pipeline", "list the pipeline", "what are we working on", or wants the active issues by phase with names. For the dense per-issue status matrix use /pipeline-status; this is the grouped, titled list.
pan kill <id> — stop a running agent (workspace and branch preserved)
pan sync-main <id> — merge latest main into the feature branch for an active workspace
| name | pan-start |
| description | pan start <id> — spawn a work agent for an issue in its own tmux session and workspace |
| triggers | ["pan start","start working on","work on issue","spawn agent","create workspace"] |
| allowed-tools | ["Bash","Read"] |
Run the command now:
pan start <issue-id>
pan start PAN-123 # Spawn agent for issue PAN-123
pan start MIN-456 # Works with any tracker prefix
pan start PAN-123 --force # Clear a paused agent gate and start anyway
pan start PAN-123 --host # Break-glass: bypass workspace Docker stack-health gate
pan start PAN-123 --fresh # Drop the saved session and start a new one (e.g. switch model)
Creates a git worktree at workspaces/feature-<id>/, installs dependencies, then spawns
an autonomous Claude Code agent in a tmux session (agent-<id>). The agent loads the
issue spec, creates a plan, and begins implementation.
If an agent is paused, pan start <id> refuses to spawn until you run pan unpause <id>.
Use --force only when you intentionally want to clear that pause gate and start anyway.
For projects with workspace Docker configured, pan start checks stack health before
spawning. Use --host only as an explicit break-glass override; interactive shells always
prompt, while non-interactive callers must pass --yes to confirm.
If a stopped agent has a saved Claude session, pan start refuses and points you to
pan resume <id> (continue that session). Use --fresh to deliberately discard the
saved session and start a brand-new one — for example, to relaunch a stopped agent on a
different model, where the existing session can't resume under different provider routing.
--fresh is non-destructive: it clears only the resume pointer, never the JSONL transcript,
and refuses while the agent is still running (stop it first with pan kill <id>).
pan plan <id> — create an execution plan before startingpan show <id> — inspect agent state while it workspan tell <id> — send a message to the running agentpan done <id> — signal the agent has completed its work