A failed or refused chat turn now says why and what to do (lane chat-fail, defects F1 to F3).
F1, a failed turn (packages/harness/src/failure-notice.mjs, runner.mjs, packages/webui/src/public/chat.js). The chat line carries the harness's error as a plain cause and a next step. The cause is decoded, checked against the run's secrets, redacted and capped before it is shown. The code lives in the mounted harness directory so a sandboxed runner loads it.
F2, a refused start and a proxy stall (packages/bus/src). A refused thread start and a proxy-stall stop each put one plain line in the chat, once, with the cause and the next step.
F3, an account the proxy can't use (packages/bus/src). An account the proxy reports as unavailable or in error carries one plain reason with the next step, built only from fixed patterns. The reason reaches the page data; no page shows it yet (see Left for later).
packages/bus/tests/pickup-launch.test.mjs was red on refactor since #2001: its fixture ran a legacy Claude model on pi, which the harness rule refuses. The fixture runs that model on claude-code. No assertion changed.
packages/webui/tests/tasks-board-browser.test.mjs went red when 20 Nov 2026 UTC arrived: its fixture task was due that day and the card now read "overdue". The fixture task is due in 2099.
No new route, bus verb, schema change, refusal code, grant or role. Nothing under roles/, contracts/ or packages/queue/.
Tests
Lane gate on 07eca4a67: 271 files, 3392 pass, 4 fail (the pickup-launch fixture, fixed in the next commit). All 202 bus and plugins-harness files on 5a07f9e1f: 2086 pass, 0 fail.
Lead check in a clean environment: 622 files on 5a07f9e1f: 6458 pass, 1 fail, 7 skip. The one fail is the tasks-board date test, fixed in a7362a8fc and green alone (23 pass, 0 fail).
Review
Four rounds, each by a fresh claude-opus-5-5 reviewer: changes (9 findings), approve, changes (5 findings), approve. The last two commits are test fixtures only and were checked by the Lead.
Left for later
No page shows the F3 reason yet. The line belongs in packages/webui/src/public/display.js (field account.reason).
packages/webui/src/public/bus.js (Messages view) shows the new failure body with "Details:" twice.
A project whose setup never finishes stays silent in chat (project-pending is a wait).
A refused start outside the thread launcher has no chat line.
Redaction follow-ups rated P3 by the reviewers: over-redaction of long words after a key word, a secret split in two by ordinary words, a slow decode on text full of invalid escapes, English-only status patterns.
## What changes
A failed or refused chat turn now says why and what to do (lane chat-fail, defects F1 to F3).
- **F1, a failed turn** (`packages/harness/src/failure-notice.mjs`, `runner.mjs`, `packages/webui/src/public/chat.js`). The chat line carries the harness's error as a plain cause and a next step. The cause is decoded, checked against the run's secrets, redacted and capped before it is shown. The code lives in the mounted harness directory so a sandboxed runner loads it.
- **F2, a refused start and a proxy stall** (`packages/bus/src`). A refused thread start and a proxy-stall stop each put one plain line in the chat, once, with the cause and the next step.
- **F3, an account the proxy can't use** (`packages/bus/src`). An account the proxy reports as unavailable or in error carries one plain reason with the next step, built only from fixed patterns. The reason reaches the page data; no page shows it yet (see Left for later).
- **`packages/bus/tests/pickup-launch.test.mjs`** was red on refactor since #2001: its fixture ran a legacy Claude model on pi, which the harness rule refuses. The fixture runs that model on claude-code. No assertion changed.
- **`packages/webui/tests/tasks-board-browser.test.mjs`** went red when 20 Nov 2026 UTC arrived: its fixture task was due that day and the card now read "overdue". The fixture task is due in 2099.
No new route, bus verb, schema change, refusal code, grant or role. Nothing under `roles/`, `contracts/` or `packages/queue/`.
## Tests
- Lane gate on 07eca4a67: 271 files, 3392 pass, 4 fail (the pickup-launch fixture, fixed in the next commit). All 202 bus and plugins-harness files on 5a07f9e1f: 2086 pass, 0 fail.
- Lead check in a clean environment: 622 files on 5a07f9e1f: 6458 pass, 1 fail, 7 skip. The one fail is the tasks-board date test, fixed in a7362a8fc and green alone (23 pass, 0 fail).
## Review
Four rounds, each by a fresh claude-opus-5-5 reviewer: changes (9 findings), approve, changes (5 findings), approve. The last two commits are test fixtures only and were checked by the Lead.
## Left for later
- No page shows the F3 reason yet. The line belongs in `packages/webui/src/public/display.js` (field `account.reason`).
- `packages/webui/src/public/bus.js` (Messages view) shows the new failure body with "Details:" twice.
- A project whose setup never finishes stays silent in chat (`project-pending` is a wait).
- A refused start outside the thread launcher has no chat line.
- Redaction follow-ups rated P3 by the reviewers: over-redaction of long words after a key word, a secret split in two by ordinary words, a slow decode on text full of invalid escapes, English-only status patterns.
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
A failed or refused chat turn now says why and what to do (lane chat-fail, defects F1 to F3).
packages/harness/src/failure-notice.mjs,runner.mjs,packages/webui/src/public/chat.js). The chat line carries the harness's error as a plain cause and a next step. The cause is decoded, checked against the run's secrets, redacted and capped before it is shown. The code lives in the mounted harness directory so a sandboxed runner loads it.packages/bus/src). A refused thread start and a proxy-stall stop each put one plain line in the chat, once, with the cause and the next step.packages/bus/src). An account the proxy reports as unavailable or in error carries one plain reason with the next step, built only from fixed patterns. The reason reaches the page data; no page shows it yet (see Left for later).packages/bus/tests/pickup-launch.test.mjswas red on refactor since #2001: its fixture ran a legacy Claude model on pi, which the harness rule refuses. The fixture runs that model on claude-code. No assertion changed.packages/webui/tests/tasks-board-browser.test.mjswent red when 20 Nov 2026 UTC arrived: its fixture task was due that day and the card now read "overdue". The fixture task is due in 2099.No new route, bus verb, schema change, refusal code, grant or role. Nothing under
roles/,contracts/orpackages/queue/.Tests
07eca4a67: 271 files, 3392 pass, 4 fail (the pickup-launch fixture, fixed in the next commit). All 202 bus and plugins-harness files on5a07f9e1f: 2086 pass, 0 fail.5a07f9e1f: 6458 pass, 1 fail, 7 skip. The one fail is the tasks-board date test, fixed ina7362a8fcand green alone (23 pass, 0 fail).Review
Four rounds, each by a fresh claude-opus-5-5 reviewer: changes (9 findings), approve, changes (5 findings), approve. The last two commits are test fixtures only and were checked by the Lead.
Left for later
packages/webui/src/public/display.js(fieldaccount.reason).packages/webui/src/public/bus.js(Messages view) shows the new failure body with "Details:" twice.project-pendingis a wait).