pan sync-main <id> — merge latest main into the feature branch for an active workspace
pan sync-main <id> — merge latest main into the feature branch for an active workspace
npx skills add https://github.com/eltmon/panopticon-cli --skill pan-sync-mainこのコマンドをClaude Codeにコピー＆ペーストしてスキルをインストール
| name | pan-sync-main |
| description | pan sync-main <id> — merge latest main into the feature branch for an active workspace |
| triggers | ["sync with main","sync main into workspace","pull in hotfix","merge main into branch","pan sync-main","get latest changes from main"] |
| allowed-tools | ["Bash","Read"] |
Merges the latest main branch into a workspace's feature branch. Uses git merge (not rebase) to avoid rewriting history, and delegates conflict resolution to the merge-agent specialist.
# CLI command
pan sync-main PAN-XXX
# Or via the dashboard API
curl -X POST http://localhost:3011/api/issues/PAN-XXX/sync-main
pan workspace discard --confirm first; agents never git stash)git fetch origin maingit merge origin/main| Result | Meaning |
|---|---|
| Already up to date | Main has no new commits since last sync |
| Success (N commits) | Clean merge or agent-resolved conflicts |
| Uncommitted changes | Commit or discard workspace changes first |
| Conflict (unresolvable) | Agent could not resolve — merge aborted, workspace unchanged |
# Sync PAN-123 workspace with latest main
pan sync-main PAN-123
# Output on success:
# ✓ Synced 3 commit(s) from main
# Commits merged: 3
# Changed files (5):
# src/lib/auth.ts
# src/lib/config.ts
# ...
# Output when already current:
# ✓ PAN-123 is already up to date with main
# Output on uncommitted changes (blocks):
# ✗ Sync failed: Workspace has uncommitted changes. Commit or discard them before syncing with main.
The "Sync with Main" button appears in the workspace detail panel:
pan approve <id> — Review and merge to mainpan review request <id> — Trigger review pipelinepan tell <id> "<message>" — Send message to agentFind, 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 kill <id> — stop a running agent (workspace and branch preserved)