Configurable sidebar detail for worktree rows

[big-guy]

Summary

Adds a Worktree details picker in Settings → Worktrees (below Setup & teardown scripts) that controls what extra info renders on the right side of each sidebar row. Default is unchanged (diff), so existing users see no behavior change unless they pick a different option.

Modes

• Diff stat (default) — +N −M from PR additions/deletions
• Age — relative worktree age (<1h / Nh / Nd / N.Ny, years switch in at ≥365 days)
• Pull Request — first assignee's avatar (far right) + milestone title + #NNN pill
• Nothing — hide the detail

The detail hides on hover so the existing Snooze / Remove action buttons can appear in its place — no real estate lost.

Cmd+I cycle (transient override)

A new hotkey Cmd+I cycles the displayed detail through diff → age → pr → diff without changing the configured default. 'none' is intentionally skipped so the hotkey never just blanks the row. The override is per-client renderer state (a tiny useSyncExternalStore cell in src/renderer/worktree-detail-override.ts) — no IPC, no persistence, resets on reload. Matches how sidebar widths / modal visibility are scoped per CLAUDE.md's slice-vs-useState guidance.

Live preview

A mock sidebar row above the option buttons in Settings updates in real time as you pick an option, including the same group-hover:hidden / hidden group-hover:flex Tailwind pattern as the real WorktreeTab — hover the preview to see the Snooze + Remove icons swap in.

Wiring

Standard slice path: shared reducer + event variant, persisted with default-omitted serialization ('diff' not written to config.json), IPC handler with validation for all four values, backend method, ElectronAPI type. The PR-mode render only fires for worktrees that already have a prStatus; otherwise nothing renders (same silent no-op as the diff mode when there's no PR yet).

Pure helper formatWorktreeAge lives in src/renderer/components/worktree-detail.ts with vitest coverage for hour/day/year boundaries and edge cases (missing createdAt, clocks in the future).

Test plan

• npm run typecheck clean
• npx electron-vite build clean
• npx vitest run src/renderer/components/worktree-detail.test.ts src/shared/state/settings.test.ts — age helper + settings reducer pass
• Launch app, open Settings → Worktrees → Worktree details, pick each option (Diff stat / Age / Pull Request / Nothing) and verify the sidebar updates live
• Hover a sidebar row and confirm the detail collapses to reveal the Snooze + Remove buttons
• Press Cmd+I in the app and confirm the sidebar detail cycles diff → age → pr → diff without touching the Settings picker; reload and confirm the override is gone
• On a worktree with an assignee + milestone + PR, switch to Pull Request mode and verify the milestone, #NNN, and far-right avatar render correctly
• Quit and relaunch — the chosen detail persists; default-value choice (diff) is omitted from config.json rather than written

[big-guy]

Looking for opinions on this.

I could go two ways with this:

1. There are useful details that users would want to see at a glance. Settings would let you pick which one you want to see. This PR is the first stab at that.
2. This is just visually distracting and is covered by the right column (PR/changed files). We'd just remove this entirely

For (1), a few future ideas I had:

• Information about the agent/model being used
• real-time status info (like subagents running or tasks completed/remaining)
• token spend

All of the above are complicated with multiple agents running at once or mixed agents (Codex + Claude).

If I had this option today, I would probably set it to None.

[frenchie4111]

I like the change you made in this PR to make it optional. I can't really see it getting more noisy from here. Like you said, most of the additional information belongs in the context sidebar.

I am personally on the fence between Diff and None. Diffs are useful to understand the magnitude of the changes on the worktree. It's a decent way of understanding "okay that one is going to take me X minutes to review" or "okay that one is X% risky"

naming nit. It's hard to figure out what "Sidebar" means in this context so I can see the settings being a bit confusing to people. We likely should use a preview based thing (like you have in the big UX change)

[frenchie4111]

One thing that I could find useful in the worktree sidebar is knowing who's PR I am reviewing. Now that I have been reviewing PRs within harness for a while the juggling of PRs is sometimes like "wait which one was this again..."

[big-guy]

One thing that I could find useful in the worktree sidebar is knowing who's PR I am reviewing. Now that I have been reviewing PRs within harness for a while the juggling of PRs is sometimes like "wait which one was this again..."

Do you care to know that before switching to a worktree? The changes on main for the PR panel show the assignee avatar now.

[big-guy]

I am personally on the fence between Diff and None. Diffs are useful to understand the magnitude of the changes on the worktree. It's a decent way of understanding "okay that one is going to take me X minutes to review" or "okay that one is X% risky"

Ah, this gives me other ideas that remove the need to make this configurable.

Instead of showing the details all the time, this could be shown some other ways:

• On hover, show a tooltip that summarizes diff stat, PR info and age.
• On mouseover, change how the row is presented so you can see the same information.
• On a keypress (maybe cmd), change how the row is presented to show more details, like above.

Or, this isn't a global setting. This is context based depending on the status of the worktree. If it's something you created, maybe you care about age and whether or not it's about to be merged. If it's something someone else created (and you're reviewing), you care about the size of it and who's assigned. If it's something that's inflight (no PR yet), you care about something else.

WDYT?

[big-guy]

Here's another variation... there's a default setting used (diff, PR, age, none) and a shortcut (cmd+I) that cycles through them. So you could configure this to None, but temporarily look at the others

[big-guy]

@frenchie4111 I'm not sure what the configuration looks like on your side, but it might make sense to enable the Merge queue. That way we can submit things for merge without having to update/rebase the PR first.