Files
Brennan Benson 5ddfd7bcaf An unanswered model or effort change fails only its message, and each agent process end is logged with its cause (#40038)
* fix(native-chat): an unanswered model or effort change fails only its message, and each agent process end is logged with its cause

A model or effort write the agent didn't answer within 30 s, or a send withdrawn while its
write was pending, closed the agent's stdin. OpenCode exits 0 on that, so the chat showed
"OpenCode stopped while this response was in progress (code 0)" and its background work
died, with nothing logged. Session setters now carry a call deadline that sends
$/cancel_request and never touches the stream; later controls and prompts wait for a
withdrawn write to settle. Every agent process end logs who ended it and why.

* fix(native-chat): name Orca as the one ending an agent it stopped after its own failure

The exit record now reads endedBy orca for a host force-close and for an ACP agent Orca
stopped after losing its connection or refusing a journal write, with that reason leading.
The withdrawn-write test no longer races its deadline.

* fix(native-chat): keep who ended an agent when its last journal write is refused

Ruled by the independent decider: the failure-close cause is recorded before any publish that
can re-enter cleanup, an ended or requested ending never takes a new one, and the ended event
reads it from before publishing. A test drives a real refused journal write on an agent's own
exit and on a lost connection.

* fix(native-chat): redact the agent process end record's reason before it is logged

The reason can carry the agent's stderr tail, and the console line is not redacted downstream.
2026-11-08 17:56:18 -08:00
..