Repository navigation
[FEATURE]: Auto-collapse all completed response activity into one summary row in Desktop #49088
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Problem
In OpenCode Desktop, after an assistant response finishes, every process detail remains laid out above the final answer: reasoning, exploration, read, grep, glob, list, Shell, Webfetch, edit, write, patch calls, and other tool activity. Long turns can leave dozens of rows on screen, so the final answer is difficult to find and read.
Disabling Show reasoning summaries, Expand Shell tool calls, and Expand edit tool calls does not solve this. Those settings only affect reasoning text or the body of individual tool cards; the activity rows themselves remain visible.
This request is not just about collapsing reasoning text or each tool output separately. It is about one turn-level collapsible container that includes all activity before the final answer, regardless of activity type.
Desired behavior
Please match the interaction used by Codex Desktop:
- While the assistant is working, show reasoning and tool activity live.
- When the final answer appears, automatically collapse all preceding reasoning and tool activity for that turn into one compact summary row, for example:
Completed in 3m 39sorCompleted · 18 steps · 3m 39s. - Keep the final answer outside the collapsed container and immediately readable.
- Clicking the summary row should expand the complete chronological activity history; clicking again should collapse it.
- If the user manually expands a completed turn, do not immediately auto-collapse it again.
- Ideally provide a setting such as Auto-collapse completed response activity, enabled by default.
The collapsed group should include every activity type, including reasoning, exploration groups, searches, reads, shell commands, web fetches, edits, writes, patches, and any future tool types.
Why this matters
The activity timeline is useful while work is in progress, but after completion the final answer becomes the primary content. Keeping all implementation details permanently flattened into the conversation creates visual noise, increases scrolling, and significantly hurts readability during long coding sessions.
Environment
- OpenCode Desktop 1.18.29
- Windows
- Current/new Desktop layout
Related issues
- [FEATURE]: Collapsible thinking steps with AI-generated summary titles to reduce Desktop lag (inspired by Trae) #29212 requests collapsible reasoning/thinking text, but does not cover grouping the entire completed turn, including every tool activity type.
- [FEATURE]: Persist desktop/web steps panel collapse state across sessions #7174 describes the older steps panel auto-collapsing after completion, but its request was about persisting panel state across sessions. This request asks to restore that completed-turn behavior in the current Desktop layout and apply it to all activity.
Activity
github-actions commentedon Sep 15, 2026
This issue might be a duplicate of existing issues. Please check:
If these cover the same need, consider consolidating there rather than tracking separately.
ankhzet commentedon Sep 15, 2026
@zqlu5566 +1, i would also add a "Go to last prompt" button to scroll you directly to the start of the input bubble that prompted this activity segment, as while working on several sessions/projects, it's often usefull to be able to quickly refresh the memory of what was the prompt exactly.
I, for. example, often forget on which phase of /speckit.{plan,tasks,implement,converge} i am on a specific session, and having to scroll around to find clues (or my last prompt, which may be tens of screen hights away) is not very convenient.
jinhuang712 commentedon Sep 21, 2026
+1 — hitting the same thing on macOS Desktop with the current layout.
The three existing timeline settings (
Show reasoning summaries,Expand shell tool parts,Expand edit tool parts) only control what is rendered inside individual rows; the activity rows themselves still stay flattened in the transcript once a turn ends. On long agentic turns the final answer ends up dozens of rows below the prompt, which is the main readability hit.There is already a partial precedent in the current layout:
read/glob/grep/listare grouped into a singleUsed N ...summary row (ContextToolGroupinpackages/session-ui). This request reads like the same idea extended to the whole completed turn, with the final assistant text kept outside the collapsed container.Requesting a design review from the core team before anyone invests in an implementation — per CONTRIBUTING, UI/core product features need sign-off first. If a maintainer can confirm the intended shape (auto-collapse on turn completion, an opt-out setting, final answer always visible), I am happy to help test and contribute.
lincux0 commentedon Oct 7, 2026
Hi! I'd like to help implement this feature for the Desktop/Web UI.
The proposed behavior matches a pain point I've been running into during long agentic sessions, and I'd be interested in contributing a small, focused implementation that:
I noticed this issue is currently assigned, so before starting implementation I'd like to check whether this is already being worked on.
If contributions are welcome, I'm happy to work from the existing timeline/session UI architecture and follow the project's design-review requirements. Is there a preferred implementation direction or design I should follow?
opencodejr commentedon Oct 28, 2026
Thanks for the detailed write-up, @zqlu5566!
You're on OpenCode Desktop 1.18.29, which is OpenCode v1. v1 now only gets fixes for critical bugs, such as data loss, security problems or crashes with no workaround. Feature requests like this one are unlikely to be added to v1.
The active work is happening in OpenCode v2 (versions 2.x, npm package
@opencode/cli, which has a rewritten Desktop/web app). Please try v2 and see whether its session timeline already handles completed turns better for you. If the problem is still there on v2, reply here or open a new issue that mentions your v2 version, and we'll look at it for v2.Related issues:
If you think this is critical, please reply and explain why.
opencodejr commentedon Oct 29, 2026
Closing this as not planned. The request was made against OpenCode Desktop 1.18.29 (v1), which only gets critical fixes, and we haven't heard back since.
If you try OpenCode v2 (2.x,
@opencode/cli) and completed turns still leave too much activity on screen, please open a new issue and include your v2 version. A related request for the v2 TUI is #59721. Thanks again for the detailed write-up!