com um clique
pan-reload
Build Overdeck, then restart the dashboard only if the build succeeds.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Menu
Build Overdeck, then restart the dashboard only if the build succeeds.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Add repositories to the current progressive polyrepo workspace
pan close <id> — close-out ceremony for a completed and merged issue
pan review <subcommand> — manage the code review lifecycle: list pending work, re-request review, heal status drift, reset/abort/restart review cycles
pan start <id> — spawn a work agent for an issue in its own tmux session and workspace
Maintain a project knowledge wiki in Open Knowledge Format with /okf init, open, author, convert, sync, study, retro, extract, validate, lint, and embed.
pan flywheel — start, pause, resume, complete, stop, inspect, emit, and report on the singleton Fix-All Flywheel orchestrator
| name | pan-reload |
| description | Build Overdeck, then restart the dashboard only if the build succeeds. |
Use this after code changes that should run in the local Overdeck dashboard.
pan reload
pan reload --force # explicitly bypass the agent deploy-window gate
pan reload runs bun install and then npm run build first. If either fails, it leaves the current dashboard running and exits non-zero. If both succeed, it restarts the dashboard and waits for http://127.0.0.1:3011/api/health.
npm run build already rebuilds the dashboard server bundle (via build-post-cli.mjs → build:dashboard:server:bundle), so pan reload picks up server/deacon code changes — you do not need a separate npm run build:dashboard:server. The bun install step runs first so a merge/rebase that added a runtime dependency (e.g. chokidar) can't produce a freshly-built server that boot-crashes with ERR_MODULE_NOT_FOUND.
--skip-build — restart the current bundle without running bun install or npm run build.--force — bypass the deploy-window gate for an agent-issued reload. Without it, active verification, merge, post-merge, flywheel, restart, or pan dev ownership refuses the reload because it would disconnect live conversations and terminals.--health-timeout <ms> — set the dashboard health-check budget. The default is 30000.--no-deacon — restart without Cloister/Deacon auto-start.pkill, fuser, or manual port cleanup. The command uses the dashboard lifecycle code.3010 and the API on port 3011 by default.dist/dashboard/server.js under Node 22.