Add expandable command and file-change activity boxes

[Quicksaver]

Summary

This adds richer expandable activity boxes for command and file-change work-log rows in the chat timeline. Command rows can now show the command, raw command, exit code, duration, stdout/stderr or fallback output, and file-change rows can show changed paths plus inline unified diffs when patch data is available.

The implementation keeps this data in the derived work-log model, extracts command result and patch metadata from provider payloads, and renders the richer details without losing the existing compact row behavior.

What Changed

• Preserved command output metadata in WorkLogEntry, including stdout, stderr, fallback output, exit code, and duration.
• Added bounded file-change patch extraction from provider payloads, including Codex-style nested file-change records and simple content diffs normalized into unified patches.
• Kept stable arrival order for unsequenced same-timestamp activity events so streamed output chunks are not scrambled by random event ids.
• Added expandable command details in MessagesTimeline with command/raw-command sections, status chips, tail-truncated output, and full-output expansion.
• Added expandable file-change details in MessagesTimeline with changed-file chips and inline diff rendering through the existing diff rendering utilities.
• Kept generic tool expansion behavior for rows that are neither command nor file-change details.
• Hardened command-output extraction so blank completed stdout falls back to aggregated output while live incremental whitespace chunks are still preserved exactly.
• Hardened command-output merging so shorter completed snapshots and shorter line-complete updated snapshots do not corrupt already merged command output, while prefix-like incremental chunks still append exactly.
• Refined shorter-prefix command-output merging so single-line repeated-prefix snapshots do not duplicate output, while ambiguous multiline prefix chunks still preserve incremental stream data.
• Addressed follow-up review findings in the merged VS Code extension code by stabilizing subagent activity row hooks, escaping inline webview bootstrap payloads, surfacing malformed desktop readiness responses, preserving readiness retries for transient body-read failures, disposing connected webview resources if render fails, and cleaning MCP socket directories after listen failures.
• Aligned desktop backend advertisement errors with Effect service conventions by switching to a schema tagged error with a stable message while preserving sanitized structured cause diagnostics in warning annotations.
• Surfaced source-control thread ref metadata update failures in the chat error banner without hiding unrelated thread errors when later metadata updates succeed, while making source-control metadata errors dismissible, keeping provider session errors non-dismissible, ignoring stale metadata update responses, pruning stale per-thread metadata state, and preserving cached active-thread metadata state across reconnect snapshots.
• Added focused coverage for command output extraction, output merging, file-change patch extraction, renderable command output helpers, and timeline rendering of command/file-change rows.

Why

Individual command and diff events are mostly opaque currently. We can somewhat see what the agent is doing, but we don't have a clear picture of what each command actually outputs, or what each file change actually produced.

Usually that's fine, most times we inspect the end result and trust the agent. Sometimes it's good to inspect a little deeper. For commands we can help steer by debugging their output, or just compare the results with manual runs. For diffs we can see better follow along the multiple changes an agent makes, or even inspect changes to git-ignored files (which don't appear on the main diff panel).

Validation

• (cd apps/web && pnpm exec vp test run --passWithNoTests --project unit src/session-logic.test.ts) passed: 1 file, 79 tests.
• (cd apps/web && pnpm exec vp test run --passWithNoTests --project unit src/components/chat/MessagesTimeline.test.tsx) passed: 1 file, 13 tests.
• pnpm exec vp run --filter @t3tools/web test -- src/components/chat/MessagesTimeline.test.tsx passed on the final branch state: 145 files, 1318 tests.
• pnpm exec vp run --filter t3code-vscode test -- src/backendManager.test.ts src/webview.test.ts src/mcpBridge.test.ts src/extension.test.ts passed on the final branch state: 6 files, 55 tests.
• pnpm exec vp run --filter @t3tools/desktop test -- src/backend/DesktopBackendManager.test.ts passed on the final branch state: 43 files, 241 tests.
• pnpm exec vp run --filter @t3tools/web test -- src/components/source-control/SourceControlPanel.logic.test.ts src/state/sourceControlPanel.test.ts passed after the source-control metadata error handling fix: 146 files, 1330 tests.
• pnpm exec vp run --filter @t3tools/web test -- src/components/ChatView.logic.test.ts passed after the source-control metadata error dismissal/race fixes: 146 files, 1335 tests.
• pnpm exec vp check passed. It reported 20 existing lint warnings outside this branch's changed files.
• pnpm exec vp run typecheck passed across all packages.
• $assess-work completed after the review fixes. Earlier CodeRabbit first/final passes reported 0 issues; Codex and blast review follow-ups were addressed in 1558dd029, 26c447183, and the desktop advertisement diagnostic commits through bac9d4907. The Macroscope source-control metadata thread was addressed by aa0adfd93, 1bb7681c, and a02327a7. The latest Cursor source-control metadata dismissal/race threads were addressed by 4ca7cf953, f15d7e34c, ef437d295, cface2863, and documented in 2565d1d90; CodeRabbit/Codex/blast assessment follow-ups were addressed and the final CodeRabbit pass reported 0 issues.

Proof

before:

after:

expanded command output with tail truncation:

expanded inline file-change diffs:

---

Note

High Risk
Touches orchestration persistence and auth bootstrap paths plus broad Git/VCS and desktop lifecycle behavior; scope and cross-client impact make regressions costly.

Overview
Chat work-log rows now expose richer expandable detail: command sections (stdout/stderr, exit code, duration, tail truncation), file-change chips with inline unified diffs when patch data exists, and dedicated subagent summary rows that link into child threads instead of treating collab items like generic expandable tools. session-logic carries structured command output, patch extraction, stable ordering for streamed chunks, and safer incremental output merging.

Codex subagent orchestration is wired end-to-end: threads gain persisted parentRelation (projection ingest/query, lifecycle commands), child shells and launch prompts from collab metadata, title generation from the title seed, resume/re-run status updates, and child turn interrupts routed through the root provider session without falling back to the parent’s active turn.

The fork also adds substantial platform surface: Git Version Control right-panel behavior and server RPCs (documented in SOURCE_CONTROL.md), desktop backend advertisements with sanitized failure diagnostics and cleanup on stop, VS Code–style host bootstrap (workspace folders, MCP servers, stdio-to-uds relay), legacy /api/auth/bootstrap/bearer compatibility routes, Electron context-menu separator normalization, and agent skills for multi-worktree update/port/comment flows. Docs and investigation logs (SUBAGENTS.md, POWER_CONSUMPTION.md, fork pointer in AGENTS.md) accompany these behaviors.

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

Note

Add expandable command and file-change activity boxes to the chat timeline

• Work entries in the messages timeline now render as expandable/collapsible rows with aria-expanded and aria-label attributes; commands, file changes, and subagent items each show structured detail panels when expanded.
• Subagent child threads are rendered as individual navigable buttons beneath a tool work entry, showing live or formatted status/duration labels and routing to the child conversation on click.
• session-logic.ts is significantly extended to extract stdout, stderr, exitCode, durationMs, and patch from tool payloads; merging across streaming updates now prefers cumulative content and avoids regressing to shorter snapshots.
• The Codex and Cursor adapters now buffer child subagent deltas and attach them to parent collab completion events; subagent conversations are deterministically routed to stable child thread IDs derived from a SHA-256 hash.
• Subagent threads are created and updated on-the-fly during provider runtime ingestion, with parentRelation lineage, depth, timing, and status transitions persisted to a new DB migration (033/034).
• Risk: the DB schema gains 12 new columns on projection_threads and two new indexes; migration 034 backfills root_thread_id for existing rows, which could be slow on large databases.

^{Macroscope summarized 91c1d67.}

[macroscopeapp]

Effect service conventions: one error class deviates from the module's pattern and the service error conventions.

^{Posted via Macroscope — Effect Service Conventions}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

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

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

[macroscopeapp]

Effect service conventions: one issue found in the newly added SourceControlPanelService. See inline comment.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

This newly added service declares a standalone SourceControlPanelServiceShape interface and passes it into Context.Service, but the convention is to define the service interface inline in the Context.Service declaration and refer to it as SourceControlPanelService["Service"] (no standalone FooShape type).

Suggested change: move the interface body inline into the tag and drop the separate interface:

export class SourceControlPanelService extends Context.Service<
  SourceControlPanelService,
  {
    readonly snapshot: (
      input: VcsPanelSnapshotInput,
    ) => Effect.Effect<VcsPanelSnapshotResult, GitCommandError>;
    // ...rest of the members...
    readonly compare: (
      input: VcsPanelCompareInput,
    ) => Effect.Effect<VcsPanelCompareResult, GitCommandError>;
  }
>()("t3/sourceControl/SourceControlPanelService") {}

Then update the implementation references from SourceControlPanelServiceShape["..."] to SourceControlPanelService["Service"]["..."].

^{Posted via Macroscope — Effect Service Conventions}