You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 653d353
Browse filesBrowse the repository at this point in the historyBrowse files
fix(core): settle a declined tool call as the user's stop
A declined permission or a dismissed question ends the turn with a bare self-interrupt, which the settle reads as a shutdown. The turn then keeps its execution claim, is reported as `session.execution.interrupted` with reason `shutdown`, projects no idle outcome, and resumes at the next server start with "The server restarted while you were working…", so the model goes on with the work the user declined. Clients that wait out a shutdown (opencode.el) also keep the session busy after the reject.
The step now names the stop before interrupting: the drain input gains `reportDeclined`, which the execution layer wires to the coordinator's new `stopReason(key, "user")`. The settle releases the claim and cancels the session's jobs as for any user interrupt. Teardown is unchanged: a location that shuts down is closed before its pending asks are failed, and the step completes those for continuation before it reaches the decline.
This follows upstream PR anomalyco#54344 (closed unmerged) for upstream issue anomalyco#54180.
0 commit comments