@edgehero/pi-dispatch-admin 0.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +33 -0
- package/dist/index.mjs +7057 -0
- package/package.json +53 -0
- package/skills/operate-pi-dispatch/SKILL.md +50 -0
package/README.md
ADDED
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
# @edgehero/pi-dispatch-admin
|
|
2
|
+
|
|
3
|
+
The **operator console** for [**pi-dispatch**](https://github.com/edgehero/pi-dispatch) — a
|
|
4
|
+
[pi](https://github.com/earendil-works/pi) extension that adds a `/dispatch` command (a live TUI overlay +
|
|
5
|
+
model-callable tools) for running the pi coding agent as a self-hosted service.
|
|
6
|
+
|
|
7
|
+
> This is a **companion** to a running pi-dispatch deployment. It reads that deployment's Valkey queue and
|
|
8
|
+
> run-history — install it in your own pi, alongside the pi-dispatch service. On its own it will show
|
|
9
|
+
> "queue unreachable".
|
|
10
|
+
|
|
11
|
+
## What it gives you
|
|
12
|
+
|
|
13
|
+
- A `/dispatch` overlay: live queue state, day/week/month **spend meters** + a daily token counter, run
|
|
14
|
+
history with per-job token & cost, and a unified **triggers** pane (cron / label / comment / pull_request).
|
|
15
|
+
- **Editable** triggers and **scheduled pause windows** ("quiet hours" per folder/repo), applied live.
|
|
16
|
+
- **Confirm-gated** model tools so an agent can operate the deployment (change limits, manage triggers/pauses)
|
|
17
|
+
with **a human approving each change** — fail-closed when no operator is present.
|
|
18
|
+
- The bundled `operate-pi-dispatch` **skill** documenting those human-in-the-loop gates.
|
|
19
|
+
|
|
20
|
+
## Install
|
|
21
|
+
|
|
22
|
+
```bash
|
|
23
|
+
pi install npm:@edgehero/pi-dispatch-admin
|
|
24
|
+
```
|
|
25
|
+
|
|
26
|
+
Then run pi and use `/dispatch`. Point it at your deployment with `VALKEY_URL` / `PI_LOGS_DIR` /
|
|
27
|
+
`PI_SETTINGS_FILE` / `PI_TRIGGERS_FILE` / `PI_PAUSE_WINDOWS_FILE` (the same values your pi-dispatch worker uses).
|
|
28
|
+
|
|
29
|
+
## The service
|
|
30
|
+
|
|
31
|
+
The queue, worker, container image, and GitHub receiver live in the main repo:
|
|
32
|
+
**https://github.com/edgehero/pi-dispatch** — start there. MIT. Read
|
|
33
|
+
[`SECURITY.md`](https://github.com/edgehero/pi-dispatch/blob/main/SECURITY.md) before you rely on it.
|