Agent docs

Pizza Bot

Choose the reviewed plugin path or the full read-only bridge.

Plugin path

Copy integrations/pizza-bot-plugin into~/.pizza-bot/plugins/audioreality, or install a ZIP of that directory from Pizza Bot's Plugins page. SetAUDIOREALITY_TOKEN in the environment that starts Pizza Bot, then reload plugins.

The audioreality-report skill asks beforesubmit_report, showing exactly what leaves. The cron-readyaudioreality-standup skill allows batched submission, but Pizza Bot currently gives skills no tool for listing completed, Unread, or Action threads. It can therefore report only the current automation thread.

Bridge path

Use the bridge for complete terminal-event and Action-queue coverage. It reads Pizza Bot's HTTP API and submits Report v1 records; it never approves, rejects, edits, resumes, or deletes Pizza Bot data.

export PIZZA_BOT_URL=http://127.0.0.1:8080
export PIZZA_BOT_TOKEN=your-pizza-api-token
export AUDIOREALITY_TOKEN=ar_show_...
npx -y @audioreality/pizza-bot-bridge

Modes and mapping

success maps to ok; error to fail.
timeout and cancelled map to warn.
interrupted maps to needs_decision.
BRIDGE_MODE can be events, digest, or both.
BRIDGE_DIGEST_AT=07:00 controls the local daily Action snapshot.
INCLUDE_DETAILS=false keeps the default summary-only.

Replay and desktop limits

Persist BRIDGE_STATE_FILE: the SSE cursor advances only after a report is accepted, superseded, or deduplicated. Pizza Bot has no approval-resolved event, so a terminal event or Action-list disappearance resolves the shared thread run_id.

The desktop app exposes no supported sidecar discovery file. Supply its active loopback URL and token explicitly, or run the bridge beside the standalone backend with the provided Docker Compose example.