[Bug]: Inacesible tool call log

[trejjam]

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/desktop

Steps to reproduce

1. Start the app
2. Configure opencode HTTP API
3. Ask a model to execute a tool call (e.g., execute ls -la /home/)
4. Tool call executed

Expected behavior

Possibility to see the tool call log (does not react on click, stays compacted)

Actual behavior

Log stays compacted, when changing thread to thread, it disappears completely.

t3code:

opencode web UI:

Impact

Major degradation or frequent failure

Version or commit

t3code-nightly-bin 0.0.21_nightly.20260417.58-1

Environment

Manjaro, desktop, opencode remote backend, opus 4.7

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

No response

[trejjam]

Not related to the issue: thank you for supporting opencode HTTP API. I can see a great productivity boost coming :)

[juliusmarminge]

Closing as substantially fixed by merged PR #3022, which keeps work-log rows across turns, makes them expandable, and exposes full detail. The narrower echoed-command-versus-output defect remains tracked by canonical #216 and active PR #4083.