fix(tui): restore nested subagent navigation without changing inline task UI

[nexxeln]

Closes#15972
Closes#15769

Summary

• fix session_child_first in nested subagent sessions by using direct children of the current session (parentID === route.sessionID) instead of sibling lookup
• keep task rows as InlineTool and add optional click handling to inline tools so task click-to-navigate is restored without switching to block-style UI
• preserve existing children() semantics used by sibling-level aggregations (permissions()/questions()) to keep blast radius low

Verification

• bun run typecheck (packages/opencode)
• bun test test/config/tui.test.ts (packages/opencode)
• bun run build (packages/opencode)

[guazi04]

Nice, this looks great! One small suggestion: might be worth adding hover highlighting to InlineTool when onClick is set (similar to how BlockTool already does it). Without it there's no visual feedback that the task row is clickable — users might not realize they can click to navigate.

Something like:

const[hover,setHover]=createSignal(false)// on the box:onMouseOver={()=>props.onClick&&setHover(true)}onMouseOut={()=>setHover(false)}// on text/spinner:fg={hover() ? theme.text : fg()}

Minor thing, feel free to ignore 🙂

[jerome-benoit]

@nexxeln Tested this on Linux — the navigation logic and subagents memo are solid, but click-to-navigate on Task rows is completely broken because of the renderer.hasSelection guard.

Root cause:renderer.hasSelection (a getter on @opentui/core's renderer) returns true whenever any text buffer has selection state — which in a TUI with rendered text content is essentially always. Every onMouseUp handler exits early on the if (renderer.hasSelection) return check, so props.onClick?.() never fires.

Confirmed empirically: instrumented the handlers with Log.Default.error calls — onMouseUp fires correctly on every click, but hasSelection is true on 100% of events (38+ clicks, zero onClick invocations).

Fix: revert all three renderer.hasSelection → renderer.getSelection()?.getSelectedText() (the original check). This evaluates whether there's actual selected text content, not just whether a selection object exists.

Affected locations in the diff:

• UserMessage onMouseUp (L1126)
• InlineTool onMouseUp (L1685)
• BlockTool onMouseUp (L1738)

[github-actions]

Closing this pull request because it has had no updates for more than 60 days. If you plan to continue working on it, feel free to reopen or open a new PR.