Settings > Triage lets the instance owner read and save the Triage route. Saving starts nothing: the Console still passes route: null to the Triage host, and the key and the wiring are separate changes.
Read. GET /api/triage/route returns the stored route (model, harness, cap, reset 00:00, time zone, revision, updatedAt) or route: null, plus the models the catalogue offers with the harnesses each one takes. No key, path, actor or env value.
Save. POST /api/triage/route takes exactly model, harness, cap, timeZone and revision. The model check is checkRoutes from packages/organization/src/launch-settings.mjs, called unchanged. The write goes through the store's writeRoute, so the lock, the revision compare and the receipt are the store's. A stale revision answers 409 triage-route-stale.
Owner only. The routes exist only with a system config and the dev owner or SSO. They use the proxy-admin owner rule. Anyone else gets the normal not-found page and the page reads no route.
Origin. POST needs exactly one matching Origin and same-origin. GET follows the repo GET convention: it refuses a foreign Origin or a cross-site request and accepts a request with no Origin and no Fetch Metadata, so a LAN dev host can read.
Catalogue. The Console asks each active organization's bus for its catalogue, in parallel, 5 s each. A model counts only if every ready catalogue describes it the same way and marks it available. With no ready catalogue every save is refused.
Panel. Model, harness, daily cap, reset 00:00 (read only) and time zone with no default. A refusal shows one plain line and keeps the fields. A save sends the revision the fields were read at.
Jason approved the route design on 2026-11-18 ("route as recommended") and this slice the same day.
Tests: triage-route-http (21), triage-settings-browser (9, plus a shots test that skips), browser, triage-drawer-browser.
triage-drawer-browser changes: its three no-Triage-request checks now skip the static /triage-settings.js script, which every page loads and which carries no data.
No bus schema, vocabulary, policy, role or CLI change.
Tests
Mutants: 61 of 63 red. The two survivors are equivalent (the catalogue check refuses the same inputs; the store throws only its own codes).
Lane gate on 0ba50111f: 201 webui test files, 1751 pass, 0 fail, 5 skipped (4 org-quick-live, 1 shots).
Lead check on 0ba50111f in a clean environment: 17 files (the nine triage test files, browser, proxy-page, single-pane, the three system pages, w15-shell and agent-drawer), 273 tests, 272 pass, 0 fail, 1 skipped (shots).
Review
One fresh claude-opus-5-5 reviewer: changes, two P2s and three P3s, nothing at P1. The P2s: a stale draft could revert another writer's save, and GET refused the owner on a LAN dev host. All five are fixed in the second commit with tests. No reviewer read the second or third commit.
Left for later
The display.js change adds triage/route to the unscoped API paths. No browser test runs it with an organization selected.
The code was written before its tests. Each test was then shown red by turning off the route or the script tag.
The catalogue merge is strict: one organization with an odd catalogue narrows the choices for all.
## What changes
Settings > Triage lets the instance owner read and save the Triage route. Saving starts nothing: the Console still passes `route: null` to the Triage host, and the key and the wiring are separate changes.
- **Read.** GET `/api/triage/route` returns the stored route (model, harness, cap, reset 00:00, time zone, revision, updatedAt) or `route: null`, plus the models the catalogue offers with the harnesses each one takes. No key, path, actor or env value.
- **Save.** POST `/api/triage/route` takes exactly `model`, `harness`, `cap`, `timeZone` and `revision`. The model check is `checkRoutes` from `packages/organization/src/launch-settings.mjs`, called unchanged. The write goes through the store's `writeRoute`, so the lock, the revision compare and the receipt are the store's. A stale revision answers 409 `triage-route-stale`.
- **Owner only.** The routes exist only with a system config and the dev owner or SSO. They use the proxy-admin owner rule. Anyone else gets the normal not-found page and the page reads no route.
- **Origin.** POST needs exactly one matching Origin and `same-origin`. GET follows the repo GET convention: it refuses a foreign Origin or a cross-site request and accepts a request with no Origin and no Fetch Metadata, so a LAN dev host can read.
- **Catalogue.** The Console asks each active organization's bus for its catalogue, in parallel, 5 s each. A model counts only if every ready catalogue describes it the same way and marks it available. With no ready catalogue every save is refused.
- **Panel.** Model, harness, daily cap, reset 00:00 (read only) and time zone with no default. A refusal shows one plain line and keeps the fields. A save sends the revision the fields were read at.
Jason approved the route design on 2026-11-18 ("route as recommended") and this slice the same day.
## How
- `packages/webui/src/triage-route-http.mjs` (new), `public/triage-settings.js` (new), `cli.mjs`, `serve.mjs`, `public/bus.js`, `public/index.html`, `public/display.js`.
- Tests: `triage-route-http` (21), `triage-settings-browser` (9, plus a shots test that skips), `browser`, `triage-drawer-browser`.
- `triage-drawer-browser` changes: its three no-Triage-request checks now skip the static `/triage-settings.js` script, which every page loads and which carries no data.
- No bus schema, vocabulary, policy, role or CLI change.
## Tests
- Mutants: 61 of 63 red. The two survivors are equivalent (the catalogue check refuses the same inputs; the store throws only its own codes).
- Lane gate on 0ba50111f: 201 webui test files, 1751 pass, 0 fail, 5 skipped (4 `org-quick-live`, 1 shots).
- Lead check on 0ba50111f in a clean environment: 17 files (the nine triage test files, browser, proxy-page, single-pane, the three system pages, w15-shell and agent-drawer), 273 tests, 272 pass, 0 fail, 1 skipped (shots).
## Review
One fresh claude-opus-5-5 reviewer: changes, two P2s and three P3s, nothing at P1. The P2s: a stale draft could revert another writer's save, and GET refused the owner on a LAN dev host. All five are fixed in the second commit with tests. No reviewer read the second or third commit.
## Left for later
- The `display.js` change adds `triage/route` to the unscoped API paths. No browser test runs it with an organization selected.
- The code was written before its tests. Each test was then shown red by turning off the route or the script tag.
- The catalogue merge is strict: one organization with an odd catalogue narrows the choices for all.
GET and POST /api/triage/route, owner only behind the proxy-admin gate, with one
Origin and Sec-Fetch-Site same-origin on a write and Fetch Metadata on a read.
GET returns the stored route or says it is not set, plus the merged catalogue
choices (model keys, availability, compatible installed harnesses) with no
provider, upstream, module, key or path. POST takes model, harness, cap, time
zone and revision, checks the route with checkRoutes against the merged
catalogue (offered, available, compatible, installed), requires a known time
zone with no default, and writes through the store's writeRoute, so the lock,
the revision compare and the receipt are the store's. A stale revision answers
409 with the stored revision. updatedBy is the signed-in owner.
The Settings > Triage page shows only to the owner /api/config marks proxyAdmin.
Model and harness selects (the harness list is the chosen model's), a cap in
tokens, reset 00:00 read only, a time zone, Save. Not set before a first save;
a refusal is one line and keeps the fields; a stale save offers Reload route; a
second Save while one runs does nothing; one line says saving does not start
Triage. cli.mjs keeps route: null for the Triage host.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What changes
Settings > Triage lets the instance owner read and save the Triage route. Saving starts nothing: the Console still passes
route: nullto the Triage host, and the key and the wiring are separate changes./api/triage/routereturns the stored route (model, harness, cap, reset 00:00, time zone, revision, updatedAt) orroute: null, plus the models the catalogue offers with the harnesses each one takes. No key, path, actor or env value./api/triage/routetakes exactlymodel,harness,cap,timeZoneandrevision. The model check ischeckRoutesfrompackages/organization/src/launch-settings.mjs, called unchanged. The write goes through the store'swriteRoute, so the lock, the revision compare and the receipt are the store's. A stale revision answers 409triage-route-stale.same-origin. GET follows the repo GET convention: it refuses a foreign Origin or a cross-site request and accepts a request with no Origin and no Fetch Metadata, so a LAN dev host can read.Jason approved the route design on 2026-11-18 ("route as recommended") and this slice the same day.
How
packages/webui/src/triage-route-http.mjs(new),public/triage-settings.js(new),cli.mjs,serve.mjs,public/bus.js,public/index.html,public/display.js.triage-route-http(21),triage-settings-browser(9, plus a shots test that skips),browser,triage-drawer-browser.triage-drawer-browserchanges: its three no-Triage-request checks now skip the static/triage-settings.jsscript, which every page loads and which carries no data.Tests
0ba50111f: 201 webui test files, 1751 pass, 0 fail, 5 skipped (4org-quick-live, 1 shots).0ba50111fin a clean environment: 17 files (the nine triage test files, browser, proxy-page, single-pane, the three system pages, w15-shell and agent-drawer), 273 tests, 272 pass, 0 fail, 1 skipped (shots).Review
One fresh claude-opus-5-5 reviewer: changes, two P2s and three P3s, nothing at P1. The P2s: a stale draft could revert another writer's save, and GET refused the owner on a LAN dev host. All five are fixed in the second commit with tests. No reviewer read the second or third commit.
Left for later
display.jschange addstriage/routeto the unscoped API paths. No browser test runs it with an organization selected.