[t3dotgg]

The thread details card always shows the same rows. People who never use some of them (scripts, Open in editor, lineage) cannot get them out of the way, and Usage was stuck in Labs.

Now you choose what the card shows. Right-click the card, or open Settings → Appearance → Thread details, and tick the rows you want. Changes apply at once. Reset to default brings back the standard rows.

Default	Right-click menu	Workspace rows hidden

Nothing to show	Settings row	Settings menu

How it works

• One sparse client setting, threadDetailsItems, stores only choices that differ from the default. New rows appear for everyone, and unknown ids survive a downgrade.
• A flat list of 10 rows. A hidden row unmounts, so its queries and subscriptions stop.
• Usage moves out of Labs into the list (off by default). People who turned on the old Labs toggle keep it.
• The card now re-measures when the set of rows changes. Before, hiding rows while the card was compact left it stuck compact.
• When no row has anything to show, the card shows Choose what to show so you can always get back.
• Hidden rows keep their shortcuts. The open-in-editor fallback now also covers remote editor links, which was already missing when the card was closed or compact.
• Mobile has no matching card, so it is not changed.

Out of scope on purpose: ordering, drag and drop, per-project layouts, and plugins. Earlier attempts (#13163, #13833) grew in that direction.

Proof: tested in the web app with the Browser panel (inline card, narrow popover, non-git project, fresh draft, Settings). New tests fail without their fixes: the card density test, the remote editor shortcut test, and the setting resolution test. vp run check:changed passes.

Council review

Rounds: 3

Delegate	Round 1	Round 2	Round 3
Claude Opus 5.5	8/10	9.4/10	9.5/10
Muse Wonder Full	8.8/10	9.3/10	9.5/10
Codex GPT-6.1 Sol	8.5/10	9.2/10	9.5/10

Created with Claude Opus 5.5 in Claude Code.

🤖 Generated with Claude Code

[macroscopeapp]

Approvability

Verdict: Approved at 1f6aee2

Macroscope's review found this PR approvable — Adds customizable thread-details rows while preserving existing visibility defaults and Usage preferences. Changes are reversible client preferences, and remote editor shortcuts reuse the existing picker’s opening mechanism.

No code changes detected at 35829de. Prior analysis still applies.

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

[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	5.0 KiB	5.0 KiB	+6 B (+0.1%)	6.8 KiB	✅
Codex	Thread snapshot wire	3.8 KiB	3.8 KiB	0 B (0.0%)	4.9 KiB	✅
Codex	Live turn WebSocket wire	1.2 KiB	1.3 KiB	+6 B (+0.5%)	2.0 KiB	✅
Codex	Live turn WebSocket decoded	21.6 KiB	21.6 KiB	0 B (0.0%)	24.4 KiB	✅
Codex	Live turn messages	2	2	0 (0.0%)	8	✅
Claude	Total thread wire	5.1 KiB	5.0 KiB	−6 B (−0.1%)	6.8 KiB	✅
Claude	Thread snapshot wire	3.8 KiB	3.8 KiB	0 B (0.0%)	4.9 KiB	✅
Claude	Live turn WebSocket wire	1.3 KiB	1.3 KiB	−6 B (−0.5%)	2.0 KiB	✅
Claude	Live turn WebSocket decoded	21.9 KiB	21.9 KiB	0 B (0.0%)	24.4 KiB	✅
Claude	Live turn messages	2	2	0 (0.0%)	8	✅

Baseline: 4432fbe · PR result: 35829de · 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: 108.5 KiB
• Claude decoded thread snapshot: 108.8 KiB

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

[coderabbitai]

Important

Review skipped

Review was skipped as selected files did not have any reviewable changes.

Run configuration

• Source mode: Auto
• Repository: pingdotgg/t3code
• Branch: t3/thread-detail-panel-customization
• File: .coderabbit.config.ts
• Commit: 35829de
• Layers: Repository TS config
• Review profile: CHILL
• Plan: Team
• Run ID: 871a28ad-9c90-422a-b504-88a3fd7d69e2

Commits

Reviewing files that changed from the base of the PR and between 1f6aee2 and 35829de.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

No actionable comments were generated in the recent review.

Recent review info

Run configuration

• Source mode: Auto
• Repository: pingdotgg/t3code
• Branch: t3/thread-detail-panel-customization
• File: .coderabbit.config.ts
• Commit: 1f6aee2
• Layers: Repository TS config
• Review profile: CHILL
• Plan: Team
• Run ID: 769d5174-3099-4b87-8ea2-b63c670f23a1

Commits

Reviewing files that changed from the base of the PR and between 58e60bf and 1f6aee2.

Files selected for processing: 21

• apps/desktop/src/settings/DesktopClientSettings.test.ts
• apps/web/src/components/ChatView.tsx
• apps/web/src/components/GitActionsControl.tsx
• apps/web/src/components/chat/OpenInPicker.browser.test.tsx
• apps/web/src/components/chat/OpenInPickerShortcut.ts
• apps/web/src/components/chat/ThreadAutomationsPanel.tsx
• apps/web/src/components/chat/ThreadDetailsCard.browser.test.tsx
• apps/web/src/components/chat/ThreadDetailsCard.tsx
• apps/web/src/components/chat/ThreadDetailsItemsMenu.tsx
• apps/web/src/components/chat/ThreadDetailsPanel.tsx
• apps/web/src/components/chat/ThreadDetailsSection.tsx
• apps/web/src/components/chat/ThreadDetailsUsage.tsx
• apps/web/src/components/chat/threadDetailsItems.test.ts
• apps/web/src/components/chat/threadDetailsItems.ts
• apps/web/src/components/settings/AppearanceSettingsPanel.tsx
• apps/web/src/components/settings/LabsSettingsPanel.tsx
• apps/web/src/components/settings/ThreadDetailsItemsRow.tsx
• apps/web/src/components/settings/settingsSearch.ts
• docs/user/thread-sidebar.md
• docs/user/usage.md
• packages/contracts/src/settings.ts

Files with no reviewable changes: 1

• apps/web/src/components/settings/LabsSettingsPanel.tsx

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 3 remain after this review.

Walkthrough

The pull request adds per-item visibility controls for thread details, moves Usage configuration to Appearance settings, and supports opening remote editors through the favorite-editor shortcut. It also changes the placement of the automation loading-error message.

Changes: Thread details visibility

Layer / File(s)	Summary
Visibility settings and defaults packages/contracts/src/settings.ts, apps/web/src/components/chat/threadDetailsItems.ts, apps/web/src/components/chat/threadDetailsItems.test.ts, apps/desktop/src/settings/DesktopClientSettings.test.ts	The settings contract adds sparse per-item visibility overrides. Helpers resolve, update, and reset choices. Tests cover override behavior, and the desktop settings fixture includes the new setting.
Panel content and card interactions apps/web/src/components/chat/ThreadDetailsPanel.tsx, apps/web/src/components/chat/ThreadDetailsItemsMenu.tsx, apps/web/src/components/chat/ThreadDetailsCard.tsx, apps/web/src/components/chat/ThreadDetailsCard.browser.test.tsx, apps/web/src/components/chat/ThreadDetailsSection.tsx, apps/web/src/components/chat/ThreadDetailsUsage.tsx, apps/web/src/components/ChatView.tsx, apps/web/src/components/GitActionsControl.tsx	The panel filters content by visibility and availability, and adds context-menu controls. Card measurement responds to content changes. ChatView always supplies usage data, and Git action rows accept visibility controls.
Appearance settings and guidance apps/web/src/components/settings/ThreadDetailsItemsRow.tsx, apps/web/src/components/settings/AppearanceSettingsPanel.tsx, apps/web/src/components/settings/LabsSettingsPanel.tsx, apps/web/src/components/settings/settingsSearch.ts, docs/user/thread-sidebar.md, docs/user/usage.md	Appearance settings expose the thread-detail controls. Labs settings and search no longer list the former Usage toggle. User guidance describes the new controls.

Remote editor shortcut

Layer / File(s)	Summary
Remote shortcut handling apps/web/src/components/chat/OpenInPickerShortcut.ts, apps/web/src/components/chat/OpenInPicker.browser.test.tsx	The favorite-editor shortcut builds and opens a remote editor URL in remote-links mode. The browser test covers an SSH alias and verifies that the shell command is not called.

Automation loading error order

Layer / File(s)	Summary
Automation error placement apps/web/src/components/chat/ThreadAutomationsPanel.tsx	The loading-error message now renders after the task list. Its condition and content remain unchanged.

Priority: Normal

Estimated code review effort: 3 (Moderate) | ~25 minutes

Change: Feature

Sequence Diagram(s)

sequenceDiagram
  actor User
  participant ThreadDetailsPanel
  participant ThreadDetailsItemsMenuItems
  participant ClientSettings
  User->>ThreadDetailsPanel: Open item menu
  ThreadDetailsPanel->>ThreadDetailsItemsMenuItems: Render visibility controls
  User->>ThreadDetailsItemsMenuItems: Change an item
  ThreadDetailsItemsMenuItems->>ClientSettings: Update threadDetailsItems
  ClientSettings->>ThreadDetailsPanel: Provide updated visibility settings

Loading

sequenceDiagram
  actor User
  participant OpenInPickerShortcut
  participant buildRemoteOpenUrl
  participant openRemoteEditorUrl
  User->>OpenInPickerShortcut: Press favorite-editor shortcut
  OpenInPickerShortcut->>buildRemoteOpenUrl: Build URL from editor, host, and working directory
  buildRemoteOpenUrl-->>OpenInPickerShortcut: Return URL
  OpenInPickerShortcut->>openRemoteEditorUrl: Open URL

Loading

Suggested reviewers: 5knnbdwm, juliusmarminge

Merge Risk: Minimal · previous review 1f6ae

The visibility choices persist as intended, and the card adjusts when its content changes. No issue identified here needs to be resolved before merging.

Pre-merge checks: 3 · 1

Failed checks: 1 warning

Check name	Status	Explanation	Resolution
Description check		The description clearly explains the problem, implemented behavior, scope, screenshots, and verification. However, it does not follow the required section structure and does not provide a triaged issu…	Add the required Problem, Change, Scope and approval, and Verification sections. In Scope and approval, link the triaged issue or discussion with explicit maintainer approval, or explain why this focused configuration qualifies for an exemp…

Passed checks: 3 passed

Check name	Status	Explanation
Title check		The title clearly and concisely describes the main change: allowing users to choose which rows appear in the thread details card.
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Description check

Explanation

The description clearly explains the problem, implemented behavior, scope, screenshots, and verification. However, it does not follow the required section structure and does not provide a triaged issue or explicit maintainer approval for this broader behavior change.

Resolution

Add the required Problem, Change, Scope and approval, and Verification sections. In Scope and approval, link the triaged issue or discussion with explicit maintainer approval, or explain why this focused configuration qualifies for an exemption. Keep the existing screenshots and focused verification results in the Verification section.

Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}