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
A subagent session hangs on an inner tool call and I end up needing to cancel a subagent run for some reason or
I close OC while a subagent was running
that incomplete subagent calls are red in the TUI and now block a user from looking into that subagent's session transcript at all. As a workaround, I have to spawn another subagent so I can arrow through to find the one that never completed and figure out where things went wrong for that subagent. This feels like a UX bug or regression introduced in v1.15.13 that is a side-effect of what it was trying to accomplish. Specifically this looks to have taken place in #28664 in commit 5fb85a6
Looking at the code, here is what I think is going on: InlineTool was refactored to fix icon alignment on wrapped rows, but as a side-effect introduced a failed guard in the onMouseUp handler:
constfailed=createMemo(()=>Boolean(error()&&!denied()))onMouseUp={()=>{if(renderer.getSelection()?.getSelectedText())returnif(failed()){setErrorExpanded((value)=>!value)// expands error textreturn// we now never reach onClick}props.onClick?.()}}
So now, when a session is interrupted, processor.ts's cleanup() sets all in-flight tool parts to status: "error" with error: "Tool execution aborted". That flips failed() to true, causing clicks to toggle the error message instead of navigating into the child session.
The child sessionId is still preserved in the metadata (as interrupted: true), so the navigation could work. The click handler is just short-circuiting. I think the failed() guard needs to allow navigation if a sessionId exists, or not early-return when props.onClick is set.
Plugins
No response
OpenCode version
1.17.11
Steps to reproduce
kick off a subagent
wait for it to get mostly done
kill the oc instance
reopen parent session
try and click into the spawned subagent that never completed and appears red in the TUI
This issue might be a duplicate of existing issues. Please check:
[BUG] Cancelled subagents can't be opened in TUI + Ctrl+X intermittently fails #32432: Describes the same problem — cancelled/interrupted subagents can't be clicked to open their session in the TUI. Part A of that issue matches this report closely, including the same symptom (clicking does nothing after cancellation/interruption). Your analysis of the failed() guard short-circuiting props.onClick may explain the root cause described there as well.
Activity
github-actions commentedon Jun 29, 2026
This issue might be a duplicate of existing issues. Please check:
failed()guard short-circuitingprops.onClickmay explain the root cause described there as well.github-actions commentedon Aug 29, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.