pigeon

Use when deploying pigeon code changes across all machines after merging to main

Use when you need to understand worker architecture, endpoint flow, and command routing behavior before making changes

Use when you need to understand daemon route flow, storage model, worker connectivity, and command injection architecture before making changes

Use when you need to understand the OpenCode plugin event lifecycle, session state transitions, and daemon API contracts

Use when developing or refactoring OpenCode plugin handlers, tests, and daemon integration payloads

Use when you need to understand the swarm IPC subsystem — tables, routes, the per-target arbiter, the session→directory registry, and the wire envelope — before changing it

Use when implementing or testing swarm IPC features (new kinds, channels, plugin tools, or schema changes) with a TDD-first workflow

Use for day-to-day swarm IPC ops — health checks, inspecting queued/handed-off/failed messages, debugging stuck deliveries, force-failing retry loops, tailing arbiter logs

Use for daemon service health checks, runtime diagnostics, restart procedures, and burn-in monitoring

Use when daemon notifications, worker command ingest, session routes, or local injection behavior are failing

Use when configuring or troubleshooting secrets, sops injection, and auth boundaries across daemon, worker, and Telegram

Use when handling day-to-day worker operations such as health checks, log triage, incident response, and rollback

Use when worker endpoints fail, notifications are not sent, webhook auth breaks, or command routing regresses

Use when onboarding or repairing devbox and workstation configuration for Pigeon daemon, hooks, and worker connectivity

Use when deploying or updating the worker on Cloudflare and validating production health and auth behavior

Use when validating deployed worker parity with authenticated checks and an end-to-end notification and reply flow

Use when implementing daemon route, service, storage, worker, or injector changes with a test-first workflow

Use when cutting over daemon service to a new build, running burn-in checks, or preparing rollback