feat(web): custom display labels for worktrees

[TheIcarusWings]

What

Lets a worktree carry a readable display name instead of the auto-generated hash folder name (e.g. t3code-f07cb2c5). The label is cosmetic only — no git worktree move, no disk changes.

Screenshots

Bottom-bar workspace label — before vs. after renaming the worktree:

Default (hash-derived)	Custom label

Rename dialog (opened from the bottom-bar label or the sidebar):

Entry point — sidebar thread context menu ("Rename worktree"; note the renamed label already showing in the bottom bar):

Design

• Keyed by worktree PATH, not per-thread, so threads sharing a worktree always show the same name.
• Stored in a persisted worktreeLabelByPath map in useUiStateStore (local UI state).
• A single resolver — worktreeDisplayName(path, labelMap) = labelMap[path] ?? formatWorktreePathForDisplay(path) — is used everywhere a worktree name renders, so the UI stays consistent.
• The rename UI is a single, globally-mounted dialog (WorktreeRenameDialog) driven by a small worktreeRenameStore, so every entry point opens the same dialog and writes the same path-keyed label.

Rename entry points

• Sidebar thread context menu → "Rename worktree" (only for worktree-backed threads).
• Bottom-bar workspace label: double-click, or right-click → "Rename worktree" (desktop + mobile).

Leaving the field blank resets to the default hash-derived name. The label persists across reloads.

Where labels surface

• Bottom-bar workspace label (desktop BranchToolbarEnvModeSelector + mobile MobileRunContextSelector).
• Orphan-worktree delete confirmation dialog.

Tests

• worktreeDisplayName (label / fallback / blank / trim).
• setWorktreeLabel reducer (set / trim / clear / sibling independence) + persistence round-trip.
• Custom-label cases for resolveCurrentWorkspaceLabel / resolveLockedWorkspaceLabel.

pnpm typecheck and vp lint clean; full web unit suite passes (1057 tests). Verified manually in the running app: rename from all entry points, shared label across two threads on the same worktree, blank-resets-to-default, and persistence across reload.

🤖 Generated with Claude Code

---

Note

Low Risk
Client-only persisted UI labels and rename flows; worktree deletion still uses existing VCS APIs, with label cleanup on successful remove.

Overview
Adds cosmetic worktree display names keyed by environment and worktree path, persisted in local UI state and shared by every thread on that worktree (no disk/git changes).

A global WorktreeRenameDialog plus worktreeRenameStore lets users set or clear labels from the sidebar thread menu (Rename worktree), or from the bottom-bar workspace label via double-click or right-click (useWorktreeRenameTrigger). BranchToolbar / BranchToolbarEnvModeSelector read labels through useWorktreeLabel and pass them into resolveCurrentWorkspaceLabel / resolveLockedWorkspaceLabel.

worktreeDisplayName and formatWorktreeDeleteConfirmation use custom labels in orphan-worktree delete prompts; successful worktree removal clears the stored label. Unit tests cover label persistence, resolver behavior, rename trigger context-menu fallback, and display helpers.

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

Note

Add custom display labels for worktrees in the branch toolbar and sidebar

• Introduces a global WorktreeRenameDialog (via useWorktreeRenameStore) that lets users set or clear a cosmetic label for any active worktree, accessible via double-click, right-click context menu, or the sidebar thread context menu.
• Adds worktreeLabelByEnvironment to uiStateStore, persisted to localStorage and keyed by environment ID and worktree path.
• Updates BranchToolbarEnvModeSelector and BranchToolbar.MobileRunContextSelector to display the custom label when set, falling back to existing defaults ('Current worktree' / 'Worktree').
• Extends worktree delete flow in useThreadActions to show the custom label in confirmation text and clear the stored label on successful deletion.

^{Macroscope summarized 64f86a9.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 9ce56739-357c-4b92-9003-5c4b1b0fc4c5

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature (custom worktree labels) with new UI components, state management, and persistence logic. New features warrant human review, and there's an unresolved comment about potential data migration issues.

^{You can customize Macroscope's approvability policy. Learn more.}

[cursor]

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

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

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

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

[cursor]

Path-only label persistence dropped

Medium Severity

The parsePersistedState function was updated to expect the new worktreeLabelByEnvironment structure, but it no longer reads the prior worktreeLabelByPath format from the t3code:ui-state:v1 localStorage key. This causes existing custom worktree names to be lost on load and overwritten on the next state persistence.

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

[juliusmarminge]

Closing as part of backlog cleanup: this PR is stale, currently conflicting with main, has no approval, and has not had active remediation for 30+ days. If the change is still relevant, please rebase onto current main and request reopening or submit a focused current diff. Thank you for the contribution.

[TheIcarusWings]

What

Lets a worktree carry a readable display name instead of the auto-generated hash folder name (e.g. t3code-f07cb2c5). The label is cosmetic only — no git worktree move, no disk changes.

Screenshots

Bottom-bar workspace label — before vs. after renaming the worktree:

Default (hash-derived)	Custom label

Rename dialog (opened from the bottom-bar label or the sidebar):

Entry point — sidebar thread context menu ("Rename worktree"; note the renamed label already showing in the bottom bar):

Design

• Keyed by worktree PATH, not per-thread, so threads sharing a worktree always show the same name.
• Stored in a persisted worktreeLabelByPath map in useUiStateStore (local UI state).
• A single resolver — worktreeDisplayName(path, labelMap) = labelMap[path] ?? formatWorktreePathForDisplay(path) — is used everywhere a worktree name renders, so the UI stays consistent.
• The rename UI is a single, globally-mounted dialog (WorktreeRenameDialog) driven by a small worktreeRenameStore, so every entry point opens the same dialog and writes the same path-keyed label.

Rename entry points

• Sidebar thread context menu → "Rename worktree" (only for worktree-backed threads).
• Bottom-bar workspace label: double-click, or right-click → "Rename worktree" (desktop + mobile).

Leaving the field blank resets to the default hash-derived name. The label persists across reloads.

Where labels surface

• Bottom-bar workspace label (desktop BranchToolbarEnvModeSelector + mobile MobileRunContextSelector).
• Orphan-worktree delete confirmation dialog.

Tests

• worktreeDisplayName (label / fallback / blank / trim).
• setWorktreeLabel reducer (set / trim / clear / sibling independence) + persistence round-trip.
• Custom-label cases for resolveCurrentWorkspaceLabel / resolveLockedWorkspaceLabel.

pnpm typecheck and vp lint clean; full web unit suite passes (1057 tests). Verified manually in the running app: rename from all entry points, shared label across two threads on the same worktree, blank-resets-to-default, and persistence across reload.

🤖 Generated with Claude Code

---

Note

Low Risk
Client-only persisted UI labels and rename flows; worktree deletion still uses existing VCS APIs, with label cleanup on successful remove.

Overview
Adds cosmetic worktree display names keyed by environment and worktree path, persisted in local UI state and shared by every thread on that worktree (no disk/git changes).

A global WorktreeRenameDialog plus worktreeRenameStore lets users set or clear labels from the sidebar thread menu (Rename worktree), or from the bottom-bar workspace label via double-click or right-click (useWorktreeRenameTrigger). BranchToolbar / BranchToolbarEnvModeSelector read labels through useWorktreeLabel and pass them into resolveCurrentWorkspaceLabel / resolveLockedWorkspaceLabel.

worktreeDisplayName and formatWorktreeDeleteConfirmation use custom labels in orphan-worktree delete prompts; successful worktree removal clears the stored label. Unit tests cover label persistence, resolver behavior, rename trigger context-menu fallback, and display helpers.

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

Note

Add custom display labels for worktrees in the branch toolbar and sidebar

• Introduces a global WorktreeRenameDialog (via useWorktreeRenameStore) that lets users set or clear a cosmetic label for any active worktree, accessible via double-click, right-click context menu, or the sidebar thread context menu.
• Adds worktreeLabelByEnvironment to uiStateStore, persisted to localStorage and keyed by environment ID and worktree path.
• Updates BranchToolbarEnvModeSelector and BranchToolbar.MobileRunContextSelector to display the custom label when set, falling back to existing defaults ('Current worktree' / 'Worktree').
• Extends worktree delete flow in useThreadActions to show the custom label in confirmation text and clear the stored label on successful deletion.

^{Macroscope summarized 64f86a9.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 9ce56739-357c-4b92-9003-5c4b1b0fc4c5

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature (custom worktree labels) with new UI components, state management, and persistence logic. New features warrant human review, and there's an unresolved comment about potential data migration issues.

^{You can customize Macroscope's approvability policy. Learn more.}

[cursor]

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

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

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

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

[cursor]

Path-only label persistence dropped

Medium Severity

The parsePersistedState function was updated to expect the new worktreeLabelByEnvironment structure, but it no longer reads the prior worktreeLabelByPath format from the t3code:ui-state:v1 localStorage key. This causes existing custom worktree names to be lost on load and overwritten on the next state persistence.

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

[juliusmarminge]

Closing as part of backlog cleanup: this PR is stale, currently conflicting with main, has no approval, and has not had active remediation for 30+ days. If the change is still relevant, please rebase onto current main and request reopening or submit a focused current diff. Thank you for the contribution.

[TheIcarusWings]

What

Lets a worktree carry a readable display name instead of the auto-generated hash folder name (e.g. t3code-f07cb2c5). The label is cosmetic only — no git worktree move, no disk changes.

Screenshots

Bottom-bar workspace label — before vs. after renaming the worktree:

Default (hash-derived)	Custom label

Rename dialog (opened from the bottom-bar label or the sidebar):

Entry point — sidebar thread context menu ("Rename worktree"; note the renamed label already showing in the bottom bar):

Design

• Keyed by worktree PATH, not per-thread, so threads sharing a worktree always show the same name.
• Stored in a persisted worktreeLabelByPath map in useUiStateStore (local UI state).
• A single resolver — worktreeDisplayName(path, labelMap) = labelMap[path] ?? formatWorktreePathForDisplay(path) — is used everywhere a worktree name renders, so the UI stays consistent.
• The rename UI is a single, globally-mounted dialog (WorktreeRenameDialog) driven by a small worktreeRenameStore, so every entry point opens the same dialog and writes the same path-keyed label.

Rename entry points

• Sidebar thread context menu → "Rename worktree" (only for worktree-backed threads).
• Bottom-bar workspace label: double-click, or right-click → "Rename worktree" (desktop + mobile).

Leaving the field blank resets to the default hash-derived name. The label persists across reloads.

Where labels surface

• Bottom-bar workspace label (desktop BranchToolbarEnvModeSelector + mobile MobileRunContextSelector).
• Orphan-worktree delete confirmation dialog.

Tests

• worktreeDisplayName (label / fallback / blank / trim).
• setWorktreeLabel reducer (set / trim / clear / sibling independence) + persistence round-trip.
• Custom-label cases for resolveCurrentWorkspaceLabel / resolveLockedWorkspaceLabel.

pnpm typecheck and vp lint clean; full web unit suite passes (1057 tests). Verified manually in the running app: rename from all entry points, shared label across two threads on the same worktree, blank-resets-to-default, and persistence across reload.

🤖 Generated with Claude Code

---

Note

Low Risk
Client-only persisted UI labels and rename flows; worktree deletion still uses existing VCS APIs, with label cleanup on successful remove.

Overview
Adds cosmetic worktree display names keyed by environment and worktree path, persisted in local UI state and shared by every thread on that worktree (no disk/git changes).

A global WorktreeRenameDialog plus worktreeRenameStore lets users set or clear labels from the sidebar thread menu (Rename worktree), or from the bottom-bar workspace label via double-click or right-click (useWorktreeRenameTrigger). BranchToolbar / BranchToolbarEnvModeSelector read labels through useWorktreeLabel and pass them into resolveCurrentWorkspaceLabel / resolveLockedWorkspaceLabel.

worktreeDisplayName and formatWorktreeDeleteConfirmation use custom labels in orphan-worktree delete prompts; successful worktree removal clears the stored label. Unit tests cover label persistence, resolver behavior, rename trigger context-menu fallback, and display helpers.

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

Note

Add custom display labels for worktrees in the branch toolbar and sidebar

• Introduces a global WorktreeRenameDialog (via useWorktreeRenameStore) that lets users set or clear a cosmetic label for any active worktree, accessible via double-click, right-click context menu, or the sidebar thread context menu.
• Adds worktreeLabelByEnvironment to uiStateStore, persisted to localStorage and keyed by environment ID and worktree path.
• Updates BranchToolbarEnvModeSelector and BranchToolbar.MobileRunContextSelector to display the custom label when set, falling back to existing defaults ('Current worktree' / 'Worktree').
• Extends worktree delete flow in useThreadActions to show the custom label in confirmation text and clear the stored label on successful deletion.

^{Macroscope summarized 64f86a9.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 9ce56739-357c-4b92-9003-5c4b1b0fc4c5

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature (custom worktree labels) with new UI components, state management, and persistence logic. New features warrant human review, and there's an unresolved comment about potential data migration issues.

^{You can customize Macroscope's approvability policy. Learn more.}

[cursor]

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

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

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

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

[cursor]

Path-only label persistence dropped

Medium Severity

The parsePersistedState function was updated to expect the new worktreeLabelByEnvironment structure, but it no longer reads the prior worktreeLabelByPath format from the t3code:ui-state:v1 localStorage key. This causes existing custom worktree names to be lost on load and overwritten on the next state persistence.

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

[juliusmarminge]

Closing as part of backlog cleanup: this PR is stale, currently conflicting with main, has no approval, and has not had active remediation for 30+ days. If the change is still relevant, please rebase onto current main and request reopening or submit a focused current diff. Thank you for the contribution.

[TheIcarusWings]

What

Lets a worktree carry a readable display name instead of the auto-generated hash folder name (e.g. t3code-f07cb2c5). The label is cosmetic only — no git worktree move, no disk changes.

Screenshots

Bottom-bar workspace label — before vs. after renaming the worktree:

Default (hash-derived)	Custom label

Rename dialog (opened from the bottom-bar label or the sidebar):

Entry point — sidebar thread context menu ("Rename worktree"; note the renamed label already showing in the bottom bar):

Design

• Keyed by worktree PATH, not per-thread, so threads sharing a worktree always show the same name.
• Stored in a persisted worktreeLabelByPath map in useUiStateStore (local UI state).
• A single resolver — worktreeDisplayName(path, labelMap) = labelMap[path] ?? formatWorktreePathForDisplay(path) — is used everywhere a worktree name renders, so the UI stays consistent.
• The rename UI is a single, globally-mounted dialog (WorktreeRenameDialog) driven by a small worktreeRenameStore, so every entry point opens the same dialog and writes the same path-keyed label.

Rename entry points

• Sidebar thread context menu → "Rename worktree" (only for worktree-backed threads).
• Bottom-bar workspace label: double-click, or right-click → "Rename worktree" (desktop + mobile).

Leaving the field blank resets to the default hash-derived name. The label persists across reloads.

Where labels surface

• Bottom-bar workspace label (desktop BranchToolbarEnvModeSelector + mobile MobileRunContextSelector).
• Orphan-worktree delete confirmation dialog.

Tests

• worktreeDisplayName (label / fallback / blank / trim).
• setWorktreeLabel reducer (set / trim / clear / sibling independence) + persistence round-trip.
• Custom-label cases for resolveCurrentWorkspaceLabel / resolveLockedWorkspaceLabel.

pnpm typecheck and vp lint clean; full web unit suite passes (1057 tests). Verified manually in the running app: rename from all entry points, shared label across two threads on the same worktree, blank-resets-to-default, and persistence across reload.

🤖 Generated with Claude Code

---

Note

Low Risk
Client-only persisted UI labels and rename flows; worktree deletion still uses existing VCS APIs, with label cleanup on successful remove.

Overview
Adds cosmetic worktree display names keyed by environment and worktree path, persisted in local UI state and shared by every thread on that worktree (no disk/git changes).

A global WorktreeRenameDialog plus worktreeRenameStore lets users set or clear labels from the sidebar thread menu (Rename worktree), or from the bottom-bar workspace label via double-click or right-click (useWorktreeRenameTrigger). BranchToolbar / BranchToolbarEnvModeSelector read labels through useWorktreeLabel and pass them into resolveCurrentWorkspaceLabel / resolveLockedWorkspaceLabel.

worktreeDisplayName and formatWorktreeDeleteConfirmation use custom labels in orphan-worktree delete prompts; successful worktree removal clears the stored label. Unit tests cover label persistence, resolver behavior, rename trigger context-menu fallback, and display helpers.

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

Note

Add custom display labels for worktrees in the branch toolbar and sidebar

• Introduces a global WorktreeRenameDialog (via useWorktreeRenameStore) that lets users set or clear a cosmetic label for any active worktree, accessible via double-click, right-click context menu, or the sidebar thread context menu.
• Adds worktreeLabelByEnvironment to uiStateStore, persisted to localStorage and keyed by environment ID and worktree path.
• Updates BranchToolbarEnvModeSelector and BranchToolbar.MobileRunContextSelector to display the custom label when set, falling back to existing defaults ('Current worktree' / 'Worktree').
• Extends worktree delete flow in useThreadActions to show the custom label in confirmation text and clear the stored label on successful deletion.

^{Macroscope summarized 64f86a9.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 9ce56739-357c-4b92-9003-5c4b1b0fc4c5

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature (custom worktree labels) with new UI components, state management, and persistence logic. New features warrant human review, and there's an unresolved comment about potential data migration issues.

^{You can customize Macroscope's approvability policy. Learn more.}

[cursor]

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

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

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

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

[cursor]

Path-only label persistence dropped

Medium Severity

The parsePersistedState function was updated to expect the new worktreeLabelByEnvironment structure, but it no longer reads the prior worktreeLabelByPath format from the t3code:ui-state:v1 localStorage key. This causes existing custom worktree names to be lost on load and overwritten on the next state persistence.

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

[juliusmarminge]

Closing as part of backlog cleanup: this PR is stale, currently conflicting with main, has no approval, and has not had active remediation for 30+ days. If the change is still relevant, please rebase onto current main and request reopening or submit a focused current diff. Thank you for the contribution.

[TheIcarusWings]

What

Lets a worktree carry a readable display name instead of the auto-generated hash folder name (e.g. t3code-f07cb2c5). The label is cosmetic only — no git worktree move, no disk changes.

Screenshots

Bottom-bar workspace label — before vs. after renaming the worktree:

Default (hash-derived)	Custom label

Rename dialog (opened from the bottom-bar label or the sidebar):

Entry point — sidebar thread context menu ("Rename worktree"; note the renamed label already showing in the bottom bar):

Design

• Keyed by worktree PATH, not per-thread, so threads sharing a worktree always show the same name.
• Stored in a persisted worktreeLabelByPath map in useUiStateStore (local UI state).
• A single resolver — worktreeDisplayName(path, labelMap) = labelMap[path] ?? formatWorktreePathForDisplay(path) — is used everywhere a worktree name renders, so the UI stays consistent.
• The rename UI is a single, globally-mounted dialog (WorktreeRenameDialog) driven by a small worktreeRenameStore, so every entry point opens the same dialog and writes the same path-keyed label.

Rename entry points

• Sidebar thread context menu → "Rename worktree" (only for worktree-backed threads).
• Bottom-bar workspace label: double-click, or right-click → "Rename worktree" (desktop + mobile).

Leaving the field blank resets to the default hash-derived name. The label persists across reloads.

Where labels surface

• Bottom-bar workspace label (desktop BranchToolbarEnvModeSelector + mobile MobileRunContextSelector).
• Orphan-worktree delete confirmation dialog.

Tests

• worktreeDisplayName (label / fallback / blank / trim).
• setWorktreeLabel reducer (set / trim / clear / sibling independence) + persistence round-trip.
• Custom-label cases for resolveCurrentWorkspaceLabel / resolveLockedWorkspaceLabel.

pnpm typecheck and vp lint clean; full web unit suite passes (1057 tests). Verified manually in the running app: rename from all entry points, shared label across two threads on the same worktree, blank-resets-to-default, and persistence across reload.

🤖 Generated with Claude Code

---

Note

Low Risk
Client-only persisted UI labels and rename flows; worktree deletion still uses existing VCS APIs, with label cleanup on successful remove.

Overview
Adds cosmetic worktree display names keyed by environment and worktree path, persisted in local UI state and shared by every thread on that worktree (no disk/git changes).

A global WorktreeRenameDialog plus worktreeRenameStore lets users set or clear labels from the sidebar thread menu (Rename worktree), or from the bottom-bar workspace label via double-click or right-click (useWorktreeRenameTrigger). BranchToolbar / BranchToolbarEnvModeSelector read labels through useWorktreeLabel and pass them into resolveCurrentWorkspaceLabel / resolveLockedWorkspaceLabel.

worktreeDisplayName and formatWorktreeDeleteConfirmation use custom labels in orphan-worktree delete prompts; successful worktree removal clears the stored label. Unit tests cover label persistence, resolver behavior, rename trigger context-menu fallback, and display helpers.

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

Note

Add custom display labels for worktrees in the branch toolbar and sidebar

• Introduces a global WorktreeRenameDialog (via useWorktreeRenameStore) that lets users set or clear a cosmetic label for any active worktree, accessible via double-click, right-click context menu, or the sidebar thread context menu.
• Adds worktreeLabelByEnvironment to uiStateStore, persisted to localStorage and keyed by environment ID and worktree path.
• Updates BranchToolbarEnvModeSelector and BranchToolbar.MobileRunContextSelector to display the custom label when set, falling back to existing defaults ('Current worktree' / 'Worktree').
• Extends worktree delete flow in useThreadActions to show the custom label in confirmation text and clear the stored label on successful deletion.

^{Macroscope summarized 64f86a9.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 9ce56739-357c-4b92-9003-5c4b1b0fc4c5

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature (custom worktree labels) with new UI components, state management, and persistence logic. New features warrant human review, and there's an unresolved comment about potential data migration issues.

^{You can customize Macroscope's approvability policy. Learn more.}

[cursor]

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

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

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

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

[cursor]

Path-only label persistence dropped

Medium Severity

The parsePersistedState function was updated to expect the new worktreeLabelByEnvironment structure, but it no longer reads the prior worktreeLabelByPath format from the t3code:ui-state:v1 localStorage key. This causes existing custom worktree names to be lost on load and overwritten on the next state persistence.

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

[juliusmarminge]

Closing as part of backlog cleanup: this PR is stale, currently conflicting with main, has no approval, and has not had active remediation for 30+ days. If the change is still relevant, please rebase onto current main and request reopening or submit a focused current diff. Thank you for the contribution.

[TheIcarusWings]

What

Lets a worktree carry a readable display name instead of the auto-generated hash folder name (e.g. t3code-f07cb2c5). The label is cosmetic only — no git worktree move, no disk changes.

Screenshots

Bottom-bar workspace label — before vs. after renaming the worktree:

Default (hash-derived)	Custom label

Rename dialog (opened from the bottom-bar label or the sidebar):

Entry point — sidebar thread context menu ("Rename worktree"; note the renamed label already showing in the bottom bar):

Design

• Keyed by worktree PATH, not per-thread, so threads sharing a worktree always show the same name.
• Stored in a persisted worktreeLabelByPath map in useUiStateStore (local UI state).
• A single resolver — worktreeDisplayName(path, labelMap) = labelMap[path] ?? formatWorktreePathForDisplay(path) — is used everywhere a worktree name renders, so the UI stays consistent.
• The rename UI is a single, globally-mounted dialog (WorktreeRenameDialog) driven by a small worktreeRenameStore, so every entry point opens the same dialog and writes the same path-keyed label.

Rename entry points

• Sidebar thread context menu → "Rename worktree" (only for worktree-backed threads).
• Bottom-bar workspace label: double-click, or right-click → "Rename worktree" (desktop + mobile).

Leaving the field blank resets to the default hash-derived name. The label persists across reloads.

Where labels surface

• Bottom-bar workspace label (desktop BranchToolbarEnvModeSelector + mobile MobileRunContextSelector).
• Orphan-worktree delete confirmation dialog.

Tests

• worktreeDisplayName (label / fallback / blank / trim).
• setWorktreeLabel reducer (set / trim / clear / sibling independence) + persistence round-trip.
• Custom-label cases for resolveCurrentWorkspaceLabel / resolveLockedWorkspaceLabel.

pnpm typecheck and vp lint clean; full web unit suite passes (1057 tests). Verified manually in the running app: rename from all entry points, shared label across two threads on the same worktree, blank-resets-to-default, and persistence across reload.

🤖 Generated with Claude Code

---

Note

Low Risk
Client-only persisted UI labels and rename flows; worktree deletion still uses existing VCS APIs, with label cleanup on successful remove.

Overview
Adds cosmetic worktree display names keyed by environment and worktree path, persisted in local UI state and shared by every thread on that worktree (no disk/git changes).

A global WorktreeRenameDialog plus worktreeRenameStore lets users set or clear labels from the sidebar thread menu (Rename worktree), or from the bottom-bar workspace label via double-click or right-click (useWorktreeRenameTrigger). BranchToolbar / BranchToolbarEnvModeSelector read labels through useWorktreeLabel and pass them into resolveCurrentWorkspaceLabel / resolveLockedWorkspaceLabel.

worktreeDisplayName and formatWorktreeDeleteConfirmation use custom labels in orphan-worktree delete prompts; successful worktree removal clears the stored label. Unit tests cover label persistence, resolver behavior, rename trigger context-menu fallback, and display helpers.

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

Note

Add custom display labels for worktrees in the branch toolbar and sidebar

• Introduces a global WorktreeRenameDialog (via useWorktreeRenameStore) that lets users set or clear a cosmetic label for any active worktree, accessible via double-click, right-click context menu, or the sidebar thread context menu.
• Adds worktreeLabelByEnvironment to uiStateStore, persisted to localStorage and keyed by environment ID and worktree path.
• Updates BranchToolbarEnvModeSelector and BranchToolbar.MobileRunContextSelector to display the custom label when set, falling back to existing defaults ('Current worktree' / 'Worktree').
• Extends worktree delete flow in useThreadActions to show the custom label in confirmation text and clear the stored label on successful deletion.

^{Macroscope summarized 64f86a9.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 9ce56739-357c-4b92-9003-5c4b1b0fc4c5

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature (custom worktree labels) with new UI components, state management, and persistence logic. New features warrant human review, and there's an unresolved comment about potential data migration issues.

^{You can customize Macroscope's approvability policy. Learn more.}

[cursor]

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

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

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

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

[cursor]

Path-only label persistence dropped

Medium Severity

The parsePersistedState function was updated to expect the new worktreeLabelByEnvironment structure, but it no longer reads the prior worktreeLabelByPath format from the t3code:ui-state:v1 localStorage key. This causes existing custom worktree names to be lost on load and overwritten on the next state persistence.

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

[juliusmarminge]

Closing as part of backlog cleanup: this PR is stale, currently conflicting with main, has no approval, and has not had active remediation for 30+ days. If the change is still relevant, please rebase onto current main and request reopening or submit a focused current diff. Thank you for the contribution.

[TheIcarusWings]

What

Lets a worktree carry a readable display name instead of the auto-generated hash folder name (e.g. t3code-f07cb2c5). The label is cosmetic only — no git worktree move, no disk changes.

Screenshots

Bottom-bar workspace label — before vs. after renaming the worktree:

Default (hash-derived)	Custom label

Rename dialog (opened from the bottom-bar label or the sidebar):

Entry point — sidebar thread context menu ("Rename worktree"; note the renamed label already showing in the bottom bar):

Design

• Keyed by worktree PATH, not per-thread, so threads sharing a worktree always show the same name.
• Stored in a persisted worktreeLabelByPath map in useUiStateStore (local UI state).
• A single resolver — worktreeDisplayName(path, labelMap) = labelMap[path] ?? formatWorktreePathForDisplay(path) — is used everywhere a worktree name renders, so the UI stays consistent.
• The rename UI is a single, globally-mounted dialog (WorktreeRenameDialog) driven by a small worktreeRenameStore, so every entry point opens the same dialog and writes the same path-keyed label.

Rename entry points

• Sidebar thread context menu → "Rename worktree" (only for worktree-backed threads).
• Bottom-bar workspace label: double-click, or right-click → "Rename worktree" (desktop + mobile).

Leaving the field blank resets to the default hash-derived name. The label persists across reloads.

Where labels surface

• Bottom-bar workspace label (desktop BranchToolbarEnvModeSelector + mobile MobileRunContextSelector).
• Orphan-worktree delete confirmation dialog.

Tests

• worktreeDisplayName (label / fallback / blank / trim).
• setWorktreeLabel reducer (set / trim / clear / sibling independence) + persistence round-trip.
• Custom-label cases for resolveCurrentWorkspaceLabel / resolveLockedWorkspaceLabel.

pnpm typecheck and vp lint clean; full web unit suite passes (1057 tests). Verified manually in the running app: rename from all entry points, shared label across two threads on the same worktree, blank-resets-to-default, and persistence across reload.

🤖 Generated with Claude Code

---

Note

Low Risk
Client-only persisted UI labels and rename flows; worktree deletion still uses existing VCS APIs, with label cleanup on successful remove.

Overview
Adds cosmetic worktree display names keyed by environment and worktree path, persisted in local UI state and shared by every thread on that worktree (no disk/git changes).

A global WorktreeRenameDialog plus worktreeRenameStore lets users set or clear labels from the sidebar thread menu (Rename worktree), or from the bottom-bar workspace label via double-click or right-click (useWorktreeRenameTrigger). BranchToolbar / BranchToolbarEnvModeSelector read labels through useWorktreeLabel and pass them into resolveCurrentWorkspaceLabel / resolveLockedWorkspaceLabel.

worktreeDisplayName and formatWorktreeDeleteConfirmation use custom labels in orphan-worktree delete prompts; successful worktree removal clears the stored label. Unit tests cover label persistence, resolver behavior, rename trigger context-menu fallback, and display helpers.

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

Note

Add custom display labels for worktrees in the branch toolbar and sidebar

• Introduces a global WorktreeRenameDialog (via useWorktreeRenameStore) that lets users set or clear a cosmetic label for any active worktree, accessible via double-click, right-click context menu, or the sidebar thread context menu.
• Adds worktreeLabelByEnvironment to uiStateStore, persisted to localStorage and keyed by environment ID and worktree path.
• Updates BranchToolbarEnvModeSelector and BranchToolbar.MobileRunContextSelector to display the custom label when set, falling back to existing defaults ('Current worktree' / 'Worktree').
• Extends worktree delete flow in useThreadActions to show the custom label in confirmation text and clear the stored label on successful deletion.

^{Macroscope summarized 64f86a9.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 9ce56739-357c-4b92-9003-5c4b1b0fc4c5

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature (custom worktree labels) with new UI components, state management, and persistence logic. New features warrant human review, and there's an unresolved comment about potential data migration issues.

^{You can customize Macroscope's approvability policy. Learn more.}

[cursor]

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

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

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

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

[cursor]

Path-only label persistence dropped

Medium Severity

The parsePersistedState function was updated to expect the new worktreeLabelByEnvironment structure, but it no longer reads the prior worktreeLabelByPath format from the t3code:ui-state:v1 localStorage key. This causes existing custom worktree names to be lost on load and overwritten on the next state persistence.

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

[juliusmarminge]

Closing as part of backlog cleanup: this PR is stale, currently conflicting with main, has no approval, and has not had active remediation for 30+ days. If the change is still relevant, please rebase onto current main and request reopening or submit a focused current diff. Thank you for the contribution.

[TheIcarusWings]

What

Lets a worktree carry a readable display name instead of the auto-generated hash folder name (e.g. t3code-f07cb2c5). The label is cosmetic only — no git worktree move, no disk changes.

Screenshots

Bottom-bar workspace label — before vs. after renaming the worktree:

Default (hash-derived)	Custom label

Rename dialog (opened from the bottom-bar label or the sidebar):

Entry point — sidebar thread context menu ("Rename worktree"; note the renamed label already showing in the bottom bar):

Design

• Keyed by worktree PATH, not per-thread, so threads sharing a worktree always show the same name.
• Stored in a persisted worktreeLabelByPath map in useUiStateStore (local UI state).
• A single resolver — worktreeDisplayName(path, labelMap) = labelMap[path] ?? formatWorktreePathForDisplay(path) — is used everywhere a worktree name renders, so the UI stays consistent.
• The rename UI is a single, globally-mounted dialog (WorktreeRenameDialog) driven by a small worktreeRenameStore, so every entry point opens the same dialog and writes the same path-keyed label.

Rename entry points

• Sidebar thread context menu → "Rename worktree" (only for worktree-backed threads).
• Bottom-bar workspace label: double-click, or right-click → "Rename worktree" (desktop + mobile).

Leaving the field blank resets to the default hash-derived name. The label persists across reloads.

Where labels surface

• Bottom-bar workspace label (desktop BranchToolbarEnvModeSelector + mobile MobileRunContextSelector).
• Orphan-worktree delete confirmation dialog.

Tests

• worktreeDisplayName (label / fallback / blank / trim).
• setWorktreeLabel reducer (set / trim / clear / sibling independence) + persistence round-trip.
• Custom-label cases for resolveCurrentWorkspaceLabel / resolveLockedWorkspaceLabel.

pnpm typecheck and vp lint clean; full web unit suite passes (1057 tests). Verified manually in the running app: rename from all entry points, shared label across two threads on the same worktree, blank-resets-to-default, and persistence across reload.

🤖 Generated with Claude Code

---

Note

Low Risk
Client-only persisted UI labels and rename flows; worktree deletion still uses existing VCS APIs, with label cleanup on successful remove.

Overview
Adds cosmetic worktree display names keyed by environment and worktree path, persisted in local UI state and shared by every thread on that worktree (no disk/git changes).

A global WorktreeRenameDialog plus worktreeRenameStore lets users set or clear labels from the sidebar thread menu (Rename worktree), or from the bottom-bar workspace label via double-click or right-click (useWorktreeRenameTrigger). BranchToolbar / BranchToolbarEnvModeSelector read labels through useWorktreeLabel and pass them into resolveCurrentWorkspaceLabel / resolveLockedWorkspaceLabel.

worktreeDisplayName and formatWorktreeDeleteConfirmation use custom labels in orphan-worktree delete prompts; successful worktree removal clears the stored label. Unit tests cover label persistence, resolver behavior, rename trigger context-menu fallback, and display helpers.

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

Note

Add custom display labels for worktrees in the branch toolbar and sidebar

• Introduces a global WorktreeRenameDialog (via useWorktreeRenameStore) that lets users set or clear a cosmetic label for any active worktree, accessible via double-click, right-click context menu, or the sidebar thread context menu.
• Adds worktreeLabelByEnvironment to uiStateStore, persisted to localStorage and keyed by environment ID and worktree path.
• Updates BranchToolbarEnvModeSelector and BranchToolbar.MobileRunContextSelector to display the custom label when set, falling back to existing defaults ('Current worktree' / 'Worktree').
• Extends worktree delete flow in useThreadActions to show the custom label in confirmation text and clear the stored label on successful deletion.

^{Macroscope summarized 64f86a9.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 9ce56739-357c-4b92-9003-5c4b1b0fc4c5

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature (custom worktree labels) with new UI components, state management, and persistence logic. New features warrant human review, and there's an unresolved comment about potential data migration issues.

^{You can customize Macroscope's approvability policy. Learn more.}

[cursor]

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

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

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

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

[cursor]

Path-only label persistence dropped

Medium Severity

The parsePersistedState function was updated to expect the new worktreeLabelByEnvironment structure, but it no longer reads the prior worktreeLabelByPath format from the t3code:ui-state:v1 localStorage key. This causes existing custom worktree names to be lost on load and overwritten on the next state persistence.

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

[juliusmarminge]

Closing as part of backlog cleanup: this PR is stale, currently conflicting with main, has no approval, and has not had active remediation for 30+ days. If the change is still relevant, please rebase onto current main and request reopening or submit a focused current diff. Thank you for the contribution.