Expand description
The bamboo health|status|sessions|session|stop|respond|schedules admin
CLI: a thin HTTP client over a running bamboo serve for operators (health
probe, session list/inspect/stop/respond, schedule management).
The bamboo health | status | sessions | session | stop | respond | schedules admin CLI.
A thin HTTP client over a running bamboo serve instance. Each command wraps
an endpoint the server already exposes — /api/v1/health,
/api/v1/sessions, /api/v1/stop/{id}, /api/v1/respond/{id},
/api/v1/schedules — so an operator can probe and steer the backend without
hand-writing curl. The server is the single source of truth; this module
only resolves the base URL and pretty-prints responses.
Structs§
- Conn
Args - Connection options shared by every admin subcommand.
- Schedule
Create Args - Flag-based inputs for
bamboo schedules create(the common case). The clap layer guarantees exactly one trigger source (cron/every/daily/json) and thatname+promptaccompany the flag form.
Functions§
- health
bamboo health— liveness probe. Exits non-zero (via the returnedErr) when the server is unreachable or reports an unhealthy status.- history
bamboo history <session-id>— print a session’s UI-visible message transcript (a thin read overGET /api/v1/history/{id}). Handy for reviewing what a headless-prun actually did, or an interactive session’s log, without the web UI. Folded in from the retiredbamboo-cli history.- mcp_add
bamboo mcp add --json <file|->— add (or overwrite) a server from a raw JSON payload passed through toPOST /api/v1/mcp/servers. The payload may be the internal shape or the mainstream flat shape (command/url), same as the HTTP API.- mcp_
connect bamboo mcp connect <id>— enable + (re)connect a configured server (POST /api/v1/mcp/servers/{id}/connect).- mcp_
disconnect bamboo mcp disconnect <id>— disable + disconnect a server (POST /api/v1/mcp/servers/{id}/disconnect).- mcp_
refresh bamboo mcp refresh [<id>]— re-list tools from one server, or from every enabled server when no id is given (POST /api/v1/mcp/servers/{id}/refresh).- mcp_
remove bamboo mcp remove <id>— stop + delete a server (DELETE /api/v1/mcp/servers/{id}). Destructive (the stored config is gone), though a removed server can be re-added withbamboo mcp add— so it confirms likesessions delete/schedules deleteunless--yes.- mcp_
status bamboo mcp status— live view overGET /api/v1/mcp/servers: connection state + tool counts per configured server.--jsonprints the raw response.- mcp_
tools bamboo mcp tools [<id>]— list the tools one server exposes (GET /api/v1/mcp/servers/{id}/tools), or every server’s tools (GET /api/v1/mcp/tools) when no id is given.--jsonprints raw JSON.- respond
bamboo respond <id> <answer>— answer a session’s pending question (permission gate / clarification) out-of-band viaPOST /api/v1/respond/{id}. Answering resumes the blocked run server-side.- respond_
pending bamboo respond <id> --pending— show the question a session is blocked on (GET /api/v1/respond/{id}/pending), pretty or as raw JSON.- schedules_
create bamboo schedules create— POST /api/v1/schedules. Either assembles the request from the common-case flags or posts a raw JSON payload verbatim (--json <file|->) for full schema fidelity.- schedules_
delete bamboo schedules delete <id>— DELETE /api/v1/schedules/{id}. Confirms interactively (after resolving the schedule’s name) unlessyesis set.- schedules_
list bamboo schedules list— tabulate schedules on a running server.- schedules_
run bamboo schedules run <id>— POST /api/v1/schedules/{id}/run (trigger now).- schedules_
runs bamboo schedules runs <id>— run history (GET /api/v1/schedules/{id}/runs).- schedules_
show bamboo schedules show <id>— one schedule in detail. The server exposes no single-schedule GET, so this filtersGET /api/v1/schedulesby id.- session_
delete bamboo session delete <id>— delete a session (DELETE /api/v1/sessions/{id}), cancelling any running execution. Prompts for confirmation unlessyesis set.- session_
show bamboo session show <id>— one session’s detail (GET /api/v1/sessions/{id}), pretty or as raw JSON.- sessions_
list bamboo sessions— tabulate sessions on a running server.- status
bamboo status— one-screen overview: address, health, session counts.- stop
bamboo stop <id>— cancel a running session’s loop.