The Agent-Native Index

agent-native · Durable Execution & Scheduling · Verified 2026-09-26

pi-dispatch

Listed on The Agent-Native Index

Run the pi coding agent as a service — triggered on demand, on a cron schedule, or by a GitHub or GitLab issue, comment or pull/merge request — in a container you control, with a durable queue, a spend cap, and a live admin panel

Website ↗ Repo ↗ Full dossier ↗

What it does

pi-dispatch turns the pi coding agent into a self-hosted background service. CLI submissions, cron schedules, and GitHub, GitLab, Forgejo/Gitea, or Azure DevOps events enter one BullMQ/Valkey queue. A worker checks spend and turn limits, starts a locked-down ephemeral container, runs one committed skill against the target repository, records the result and usage, and removes the container.

It is scheduling and job-level durability rather than a general step-checkpoint workflow engine. Queue state survives restarts, jobs can be paused without being dropped, and selected follow-up triggers can resume the session that opened a pull request. The operator console provides run history, cost attribution, trigger/flow topology, quiet hours, and a global stop control.

Agent-facing interfaces

How agents onboard

Interaction pattern: Daemon / Extension + CLI

# Guided setup from pi
pi install npm:@edgehero/pi-dispatch-admin
# Then type /dispatch inside pi and follow the setup prompts.

# Headless setup and first job
mkdir my-dispatch && cd my-dispatch
npx @edgehero/pi-dispatch up
npx @edgehero/pi-dispatch worker
npx @edgehero/pi-dispatch run ./my-project --task "add type hints" --flow tidy

See the full onboarding section in the dossier.

Protocol surface

Interface Detail
CLI pi-dispatch up, worker, run, pause, resume, status, service, sandbox, and setup commands
pi Extension /dispatch TUI and model-callable dispatch_* observation/control tools
Forge Events HMAC-verified webhooks or polling for GitHub; webhook receivers for GitLab, Forgejo/Gitea, and Azure DevOps
Queue BullMQ over Valkey with AOF persistence, deduplication, retention, and concurrency control
Configuration triggers.json, pause windows, environment variables, committed .pi/skills, and pinned staged pi packages
Run History Durable structured records plus a per-model token/cost ledger and generated insights report

Verification

Last verified 2026-09-26.

Sources: