pan kill <id> — stop a running agent (workspace and branch preserved)
npx skills add https://github.com/eltmon/panopticon-cli --skill pan-killKopieren Sie diesen Befehl und fügen Sie ihn in Claude Code ein, um den Skill zu installieren
| name | pan-kill |
| description | pan kill <id> — stop a running agent (workspace and branch preserved) |
| triggers | ["pan kill","stop agent","kill agent","terminate agent","abort agent"] |
| allowed-tools | ["Bash","Read"] |
This skill guides you through gracefully stopping a running autonomous agent and cleaning up its resources.
# Using pan CLI
pan kill ISSUE-123
# Or directly via tmux
tmux kill-session -t agent-ISSUE-123
Before killing, understand what the agent is doing:
# List running agents
pan status
# Or via tmux
tmux list-sessions | grep agent
# See recent activity
tmux capture-pane -t agent-ISSUE-123 -p | tail -30
Give the agent a chance to save state:
# Send shutdown message (ALWAYS use pan tell, NOT raw tmux)
pan tell ISSUE-123 "Please save your progress to STATE.md and stop working."
# Wait for acknowledgment
sleep 10
tmux capture-pane -t agent-ISSUE-123 -p | tail -10
# Then kill the session
tmux kill-session -t agent-ISSUE-123
WARNING: DO NOT use raw tmux send-keys - agents often forget the Enter key. Always use pan tell which handles this correctly.
# Kill immediately
tmux kill-session -t agent-ISSUE-123
# Confirm session is gone
tmux list-sessions | grep agent-ISSUE-123
# Should return nothing
# The workspace remains for inspection
ls -la /path/to/workspaces/ISSUE-123/
# View any uncommitted work
cd /path/to/workspaces/ISSUE-123
git status
git diff
# Kill all agent sessions
tmux list-sessions -F "#{session_name}" | grep "^agent-" | xargs -I {} tmux kill-session -t {}
# Verify all gone
tmux list-sessions | grep agent
Before killing, you may want to preserve the agent's progress:
# Attach and review
tmux attach -t agent-ISSUE-123
# Ctrl+b d to detach
# Or capture the full session
tmux capture-pane -t agent-ISSUE-123 -p -S - > agent-output.txt
# Preserve workspace state (per stash-discipline: commit or use salvageable: prefix)
cd /path/to/workspaces/ISSUE-123
git add -A && git commit -m "WIP: state before kill"
# OR, for humans only — explicit salvageable stash:
# git stash push -m "salvageable:ISSUE-123:$(date -u +%Y-%m-%dT%H:%M:%SZ):pre-kill"
Options for the work:
pan start ISSUE-123 to spawn a new agentSession won't die:
# Force kill with signal
tmux kill-session -t agent-ISSUE-123
# If that fails, find and kill the process
ps aux | grep "agent-ISSUE-123"
kill -9 <PID>
Multiple agents for same issue:
# List all matching sessions
tmux list-sessions | grep ISSUE-123
# Kill each one
tmux kill-session -t agent-ISSUE-123
tmux kill-session -t agent-ISSUE-123-2
Can't find the session:
# List ALL tmux sessions
tmux list-sessions
# Check if process is running outside tmux
ps aux | grep claude
/pan:status - Check agent status/pan:tell - Send message before killing/pan:rescue - Recover work from killed agentsFind, 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
pan start <id> — spawn a work agent for an issue in its own tmux session and workspace
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 sync-main <id> — merge latest main into the feature branch for an active workspace