Repository navigation
Web: a load-test panel on the shared --load engine #2911
Description
The problem
Load testing (--load) exists only in the one-shot CLI and mcpdo. A web user has to leave the app, rebuild the connection setup in a terminal, and read a JSON summary.
Proposal
A load panel in the web client that drives the shared engine (core/cli/handlers/load-test.ts, or a browser-safe split of it) over the current connection: pick a tool or scenario, set concurrency, duration and rate, watch progress, and read the summary (latency percentiles, error tallies, per-step and per-stage rows) as a table. The engine lives under core/cli/ today and imports Node-only modules for its file readers, so part of the work is separating the browser-safe engine from the CLI front-end helpers.
Split out of #2838 (item 9, "further ideas"), which covered items 1–8. Filed as follow-up work rather than built there, at the maintainer's request.
Activity
cliffhall commentedon Nov 5, 2026
Triage: Priority Low (total 5)
Board: #28, Status
Todo.fix(web): load panel validates only what a run uses (#2911)
feat(web): load-test panel on the shared --load engine (#2911)
test(cli): drop the unreachable non-Error branch from the load file r…
fix(web): load panel validates only what a run uses (#2911)
cliffhall commentedon Nov 5, 2026
Shipped in #2929 (merge ddf68cf).