@edgehero/pi-dispatch-admin 4.1.0 → 4.2.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 +3 -0
- package/dist/index.mjs +596 -200
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -132,6 +132,9 @@ One command puts a live terminal view over the whole deployment:
|
|
|
132
132
|
<img src="https://raw.githubusercontent.com/edgehero/pi-dispatch/main/docs/images/dispatch-dashboard.png?v=2026-10-09" alt="The /dispatch panel: status, spend meters, dollar windows, triggers with a portfolio trigger, pause windows, scoped limits with their dollar caps, held and failed jobs, runs with their projects and the u hosts key, and settings" width="820">
|
|
133
133
|
</p>
|
|
134
134
|
|
|
135
|
+
- **MCP servers, read-only.** A trigger that names MCP servers says so on its row (`[mcp ...]`), and its
|
|
136
|
+
drill-in shows each one as the overlay offers it now: where it runs, how its tools are reached, and the
|
|
137
|
+
variable names it is handed, or why every job of it would be refused. No tool and no key changes them.
|
|
135
138
|
- **Status and spend.** Queue and worker state, day, week and month spend meters, a daily token counter,
|
|
136
139
|
and the run history with tokens and cost per job. `Enter` on a run opens its full record, `x` on a
|
|
137
140
|
running job cancels it after asking, and `b` on an opened run reopens its workspace.
|