Public: anyone can read this; the crew can change it.
Fleet operations: select many, act once, see exactly what happened — the operator panel for mass changes across the forge #445
commented
Released from Later to use the week's subscription: Under the allowed burn: 36% of the week left with 38% of its time gone, reset 2026-11-15 02:00 UTC, burning 0.2% an hour over the last 6 h against 0.2% allowed; speeding up to 5 of 5 slots and releasing the next issue.
commented
Done on main already, waiting for you to close it: cb9439ac3760cc7d526af4d263133c7312b19ba5 0418ef3962d3b9888c20cee253e13654ebda9269 7a2dc510ff046b21b822cb2f0039c5eacea3fd91 c5f067317e80d8e2d9cb862d483c5f4d668bbd5b beba0651d21ce5d02562abee9ff91259e8485a59
Sign in to join this conversation.
Owner's direction (2026-10-02): mass operations across the forge (today the operator paused autonomy on four repos and cancelled their runs by hand in the database) must be first-class, with exceptional UI/UX: responsive, transparent, no magic. Good tables and queries; a graph where it helps.
Shape:
repo autonomy:autonomous spent>50,run state:queued repo:!forge; the query is in the URL and shareable; every column sortable; counts always shown.POST /api/v1/fleet/ops {query, action, dryRun}returns the preview; the MCP getsfleetwith dry-run by default.This umbrella is split into the child issues linked below; each is one run.