fix(web): keep trailing tool groups out of "Worked for" accordion

[Yash-Singh1]

What Changed

Simplified composer and timeline behavior so trailing tool groups remain visible after terminal responses. Removed the hidden resting-controls layout and related scroll, selection, and event-scope plumbing, while preserving responsive branch and environment controls across web and mobile surfaces.

Why

Trailing tool groups could disappear after terminal responses because the composer relied on hidden controls, measured hosts, and restoration logic tied to timeline navigation. This change removes that fragile coordination and keeps the visible layout content-driven.

UI Changes

No screenshots included. The change updates composer context controls, branch and environment selectors, sidebar fallback icons, chat timeline behavior, and mobile work-log sizing.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Medium Risk
Changes core chat timeline row derivation and folding rules; regressions could affect turn folding, tool presentation, and assistant metadata placement across settled and error turns.

Overview
Settled-turn folding no longer hides work that appears after the terminal assistant message. The "Worked for …" accordion only folds entries at or before that message, so trailing commands and tool summaries stay on the timeline when a turn errors or finishes awkwardly.

Trailing tools read as one assistant block: when tool rows follow the final assistant text for the same turn, copy/timestamp metadata moves to a new assistant-meta row after those tools (always visible), instead of sitting under the prose alone.

Single completed tool calls render as direct work rows with an optional displayLabel (including lifecycle-collapsed start→complete pairs), replacing the previous work-toggle summary row for one-off calls. Multi-entry groups still use toggles; work-toggle rows now carry turnId for the trailing-meta logic.

UI wiring: shared AssistantMessageMeta, LegendListextraData refresh on row count changes, and stable-row equality updates for the new fields.

^{Reviewed by Cursor Bugbot for commit 515ee1f. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix trailing tool groups in MessagesTimeline to render after assistant response

• Settled turns now leave timeline entries after the terminal assistant message visible instead of folding them into the pre-response fold, via changes to deriveTurnFolds in MessagesTimeline.logic.ts.
• A new attachTrailingToolGroupsToAssistant pass suppresses metadata and copy button on the assistant message row and inserts an assistant-meta footer row after the last trailing tool group, so the metadata appears once after the trailing activity.
• Single completed tool calls now render directly as a work row with a display label instead of a summarized work-toggle row; multi-entry groups still use the grouped presentation.
• LegendList receives rows.length as extraData so the list refreshes when derived row count changes.
• Behavioral Change: MessagesTimelineRow gains assistant-meta variant, work.displayLabel, and work-toggle.turnId fields; isRowUnchanged compares these new fields for row reuse. AssistantCopyButton interface changed from receiving a full message-row object to receiving message, copyButtonVisible, and streaming directly.

^{Macroscope summarized 515ee1f.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.5 KiB	13.6 KiB	+71 B (+0.5%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	−3 B (−0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.6 KiB	+74 B (+1.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	57.1 KiB	+88 B (+0.2%)	66.4 KiB	✅
Codex	Live turn messages	8	10	+2 (+25.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.6 KiB	+20 B (+0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	+3 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.6 KiB	+17 B (+0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.9 KiB	57.9 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 5b8445b · PR result: 515ee1f · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 113.8 KiB
• Claude decoded thread snapshot: 114.5 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 3cf2ce7. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved at 515ee1f

Macroscope's review found this PR approvable — This is a focused chat-timeline bug fix that keeps trailing tool groups visible and places assistant metadata after them, with targeted regression coverage. The changes are confined to row derivation and rendering and introduce no defaults, schema, infrastructure, security, billing, authentication, or static-analysis configuration changes.

^{You can add or adjust custom eligibility rules. Learn more.}

[Yash-Singh1]

What Changed

Simplified composer and timeline behavior so trailing tool groups remain visible after terminal responses. Removed the hidden resting-controls layout and related scroll, selection, and event-scope plumbing, while preserving responsive branch and environment controls across web and mobile surfaces.

Why

Trailing tool groups could disappear after terminal responses because the composer relied on hidden controls, measured hosts, and restoration logic tied to timeline navigation. This change removes that fragile coordination and keeps the visible layout content-driven.

UI Changes

No screenshots included. The change updates composer context controls, branch and environment selectors, sidebar fallback icons, chat timeline behavior, and mobile work-log sizing.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Medium Risk
Changes core chat timeline row derivation and folding rules; regressions could affect turn folding, tool presentation, and assistant metadata placement across settled and error turns.

Overview
Settled-turn folding no longer hides work that appears after the terminal assistant message. The "Worked for …" accordion only folds entries at or before that message, so trailing commands and tool summaries stay on the timeline when a turn errors or finishes awkwardly.

Trailing tools read as one assistant block: when tool rows follow the final assistant text for the same turn, copy/timestamp metadata moves to a new assistant-meta row after those tools (always visible), instead of sitting under the prose alone.

Single completed tool calls render as direct work rows with an optional displayLabel (including lifecycle-collapsed start→complete pairs), replacing the previous work-toggle summary row for one-off calls. Multi-entry groups still use toggles; work-toggle rows now carry turnId for the trailing-meta logic.

UI wiring: shared AssistantMessageMeta, LegendListextraData refresh on row count changes, and stable-row equality updates for the new fields.

^{Reviewed by Cursor Bugbot for commit 515ee1f. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix trailing tool groups in MessagesTimeline to render after assistant response

• Settled turns now leave timeline entries after the terminal assistant message visible instead of folding them into the pre-response fold, via changes to deriveTurnFolds in MessagesTimeline.logic.ts.
• A new attachTrailingToolGroupsToAssistant pass suppresses metadata and copy button on the assistant message row and inserts an assistant-meta footer row after the last trailing tool group, so the metadata appears once after the trailing activity.
• Single completed tool calls now render directly as a work row with a display label instead of a summarized work-toggle row; multi-entry groups still use the grouped presentation.
• LegendList receives rows.length as extraData so the list refreshes when derived row count changes.
• Behavioral Change: MessagesTimelineRow gains assistant-meta variant, work.displayLabel, and work-toggle.turnId fields; isRowUnchanged compares these new fields for row reuse. AssistantCopyButton interface changed from receiving a full message-row object to receiving message, copyButtonVisible, and streaming directly.

^{Macroscope summarized 515ee1f.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.5 KiB	13.6 KiB	+71 B (+0.5%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	−3 B (−0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.6 KiB	+74 B (+1.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	57.1 KiB	+88 B (+0.2%)	66.4 KiB	✅
Codex	Live turn messages	8	10	+2 (+25.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.6 KiB	+20 B (+0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	+3 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.6 KiB	+17 B (+0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.9 KiB	57.9 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 5b8445b · PR result: 515ee1f · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 113.8 KiB
• Claude decoded thread snapshot: 114.5 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 3cf2ce7. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved at 515ee1f

Macroscope's review found this PR approvable — This is a focused chat-timeline bug fix that keeps trailing tool groups visible and places assistant metadata after them, with targeted regression coverage. The changes are confined to row derivation and rendering and introduce no defaults, schema, infrastructure, security, billing, authentication, or static-analysis configuration changes.

^{You can add or adjust custom eligibility rules. Learn more.}

[Yash-Singh1]

What Changed

Simplified composer and timeline behavior so trailing tool groups remain visible after terminal responses. Removed the hidden resting-controls layout and related scroll, selection, and event-scope plumbing, while preserving responsive branch and environment controls across web and mobile surfaces.

Why

Trailing tool groups could disappear after terminal responses because the composer relied on hidden controls, measured hosts, and restoration logic tied to timeline navigation. This change removes that fragile coordination and keeps the visible layout content-driven.

UI Changes

No screenshots included. The change updates composer context controls, branch and environment selectors, sidebar fallback icons, chat timeline behavior, and mobile work-log sizing.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Medium Risk
Changes core chat timeline row derivation and folding rules; regressions could affect turn folding, tool presentation, and assistant metadata placement across settled and error turns.

Overview
Settled-turn folding no longer hides work that appears after the terminal assistant message. The "Worked for …" accordion only folds entries at or before that message, so trailing commands and tool summaries stay on the timeline when a turn errors or finishes awkwardly.

Trailing tools read as one assistant block: when tool rows follow the final assistant text for the same turn, copy/timestamp metadata moves to a new assistant-meta row after those tools (always visible), instead of sitting under the prose alone.

Single completed tool calls render as direct work rows with an optional displayLabel (including lifecycle-collapsed start→complete pairs), replacing the previous work-toggle summary row for one-off calls. Multi-entry groups still use toggles; work-toggle rows now carry turnId for the trailing-meta logic.

UI wiring: shared AssistantMessageMeta, LegendListextraData refresh on row count changes, and stable-row equality updates for the new fields.

^{Reviewed by Cursor Bugbot for commit 515ee1f. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix trailing tool groups in MessagesTimeline to render after assistant response

• Settled turns now leave timeline entries after the terminal assistant message visible instead of folding them into the pre-response fold, via changes to deriveTurnFolds in MessagesTimeline.logic.ts.
• A new attachTrailingToolGroupsToAssistant pass suppresses metadata and copy button on the assistant message row and inserts an assistant-meta footer row after the last trailing tool group, so the metadata appears once after the trailing activity.
• Single completed tool calls now render directly as a work row with a display label instead of a summarized work-toggle row; multi-entry groups still use the grouped presentation.
• LegendList receives rows.length as extraData so the list refreshes when derived row count changes.
• Behavioral Change: MessagesTimelineRow gains assistant-meta variant, work.displayLabel, and work-toggle.turnId fields; isRowUnchanged compares these new fields for row reuse. AssistantCopyButton interface changed from receiving a full message-row object to receiving message, copyButtonVisible, and streaming directly.

^{Macroscope summarized 515ee1f.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.5 KiB	13.6 KiB	+71 B (+0.5%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	−3 B (−0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.6 KiB	+74 B (+1.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	57.1 KiB	+88 B (+0.2%)	66.4 KiB	✅
Codex	Live turn messages	8	10	+2 (+25.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.6 KiB	+20 B (+0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	+3 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.6 KiB	+17 B (+0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.9 KiB	57.9 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 5b8445b · PR result: 515ee1f · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 113.8 KiB
• Claude decoded thread snapshot: 114.5 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 3cf2ce7. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved at 515ee1f

Macroscope's review found this PR approvable — This is a focused chat-timeline bug fix that keeps trailing tool groups visible and places assistant metadata after them, with targeted regression coverage. The changes are confined to row derivation and rendering and introduce no defaults, schema, infrastructure, security, billing, authentication, or static-analysis configuration changes.

^{You can add or adjust custom eligibility rules. Learn more.}

[Yash-Singh1]

What Changed

Simplified composer and timeline behavior so trailing tool groups remain visible after terminal responses. Removed the hidden resting-controls layout and related scroll, selection, and event-scope plumbing, while preserving responsive branch and environment controls across web and mobile surfaces.

Why

Trailing tool groups could disappear after terminal responses because the composer relied on hidden controls, measured hosts, and restoration logic tied to timeline navigation. This change removes that fragile coordination and keeps the visible layout content-driven.

UI Changes

No screenshots included. The change updates composer context controls, branch and environment selectors, sidebar fallback icons, chat timeline behavior, and mobile work-log sizing.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Medium Risk
Changes core chat timeline row derivation and folding rules; regressions could affect turn folding, tool presentation, and assistant metadata placement across settled and error turns.

Overview
Settled-turn folding no longer hides work that appears after the terminal assistant message. The "Worked for …" accordion only folds entries at or before that message, so trailing commands and tool summaries stay on the timeline when a turn errors or finishes awkwardly.

Trailing tools read as one assistant block: when tool rows follow the final assistant text for the same turn, copy/timestamp metadata moves to a new assistant-meta row after those tools (always visible), instead of sitting under the prose alone.

Single completed tool calls render as direct work rows with an optional displayLabel (including lifecycle-collapsed start→complete pairs), replacing the previous work-toggle summary row for one-off calls. Multi-entry groups still use toggles; work-toggle rows now carry turnId for the trailing-meta logic.

UI wiring: shared AssistantMessageMeta, LegendListextraData refresh on row count changes, and stable-row equality updates for the new fields.

^{Reviewed by Cursor Bugbot for commit 515ee1f. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix trailing tool groups in MessagesTimeline to render after assistant response

• Settled turns now leave timeline entries after the terminal assistant message visible instead of folding them into the pre-response fold, via changes to deriveTurnFolds in MessagesTimeline.logic.ts.
• A new attachTrailingToolGroupsToAssistant pass suppresses metadata and copy button on the assistant message row and inserts an assistant-meta footer row after the last trailing tool group, so the metadata appears once after the trailing activity.
• Single completed tool calls now render directly as a work row with a display label instead of a summarized work-toggle row; multi-entry groups still use the grouped presentation.
• LegendList receives rows.length as extraData so the list refreshes when derived row count changes.
• Behavioral Change: MessagesTimelineRow gains assistant-meta variant, work.displayLabel, and work-toggle.turnId fields; isRowUnchanged compares these new fields for row reuse. AssistantCopyButton interface changed from receiving a full message-row object to receiving message, copyButtonVisible, and streaming directly.

^{Macroscope summarized 515ee1f.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.5 KiB	13.6 KiB	+71 B (+0.5%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	−3 B (−0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.6 KiB	+74 B (+1.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	57.1 KiB	+88 B (+0.2%)	66.4 KiB	✅
Codex	Live turn messages	8	10	+2 (+25.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.6 KiB	+20 B (+0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	+3 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.6 KiB	+17 B (+0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.9 KiB	57.9 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 5b8445b · PR result: 515ee1f · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 113.8 KiB
• Claude decoded thread snapshot: 114.5 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 3cf2ce7. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved at 515ee1f

Macroscope's review found this PR approvable — This is a focused chat-timeline bug fix that keeps trailing tool groups visible and places assistant metadata after them, with targeted regression coverage. The changes are confined to row derivation and rendering and introduce no defaults, schema, infrastructure, security, billing, authentication, or static-analysis configuration changes.

^{You can add or adjust custom eligibility rules. Learn more.}

[Yash-Singh1]

What Changed

Simplified composer and timeline behavior so trailing tool groups remain visible after terminal responses. Removed the hidden resting-controls layout and related scroll, selection, and event-scope plumbing, while preserving responsive branch and environment controls across web and mobile surfaces.

Why

Trailing tool groups could disappear after terminal responses because the composer relied on hidden controls, measured hosts, and restoration logic tied to timeline navigation. This change removes that fragile coordination and keeps the visible layout content-driven.

UI Changes

No screenshots included. The change updates composer context controls, branch and environment selectors, sidebar fallback icons, chat timeline behavior, and mobile work-log sizing.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Medium Risk
Changes core chat timeline row derivation and folding rules; regressions could affect turn folding, tool presentation, and assistant metadata placement across settled and error turns.

Overview
Settled-turn folding no longer hides work that appears after the terminal assistant message. The "Worked for …" accordion only folds entries at or before that message, so trailing commands and tool summaries stay on the timeline when a turn errors or finishes awkwardly.

Trailing tools read as one assistant block: when tool rows follow the final assistant text for the same turn, copy/timestamp metadata moves to a new assistant-meta row after those tools (always visible), instead of sitting under the prose alone.

Single completed tool calls render as direct work rows with an optional displayLabel (including lifecycle-collapsed start→complete pairs), replacing the previous work-toggle summary row for one-off calls. Multi-entry groups still use toggles; work-toggle rows now carry turnId for the trailing-meta logic.

UI wiring: shared AssistantMessageMeta, LegendListextraData refresh on row count changes, and stable-row equality updates for the new fields.

^{Reviewed by Cursor Bugbot for commit 515ee1f. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix trailing tool groups in MessagesTimeline to render after assistant response

• Settled turns now leave timeline entries after the terminal assistant message visible instead of folding them into the pre-response fold, via changes to deriveTurnFolds in MessagesTimeline.logic.ts.
• A new attachTrailingToolGroupsToAssistant pass suppresses metadata and copy button on the assistant message row and inserts an assistant-meta footer row after the last trailing tool group, so the metadata appears once after the trailing activity.
• Single completed tool calls now render directly as a work row with a display label instead of a summarized work-toggle row; multi-entry groups still use the grouped presentation.
• LegendList receives rows.length as extraData so the list refreshes when derived row count changes.
• Behavioral Change: MessagesTimelineRow gains assistant-meta variant, work.displayLabel, and work-toggle.turnId fields; isRowUnchanged compares these new fields for row reuse. AssistantCopyButton interface changed from receiving a full message-row object to receiving message, copyButtonVisible, and streaming directly.

^{Macroscope summarized 515ee1f.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.5 KiB	13.6 KiB	+71 B (+0.5%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	−3 B (−0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.6 KiB	+74 B (+1.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	57.1 KiB	+88 B (+0.2%)	66.4 KiB	✅
Codex	Live turn messages	8	10	+2 (+25.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.6 KiB	+20 B (+0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	+3 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.6 KiB	+17 B (+0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.9 KiB	57.9 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 5b8445b · PR result: 515ee1f · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 113.8 KiB
• Claude decoded thread snapshot: 114.5 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 3cf2ce7. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved at 515ee1f

Macroscope's review found this PR approvable — This is a focused chat-timeline bug fix that keeps trailing tool groups visible and places assistant metadata after them, with targeted regression coverage. The changes are confined to row derivation and rendering and introduce no defaults, schema, infrastructure, security, billing, authentication, or static-analysis configuration changes.

^{You can add or adjust custom eligibility rules. Learn more.}

[Yash-Singh1]

What Changed

Simplified composer and timeline behavior so trailing tool groups remain visible after terminal responses. Removed the hidden resting-controls layout and related scroll, selection, and event-scope plumbing, while preserving responsive branch and environment controls across web and mobile surfaces.

Why

Trailing tool groups could disappear after terminal responses because the composer relied on hidden controls, measured hosts, and restoration logic tied to timeline navigation. This change removes that fragile coordination and keeps the visible layout content-driven.

UI Changes

No screenshots included. The change updates composer context controls, branch and environment selectors, sidebar fallback icons, chat timeline behavior, and mobile work-log sizing.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Medium Risk
Changes core chat timeline row derivation and folding rules; regressions could affect turn folding, tool presentation, and assistant metadata placement across settled and error turns.

Overview
Settled-turn folding no longer hides work that appears after the terminal assistant message. The "Worked for …" accordion only folds entries at or before that message, so trailing commands and tool summaries stay on the timeline when a turn errors or finishes awkwardly.

Trailing tools read as one assistant block: when tool rows follow the final assistant text for the same turn, copy/timestamp metadata moves to a new assistant-meta row after those tools (always visible), instead of sitting under the prose alone.

Single completed tool calls render as direct work rows with an optional displayLabel (including lifecycle-collapsed start→complete pairs), replacing the previous work-toggle summary row for one-off calls. Multi-entry groups still use toggles; work-toggle rows now carry turnId for the trailing-meta logic.

UI wiring: shared AssistantMessageMeta, LegendListextraData refresh on row count changes, and stable-row equality updates for the new fields.

^{Reviewed by Cursor Bugbot for commit 515ee1f. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix trailing tool groups in MessagesTimeline to render after assistant response

• Settled turns now leave timeline entries after the terminal assistant message visible instead of folding them into the pre-response fold, via changes to deriveTurnFolds in MessagesTimeline.logic.ts.
• A new attachTrailingToolGroupsToAssistant pass suppresses metadata and copy button on the assistant message row and inserts an assistant-meta footer row after the last trailing tool group, so the metadata appears once after the trailing activity.
• Single completed tool calls now render directly as a work row with a display label instead of a summarized work-toggle row; multi-entry groups still use the grouped presentation.
• LegendList receives rows.length as extraData so the list refreshes when derived row count changes.
• Behavioral Change: MessagesTimelineRow gains assistant-meta variant, work.displayLabel, and work-toggle.turnId fields; isRowUnchanged compares these new fields for row reuse. AssistantCopyButton interface changed from receiving a full message-row object to receiving message, copyButtonVisible, and streaming directly.

^{Macroscope summarized 515ee1f.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.5 KiB	13.6 KiB	+71 B (+0.5%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	−3 B (−0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.6 KiB	+74 B (+1.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	57.1 KiB	+88 B (+0.2%)	66.4 KiB	✅
Codex	Live turn messages	8	10	+2 (+25.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.6 KiB	+20 B (+0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	+3 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.6 KiB	+17 B (+0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.9 KiB	57.9 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 5b8445b · PR result: 515ee1f · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 113.8 KiB
• Claude decoded thread snapshot: 114.5 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 3cf2ce7. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved at 515ee1f

Macroscope's review found this PR approvable — This is a focused chat-timeline bug fix that keeps trailing tool groups visible and places assistant metadata after them, with targeted regression coverage. The changes are confined to row derivation and rendering and introduce no defaults, schema, infrastructure, security, billing, authentication, or static-analysis configuration changes.

^{You can add or adjust custom eligibility rules. Learn more.}

[Yash-Singh1]

What Changed

Simplified composer and timeline behavior so trailing tool groups remain visible after terminal responses. Removed the hidden resting-controls layout and related scroll, selection, and event-scope plumbing, while preserving responsive branch and environment controls across web and mobile surfaces.

Why

Trailing tool groups could disappear after terminal responses because the composer relied on hidden controls, measured hosts, and restoration logic tied to timeline navigation. This change removes that fragile coordination and keeps the visible layout content-driven.

UI Changes

No screenshots included. The change updates composer context controls, branch and environment selectors, sidebar fallback icons, chat timeline behavior, and mobile work-log sizing.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Medium Risk
Changes core chat timeline row derivation and folding rules; regressions could affect turn folding, tool presentation, and assistant metadata placement across settled and error turns.

Overview
Settled-turn folding no longer hides work that appears after the terminal assistant message. The "Worked for …" accordion only folds entries at or before that message, so trailing commands and tool summaries stay on the timeline when a turn errors or finishes awkwardly.

Trailing tools read as one assistant block: when tool rows follow the final assistant text for the same turn, copy/timestamp metadata moves to a new assistant-meta row after those tools (always visible), instead of sitting under the prose alone.

Single completed tool calls render as direct work rows with an optional displayLabel (including lifecycle-collapsed start→complete pairs), replacing the previous work-toggle summary row for one-off calls. Multi-entry groups still use toggles; work-toggle rows now carry turnId for the trailing-meta logic.

UI wiring: shared AssistantMessageMeta, LegendListextraData refresh on row count changes, and stable-row equality updates for the new fields.

^{Reviewed by Cursor Bugbot for commit 515ee1f. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix trailing tool groups in MessagesTimeline to render after assistant response

• Settled turns now leave timeline entries after the terminal assistant message visible instead of folding them into the pre-response fold, via changes to deriveTurnFolds in MessagesTimeline.logic.ts.
• A new attachTrailingToolGroupsToAssistant pass suppresses metadata and copy button on the assistant message row and inserts an assistant-meta footer row after the last trailing tool group, so the metadata appears once after the trailing activity.
• Single completed tool calls now render directly as a work row with a display label instead of a summarized work-toggle row; multi-entry groups still use the grouped presentation.
• LegendList receives rows.length as extraData so the list refreshes when derived row count changes.
• Behavioral Change: MessagesTimelineRow gains assistant-meta variant, work.displayLabel, and work-toggle.turnId fields; isRowUnchanged compares these new fields for row reuse. AssistantCopyButton interface changed from receiving a full message-row object to receiving message, copyButtonVisible, and streaming directly.

^{Macroscope summarized 515ee1f.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.5 KiB	13.6 KiB	+71 B (+0.5%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	−3 B (−0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.6 KiB	+74 B (+1.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	57.1 KiB	+88 B (+0.2%)	66.4 KiB	✅
Codex	Live turn messages	8	10	+2 (+25.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.6 KiB	+20 B (+0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	+3 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.6 KiB	+17 B (+0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.9 KiB	57.9 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 5b8445b · PR result: 515ee1f · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 113.8 KiB
• Claude decoded thread snapshot: 114.5 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 3cf2ce7. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved at 515ee1f

Macroscope's review found this PR approvable — This is a focused chat-timeline bug fix that keeps trailing tool groups visible and places assistant metadata after them, with targeted regression coverage. The changes are confined to row derivation and rendering and introduce no defaults, schema, infrastructure, security, billing, authentication, or static-analysis configuration changes.

^{You can add or adjust custom eligibility rules. Learn more.}

[Yash-Singh1]

What Changed

Simplified composer and timeline behavior so trailing tool groups remain visible after terminal responses. Removed the hidden resting-controls layout and related scroll, selection, and event-scope plumbing, while preserving responsive branch and environment controls across web and mobile surfaces.

Why

Trailing tool groups could disappear after terminal responses because the composer relied on hidden controls, measured hosts, and restoration logic tied to timeline navigation. This change removes that fragile coordination and keeps the visible layout content-driven.

UI Changes

No screenshots included. The change updates composer context controls, branch and environment selectors, sidebar fallback icons, chat timeline behavior, and mobile work-log sizing.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Medium Risk
Changes core chat timeline row derivation and folding rules; regressions could affect turn folding, tool presentation, and assistant metadata placement across settled and error turns.

Overview
Settled-turn folding no longer hides work that appears after the terminal assistant message. The "Worked for …" accordion only folds entries at or before that message, so trailing commands and tool summaries stay on the timeline when a turn errors or finishes awkwardly.

Trailing tools read as one assistant block: when tool rows follow the final assistant text for the same turn, copy/timestamp metadata moves to a new assistant-meta row after those tools (always visible), instead of sitting under the prose alone.

Single completed tool calls render as direct work rows with an optional displayLabel (including lifecycle-collapsed start→complete pairs), replacing the previous work-toggle summary row for one-off calls. Multi-entry groups still use toggles; work-toggle rows now carry turnId for the trailing-meta logic.

UI wiring: shared AssistantMessageMeta, LegendListextraData refresh on row count changes, and stable-row equality updates for the new fields.

^{Reviewed by Cursor Bugbot for commit 515ee1f. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix trailing tool groups in MessagesTimeline to render after assistant response

• Settled turns now leave timeline entries after the terminal assistant message visible instead of folding them into the pre-response fold, via changes to deriveTurnFolds in MessagesTimeline.logic.ts.
• A new attachTrailingToolGroupsToAssistant pass suppresses metadata and copy button on the assistant message row and inserts an assistant-meta footer row after the last trailing tool group, so the metadata appears once after the trailing activity.
• Single completed tool calls now render directly as a work row with a display label instead of a summarized work-toggle row; multi-entry groups still use the grouped presentation.
• LegendList receives rows.length as extraData so the list refreshes when derived row count changes.
• Behavioral Change: MessagesTimelineRow gains assistant-meta variant, work.displayLabel, and work-toggle.turnId fields; isRowUnchanged compares these new fields for row reuse. AssistantCopyButton interface changed from receiving a full message-row object to receiving message, copyButtonVisible, and streaming directly.

^{Macroscope summarized 515ee1f.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.5 KiB	13.6 KiB	+71 B (+0.5%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	−3 B (−0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.6 KiB	+74 B (+1.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	57.1 KiB	+88 B (+0.2%)	66.4 KiB	✅
Codex	Live turn messages	8	10	+2 (+25.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.6 KiB	+20 B (+0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	+3 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.6 KiB	+17 B (+0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.9 KiB	57.9 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 5b8445b · PR result: 515ee1f · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 113.8 KiB
• Claude decoded thread snapshot: 114.5 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 3cf2ce7. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved at 515ee1f

Macroscope's review found this PR approvable — This is a focused chat-timeline bug fix that keeps trailing tool groups visible and places assistant metadata after them, with targeted regression coverage. The changes are confined to row derivation and rendering and introduce no defaults, schema, infrastructure, security, billing, authentication, or static-analysis configuration changes.

^{You can add or adjust custom eligibility rules. Learn more.}