The question tool aborts with Interaction cancelled because the location shut down in the desktop app, making it impossible to collect a decision from the owner.
Environment
- Client: OpenCode desktop app (
ai.opencode.desktop, bundle /Applications/OpenCode.app)
- Server: 2.0.16, pid 90359,
http://127.0.0.1:49374
- CLI binary: 2.0.18
- macOS (darwin)
Reproduction
- Run a session in the desktop app.
- Call the
question tool with any question and options.
- Observe the tool result:
{"error":{"type":"aborted","message":"Interaction cancelled because the location shut down","content":[]}}
The control never renders, so no answer can be given.
Occurrences — 2 consecutive, in the same session, with the server restarting between them:
- attempt 1, after the server had just restarted
- attempt 2, after a second server restart
Impact
Any workflow that relies on the question tool to present owner decision controls (Adopt/Adapt/Reject, A/B/C options) is unusable in the desktop app. The only fallback is plain prose in the assistant message, which loses the structured, nothing-pre-selected control that decision requests depend on.
Suspected cause
The abort message suggests the question's owning "location" is being torn down — plausibly a lifecycle/race issue between the question control's location and the desktop app's session or server lifecycle, rather than an owner cancellation. Note the two failures both coincided with a server restart, which may be relevant.
Question
Is this a known limitation of the desktop client, or a bug? If it is a race with server restart, it would be good to have it fail loudly (or retry) rather than silently aborting the interaction.
The
questiontool aborts withInteraction cancelled because the location shut downin the desktop app, making it impossible to collect a decision from the owner.Environment
ai.opencode.desktop, bundle/Applications/OpenCode.app)http://127.0.0.1:49374Reproduction
questiontool with any question and options.{"error":{"type":"aborted","message":"Interaction cancelled because the location shut down","content":[]}}The control never renders, so no answer can be given.
Occurrences — 2 consecutive, in the same session, with the server restarting between them:
Impact
Any workflow that relies on the
questiontool to present owner decision controls (Adopt/Adapt/Reject, A/B/C options) is unusable in the desktop app. The only fallback is plain prose in the assistant message, which loses the structured, nothing-pre-selected control that decision requests depend on.Suspected cause
The abort message suggests the question's owning "location" is being torn down — plausibly a lifecycle/race issue between the question control's location and the desktop app's session or server lifecycle, rather than an owner cancellation. Note the two failures both coincided with a server restart, which may be relevant.
Question
Is this a known limitation of the desktop client, or a bug? If it is a race with server restart, it would be good to have it fail loudly (or retry) rather than silently aborting the interaction.