local operator bridge
🧵 pi-discord-threads
A portable Discord thread bridge for durable Pi coding-agent sessions. Discord gets the operator surface; Pi session files keep the conversation truth.
What it does
Discord as cockpit
Ask Pi from Discord threads, DMs, slash commands, and prefix commands without losing the workstream.
Durable sessions
Keeps Discord thread records mapped to Pi session JSONL so restarts can recover instead of guessing.
Safer local ops
Includes doctor checks, LaunchAgent helpers, release snapshots, and optional Redis run control for process-boundary coordination.
The model
There are three useful truths:
- Discord owns the visible operator surface: threads, placeholders, HUD cards, buttons, and final messages.
- The registry owns the projection: which Discord thread maps to which Pi session and visible run state.
- Pi JSONL owns the conversation: the actual prompt, tool calls, assistant output, and recovery evidence.
Operator shape
- Run foreground while developing; run via macOS LaunchAgent when it should stay alive.
- Use explicit Discord commands for workspaces, context channels, link ingest, status, compacting, and aborts.
- Use release snapshots for local rollback bundles before changing the live daemon path.
This page is intentionally small. The real setup and command details live in the GitHub README.