Make worktree placement configurable

[colonelpanic8]

What Changed

• Add a persisted worktreePathTemplate server setting.
• Expand {worktreesDir}, {repoRoot}, {repoName}, and {branch} when creating worktrees.
• Keep {worktreesDir}/{repoName}/{branch} as the default, preserving the existing centralized layout.
• Add a General settings control with a one-click reset to the default.
• Apply the setting to new-session, explicit VCS, and pull-request worktree creation flows.
• Normalize relative repository roots and allow review previews for worktrees matching the configured template.

Why

Some users keep worktrees alongside each repository, while others prefer T3 Code's centralized worktree directory. A configurable template supports both layouts without changing existing behavior.

For example, {repoRoot}/.worktrees/{branch} creates repository-local worktrees.

UI Changes

The General settings panel now exposes the worktree path template and documents its available variables. Browser verification covered the default value, persisting a repository-local template, and resetting to the default.

Default centralized template	Repository-local template persisted after reload

These current screenshots were recaptured from PR head 366d6e021814242392c778d49fd195397a8cbf11 in the combined package 0.0.29-patched-main-20260724 (integration 4dd4cef4039303179929a1dbdbf0c9b358c076f9).

Checklist

• pnpm exec vp test run packages/contracts/src/settings.test.ts apps/server/src/serverSettings.test.ts apps/server/src/vcs/GitVcsDriverCore.test.ts apps/server/src/server.test.ts -t 'bootstraps first-send worktree turns|ServerSettings worktree path template|ServerSettingsPatch string normalization|server settings|uses the configured repository-local worktree path template|keeps the centralized worktree path as the default' (21 passed)
• pnpm exec vp test run apps/server/src/review/ReviewService.test.ts apps/server/src/vcs/GitVcsDriverCore.test.ts (40 passed)
• Targeted vp check for the final review-fix files (no warnings)
• pnpm exec vp check (passes with 12 pre-existing warnings in untouched files)
• pnpm --filter t3 typecheck
• pnpm --filter @t3tools/contracts typecheck
• Integrated web verification in an isolated authenticated environment against the exact combined package; default value, repository-local edit, and persistence after reload verified
• pnpm exec vp run typecheck (workspace baseline fails in untouched web/mobile files: existing implicit-any and unknown AtomRegistry errors; the affected server and contracts package checks pass)

---

Note

Medium Risk
Touches worktree creation, review path sandboxing, and persisted settings across Git/VCS/WS layers; default template preserves prior behavior but misconfigured templates or template-matching edge cases could block previews or place worktrees unexpectedly.

Overview
Adds a persisted worktreePathTemplate server setting (default {worktreesDir}/{repoName}/{branch}) with a General settings field to edit and reset it.

Worktree creation no longer hardcodes the centralized layout: GitVcsDriverCore.createWorktree resolves paths via new resolveWorktreePathTemplate / matchesWorktreePathTemplate helpers, and bootstrap, VCS RPC, and PR-thread flows pass the setting (with fallback on read failure).

Review diff preview widens allowed cwd values: besides the workspace and legacy worktrees dir, paths under persisted thread worktrees or paths matching the template against active project repo roots are accepted. The WS handler loads getActiveProjectWorkspaceRoots and getActiveThreadWorktreePaths from projection SQL (without shell snapshot hydration) and forwards them to ReviewService.

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

Note

Make worktree placement configurable via a path template setting

• Adds a worktreePathTemplate field to ServerSettings (default: {worktreesDir}/{repoName}/{branch}) with UI controls in the General settings panel to view, edit, and reset it.
• GitVcsDriverCore.createWorktree and GitWorkflowService.createWorktree now accept an optional pathTemplate and resolve the worktree path by expanding template placeholders ({worktreesDir}, {repoRoot}, {repoName}, {branch}) instead of using a hardcoded path join.
• New resolveWorktreePathTemplate and matchesWorktreePathTemplate utilities in worktreePathTemplate.ts handle expansion and pattern matching against candidate paths.
• ReviewService.getDiffPreview now accepts optional repositoryRoots and knownWorktreePaths; workspace boundary validation allows cwds inside known worktree paths or matching the configured template against any provided repository root.
• ProjectionSnapshotQuery gains getActiveProjectWorkspaceRoots and getActiveThreadWorktreePaths methods, which the WS RPC layer uses to supply these paths to the review service.
• Risk: createWorktree may now fail earlier with a GitCommandError if repository root canonicalization fails when no explicit path is given.

^{Macroscope summarized b8aa507.}

[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 Plus

Run ID: 9ef36ed5-f453-4078-94cb-59ef58caf1d5

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.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature (configurable worktree path templates) with new settings UI, path template resolution logic, and validation changes across multiple services. New features that introduce user-facing behavior warrant human review.

^{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.}

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

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

Configurable worktree placement changes path ownership, cleanup, revival, and collision behavior. That risk is too large for a location preference while #4742 is handling worktree inventory and cleanup.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

[colonelpanic8]

What Changed

• Add a persisted worktreePathTemplate server setting.
• Expand {worktreesDir}, {repoRoot}, {repoName}, and {branch} when creating worktrees.
• Keep {worktreesDir}/{repoName}/{branch} as the default, preserving the existing centralized layout.
• Add a General settings control with a one-click reset to the default.
• Apply the setting to new-session, explicit VCS, and pull-request worktree creation flows.
• Normalize relative repository roots and allow review previews for worktrees matching the configured template.

Why

Some users keep worktrees alongside each repository, while others prefer T3 Code's centralized worktree directory. A configurable template supports both layouts without changing existing behavior.

For example, {repoRoot}/.worktrees/{branch} creates repository-local worktrees.

UI Changes

The General settings panel now exposes the worktree path template and documents its available variables. Browser verification covered the default value, persisting a repository-local template, and resetting to the default.

Default centralized template	Repository-local template persisted after reload

These current screenshots were recaptured from PR head 366d6e021814242392c778d49fd195397a8cbf11 in the combined package 0.0.29-patched-main-20260724 (integration 4dd4cef4039303179929a1dbdbf0c9b358c076f9).

Checklist

• pnpm exec vp test run packages/contracts/src/settings.test.ts apps/server/src/serverSettings.test.ts apps/server/src/vcs/GitVcsDriverCore.test.ts apps/server/src/server.test.ts -t 'bootstraps first-send worktree turns|ServerSettings worktree path template|ServerSettingsPatch string normalization|server settings|uses the configured repository-local worktree path template|keeps the centralized worktree path as the default' (21 passed)
• pnpm exec vp test run apps/server/src/review/ReviewService.test.ts apps/server/src/vcs/GitVcsDriverCore.test.ts (40 passed)
• Targeted vp check for the final review-fix files (no warnings)
• pnpm exec vp check (passes with 12 pre-existing warnings in untouched files)
• pnpm --filter t3 typecheck
• pnpm --filter @t3tools/contracts typecheck
• Integrated web verification in an isolated authenticated environment against the exact combined package; default value, repository-local edit, and persistence after reload verified
• pnpm exec vp run typecheck (workspace baseline fails in untouched web/mobile files: existing implicit-any and unknown AtomRegistry errors; the affected server and contracts package checks pass)

---

Note

Medium Risk
Touches worktree creation, review path sandboxing, and persisted settings across Git/VCS/WS layers; default template preserves prior behavior but misconfigured templates or template-matching edge cases could block previews or place worktrees unexpectedly.

Overview
Adds a persisted worktreePathTemplate server setting (default {worktreesDir}/{repoName}/{branch}) with a General settings field to edit and reset it.

Worktree creation no longer hardcodes the centralized layout: GitVcsDriverCore.createWorktree resolves paths via new resolveWorktreePathTemplate / matchesWorktreePathTemplate helpers, and bootstrap, VCS RPC, and PR-thread flows pass the setting (with fallback on read failure).

Review diff preview widens allowed cwd values: besides the workspace and legacy worktrees dir, paths under persisted thread worktrees or paths matching the template against active project repo roots are accepted. The WS handler loads getActiveProjectWorkspaceRoots and getActiveThreadWorktreePaths from projection SQL (without shell snapshot hydration) and forwards them to ReviewService.

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

Note

Make worktree placement configurable via a path template setting

• Adds a worktreePathTemplate field to ServerSettings (default: {worktreesDir}/{repoName}/{branch}) with UI controls in the General settings panel to view, edit, and reset it.
• GitVcsDriverCore.createWorktree and GitWorkflowService.createWorktree now accept an optional pathTemplate and resolve the worktree path by expanding template placeholders ({worktreesDir}, {repoRoot}, {repoName}, {branch}) instead of using a hardcoded path join.
• New resolveWorktreePathTemplate and matchesWorktreePathTemplate utilities in worktreePathTemplate.ts handle expansion and pattern matching against candidate paths.
• ReviewService.getDiffPreview now accepts optional repositoryRoots and knownWorktreePaths; workspace boundary validation allows cwds inside known worktree paths or matching the configured template against any provided repository root.
• ProjectionSnapshotQuery gains getActiveProjectWorkspaceRoots and getActiveThreadWorktreePaths methods, which the WS RPC layer uses to supply these paths to the review service.
• Risk: createWorktree may now fail earlier with a GitCommandError if repository root canonicalization fails when no explicit path is given.

^{Macroscope summarized b8aa507.}

[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 Plus

Run ID: 9ef36ed5-f453-4078-94cb-59ef58caf1d5

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.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature (configurable worktree path templates) with new settings UI, path template resolution logic, and validation changes across multiple services. New features that introduce user-facing behavior warrant human review.

^{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.}

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

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

Configurable worktree placement changes path ownership, cleanup, revival, and collision behavior. That risk is too large for a location preference while #4742 is handling worktree inventory and cleanup.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

[colonelpanic8]

What Changed

• Add a persisted worktreePathTemplate server setting.
• Expand {worktreesDir}, {repoRoot}, {repoName}, and {branch} when creating worktrees.
• Keep {worktreesDir}/{repoName}/{branch} as the default, preserving the existing centralized layout.
• Add a General settings control with a one-click reset to the default.
• Apply the setting to new-session, explicit VCS, and pull-request worktree creation flows.
• Normalize relative repository roots and allow review previews for worktrees matching the configured template.

Why

Some users keep worktrees alongside each repository, while others prefer T3 Code's centralized worktree directory. A configurable template supports both layouts without changing existing behavior.

For example, {repoRoot}/.worktrees/{branch} creates repository-local worktrees.

UI Changes

The General settings panel now exposes the worktree path template and documents its available variables. Browser verification covered the default value, persisting a repository-local template, and resetting to the default.

Default centralized template	Repository-local template persisted after reload

These current screenshots were recaptured from PR head 366d6e021814242392c778d49fd195397a8cbf11 in the combined package 0.0.29-patched-main-20260724 (integration 4dd4cef4039303179929a1dbdbf0c9b358c076f9).

Checklist

• pnpm exec vp test run packages/contracts/src/settings.test.ts apps/server/src/serverSettings.test.ts apps/server/src/vcs/GitVcsDriverCore.test.ts apps/server/src/server.test.ts -t 'bootstraps first-send worktree turns|ServerSettings worktree path template|ServerSettingsPatch string normalization|server settings|uses the configured repository-local worktree path template|keeps the centralized worktree path as the default' (21 passed)
• pnpm exec vp test run apps/server/src/review/ReviewService.test.ts apps/server/src/vcs/GitVcsDriverCore.test.ts (40 passed)
• Targeted vp check for the final review-fix files (no warnings)
• pnpm exec vp check (passes with 12 pre-existing warnings in untouched files)
• pnpm --filter t3 typecheck
• pnpm --filter @t3tools/contracts typecheck
• Integrated web verification in an isolated authenticated environment against the exact combined package; default value, repository-local edit, and persistence after reload verified
• pnpm exec vp run typecheck (workspace baseline fails in untouched web/mobile files: existing implicit-any and unknown AtomRegistry errors; the affected server and contracts package checks pass)

---

Note

Medium Risk
Touches worktree creation, review path sandboxing, and persisted settings across Git/VCS/WS layers; default template preserves prior behavior but misconfigured templates or template-matching edge cases could block previews or place worktrees unexpectedly.

Overview
Adds a persisted worktreePathTemplate server setting (default {worktreesDir}/{repoName}/{branch}) with a General settings field to edit and reset it.

Worktree creation no longer hardcodes the centralized layout: GitVcsDriverCore.createWorktree resolves paths via new resolveWorktreePathTemplate / matchesWorktreePathTemplate helpers, and bootstrap, VCS RPC, and PR-thread flows pass the setting (with fallback on read failure).

Review diff preview widens allowed cwd values: besides the workspace and legacy worktrees dir, paths under persisted thread worktrees or paths matching the template against active project repo roots are accepted. The WS handler loads getActiveProjectWorkspaceRoots and getActiveThreadWorktreePaths from projection SQL (without shell snapshot hydration) and forwards them to ReviewService.

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

Note

Make worktree placement configurable via a path template setting

• Adds a worktreePathTemplate field to ServerSettings (default: {worktreesDir}/{repoName}/{branch}) with UI controls in the General settings panel to view, edit, and reset it.
• GitVcsDriverCore.createWorktree and GitWorkflowService.createWorktree now accept an optional pathTemplate and resolve the worktree path by expanding template placeholders ({worktreesDir}, {repoRoot}, {repoName}, {branch}) instead of using a hardcoded path join.
• New resolveWorktreePathTemplate and matchesWorktreePathTemplate utilities in worktreePathTemplate.ts handle expansion and pattern matching against candidate paths.
• ReviewService.getDiffPreview now accepts optional repositoryRoots and knownWorktreePaths; workspace boundary validation allows cwds inside known worktree paths or matching the configured template against any provided repository root.
• ProjectionSnapshotQuery gains getActiveProjectWorkspaceRoots and getActiveThreadWorktreePaths methods, which the WS RPC layer uses to supply these paths to the review service.
• Risk: createWorktree may now fail earlier with a GitCommandError if repository root canonicalization fails when no explicit path is given.

^{Macroscope summarized b8aa507.}

[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 Plus

Run ID: 9ef36ed5-f453-4078-94cb-59ef58caf1d5

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.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature (configurable worktree path templates) with new settings UI, path template resolution logic, and validation changes across multiple services. New features that introduce user-facing behavior warrant human review.

^{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.}

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

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

Configurable worktree placement changes path ownership, cleanup, revival, and collision behavior. That risk is too large for a location preference while #4742 is handling worktree inventory and cleanup.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

[colonelpanic8]

What Changed

• Add a persisted worktreePathTemplate server setting.
• Expand {worktreesDir}, {repoRoot}, {repoName}, and {branch} when creating worktrees.
• Keep {worktreesDir}/{repoName}/{branch} as the default, preserving the existing centralized layout.
• Add a General settings control with a one-click reset to the default.
• Apply the setting to new-session, explicit VCS, and pull-request worktree creation flows.
• Normalize relative repository roots and allow review previews for worktrees matching the configured template.

Why

Some users keep worktrees alongside each repository, while others prefer T3 Code's centralized worktree directory. A configurable template supports both layouts without changing existing behavior.

For example, {repoRoot}/.worktrees/{branch} creates repository-local worktrees.

UI Changes

The General settings panel now exposes the worktree path template and documents its available variables. Browser verification covered the default value, persisting a repository-local template, and resetting to the default.

Default centralized template	Repository-local template persisted after reload

These current screenshots were recaptured from PR head 366d6e021814242392c778d49fd195397a8cbf11 in the combined package 0.0.29-patched-main-20260724 (integration 4dd4cef4039303179929a1dbdbf0c9b358c076f9).

Checklist

• pnpm exec vp test run packages/contracts/src/settings.test.ts apps/server/src/serverSettings.test.ts apps/server/src/vcs/GitVcsDriverCore.test.ts apps/server/src/server.test.ts -t 'bootstraps first-send worktree turns|ServerSettings worktree path template|ServerSettingsPatch string normalization|server settings|uses the configured repository-local worktree path template|keeps the centralized worktree path as the default' (21 passed)
• pnpm exec vp test run apps/server/src/review/ReviewService.test.ts apps/server/src/vcs/GitVcsDriverCore.test.ts (40 passed)
• Targeted vp check for the final review-fix files (no warnings)
• pnpm exec vp check (passes with 12 pre-existing warnings in untouched files)
• pnpm --filter t3 typecheck
• pnpm --filter @t3tools/contracts typecheck
• Integrated web verification in an isolated authenticated environment against the exact combined package; default value, repository-local edit, and persistence after reload verified
• pnpm exec vp run typecheck (workspace baseline fails in untouched web/mobile files: existing implicit-any and unknown AtomRegistry errors; the affected server and contracts package checks pass)

---

Note

Medium Risk
Touches worktree creation, review path sandboxing, and persisted settings across Git/VCS/WS layers; default template preserves prior behavior but misconfigured templates or template-matching edge cases could block previews or place worktrees unexpectedly.

Overview
Adds a persisted worktreePathTemplate server setting (default {worktreesDir}/{repoName}/{branch}) with a General settings field to edit and reset it.

Worktree creation no longer hardcodes the centralized layout: GitVcsDriverCore.createWorktree resolves paths via new resolveWorktreePathTemplate / matchesWorktreePathTemplate helpers, and bootstrap, VCS RPC, and PR-thread flows pass the setting (with fallback on read failure).

Review diff preview widens allowed cwd values: besides the workspace and legacy worktrees dir, paths under persisted thread worktrees or paths matching the template against active project repo roots are accepted. The WS handler loads getActiveProjectWorkspaceRoots and getActiveThreadWorktreePaths from projection SQL (without shell snapshot hydration) and forwards them to ReviewService.

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

Note

Make worktree placement configurable via a path template setting

• Adds a worktreePathTemplate field to ServerSettings (default: {worktreesDir}/{repoName}/{branch}) with UI controls in the General settings panel to view, edit, and reset it.
• GitVcsDriverCore.createWorktree and GitWorkflowService.createWorktree now accept an optional pathTemplate and resolve the worktree path by expanding template placeholders ({worktreesDir}, {repoRoot}, {repoName}, {branch}) instead of using a hardcoded path join.
• New resolveWorktreePathTemplate and matchesWorktreePathTemplate utilities in worktreePathTemplate.ts handle expansion and pattern matching against candidate paths.
• ReviewService.getDiffPreview now accepts optional repositoryRoots and knownWorktreePaths; workspace boundary validation allows cwds inside known worktree paths or matching the configured template against any provided repository root.
• ProjectionSnapshotQuery gains getActiveProjectWorkspaceRoots and getActiveThreadWorktreePaths methods, which the WS RPC layer uses to supply these paths to the review service.
• Risk: createWorktree may now fail earlier with a GitCommandError if repository root canonicalization fails when no explicit path is given.

^{Macroscope summarized b8aa507.}

[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 Plus

Run ID: 9ef36ed5-f453-4078-94cb-59ef58caf1d5

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.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature (configurable worktree path templates) with new settings UI, path template resolution logic, and validation changes across multiple services. New features that introduce user-facing behavior warrant human review.

^{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.}

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

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

Configurable worktree placement changes path ownership, cleanup, revival, and collision behavior. That risk is too large for a location preference while #4742 is handling worktree inventory and cleanup.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

[colonelpanic8]

What Changed

• Add a persisted worktreePathTemplate server setting.
• Expand {worktreesDir}, {repoRoot}, {repoName}, and {branch} when creating worktrees.
• Keep {worktreesDir}/{repoName}/{branch} as the default, preserving the existing centralized layout.
• Add a General settings control with a one-click reset to the default.
• Apply the setting to new-session, explicit VCS, and pull-request worktree creation flows.
• Normalize relative repository roots and allow review previews for worktrees matching the configured template.

Why

Some users keep worktrees alongside each repository, while others prefer T3 Code's centralized worktree directory. A configurable template supports both layouts without changing existing behavior.

For example, {repoRoot}/.worktrees/{branch} creates repository-local worktrees.

UI Changes

The General settings panel now exposes the worktree path template and documents its available variables. Browser verification covered the default value, persisting a repository-local template, and resetting to the default.

Default centralized template	Repository-local template persisted after reload

These current screenshots were recaptured from PR head 366d6e021814242392c778d49fd195397a8cbf11 in the combined package 0.0.29-patched-main-20260724 (integration 4dd4cef4039303179929a1dbdbf0c9b358c076f9).

Checklist

• pnpm exec vp test run packages/contracts/src/settings.test.ts apps/server/src/serverSettings.test.ts apps/server/src/vcs/GitVcsDriverCore.test.ts apps/server/src/server.test.ts -t 'bootstraps first-send worktree turns|ServerSettings worktree path template|ServerSettingsPatch string normalization|server settings|uses the configured repository-local worktree path template|keeps the centralized worktree path as the default' (21 passed)
• pnpm exec vp test run apps/server/src/review/ReviewService.test.ts apps/server/src/vcs/GitVcsDriverCore.test.ts (40 passed)
• Targeted vp check for the final review-fix files (no warnings)
• pnpm exec vp check (passes with 12 pre-existing warnings in untouched files)
• pnpm --filter t3 typecheck
• pnpm --filter @t3tools/contracts typecheck
• Integrated web verification in an isolated authenticated environment against the exact combined package; default value, repository-local edit, and persistence after reload verified
• pnpm exec vp run typecheck (workspace baseline fails in untouched web/mobile files: existing implicit-any and unknown AtomRegistry errors; the affected server and contracts package checks pass)

---

Note

Medium Risk
Touches worktree creation, review path sandboxing, and persisted settings across Git/VCS/WS layers; default template preserves prior behavior but misconfigured templates or template-matching edge cases could block previews or place worktrees unexpectedly.

Overview
Adds a persisted worktreePathTemplate server setting (default {worktreesDir}/{repoName}/{branch}) with a General settings field to edit and reset it.

Worktree creation no longer hardcodes the centralized layout: GitVcsDriverCore.createWorktree resolves paths via new resolveWorktreePathTemplate / matchesWorktreePathTemplate helpers, and bootstrap, VCS RPC, and PR-thread flows pass the setting (with fallback on read failure).

Review diff preview widens allowed cwd values: besides the workspace and legacy worktrees dir, paths under persisted thread worktrees or paths matching the template against active project repo roots are accepted. The WS handler loads getActiveProjectWorkspaceRoots and getActiveThreadWorktreePaths from projection SQL (without shell snapshot hydration) and forwards them to ReviewService.

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

Note

Make worktree placement configurable via a path template setting

• Adds a worktreePathTemplate field to ServerSettings (default: {worktreesDir}/{repoName}/{branch}) with UI controls in the General settings panel to view, edit, and reset it.
• GitVcsDriverCore.createWorktree and GitWorkflowService.createWorktree now accept an optional pathTemplate and resolve the worktree path by expanding template placeholders ({worktreesDir}, {repoRoot}, {repoName}, {branch}) instead of using a hardcoded path join.
• New resolveWorktreePathTemplate and matchesWorktreePathTemplate utilities in worktreePathTemplate.ts handle expansion and pattern matching against candidate paths.
• ReviewService.getDiffPreview now accepts optional repositoryRoots and knownWorktreePaths; workspace boundary validation allows cwds inside known worktree paths or matching the configured template against any provided repository root.
• ProjectionSnapshotQuery gains getActiveProjectWorkspaceRoots and getActiveThreadWorktreePaths methods, which the WS RPC layer uses to supply these paths to the review service.
• Risk: createWorktree may now fail earlier with a GitCommandError if repository root canonicalization fails when no explicit path is given.

^{Macroscope summarized b8aa507.}

[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 Plus

Run ID: 9ef36ed5-f453-4078-94cb-59ef58caf1d5

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.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature (configurable worktree path templates) with new settings UI, path template resolution logic, and validation changes across multiple services. New features that introduce user-facing behavior warrant human review.

^{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.}

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

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

Configurable worktree placement changes path ownership, cleanup, revival, and collision behavior. That risk is too large for a location preference while #4742 is handling worktree inventory and cleanup.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

[colonelpanic8]

What Changed

• Add a persisted worktreePathTemplate server setting.
• Expand {worktreesDir}, {repoRoot}, {repoName}, and {branch} when creating worktrees.
• Keep {worktreesDir}/{repoName}/{branch} as the default, preserving the existing centralized layout.
• Add a General settings control with a one-click reset to the default.
• Apply the setting to new-session, explicit VCS, and pull-request worktree creation flows.
• Normalize relative repository roots and allow review previews for worktrees matching the configured template.

Why

Some users keep worktrees alongside each repository, while others prefer T3 Code's centralized worktree directory. A configurable template supports both layouts without changing existing behavior.

For example, {repoRoot}/.worktrees/{branch} creates repository-local worktrees.

UI Changes

The General settings panel now exposes the worktree path template and documents its available variables. Browser verification covered the default value, persisting a repository-local template, and resetting to the default.

Default centralized template	Repository-local template persisted after reload

These current screenshots were recaptured from PR head 366d6e021814242392c778d49fd195397a8cbf11 in the combined package 0.0.29-patched-main-20260724 (integration 4dd4cef4039303179929a1dbdbf0c9b358c076f9).

Checklist

• pnpm exec vp test run packages/contracts/src/settings.test.ts apps/server/src/serverSettings.test.ts apps/server/src/vcs/GitVcsDriverCore.test.ts apps/server/src/server.test.ts -t 'bootstraps first-send worktree turns|ServerSettings worktree path template|ServerSettingsPatch string normalization|server settings|uses the configured repository-local worktree path template|keeps the centralized worktree path as the default' (21 passed)
• pnpm exec vp test run apps/server/src/review/ReviewService.test.ts apps/server/src/vcs/GitVcsDriverCore.test.ts (40 passed)
• Targeted vp check for the final review-fix files (no warnings)
• pnpm exec vp check (passes with 12 pre-existing warnings in untouched files)
• pnpm --filter t3 typecheck
• pnpm --filter @t3tools/contracts typecheck
• Integrated web verification in an isolated authenticated environment against the exact combined package; default value, repository-local edit, and persistence after reload verified
• pnpm exec vp run typecheck (workspace baseline fails in untouched web/mobile files: existing implicit-any and unknown AtomRegistry errors; the affected server and contracts package checks pass)

---

Note

Medium Risk
Touches worktree creation, review path sandboxing, and persisted settings across Git/VCS/WS layers; default template preserves prior behavior but misconfigured templates or template-matching edge cases could block previews or place worktrees unexpectedly.

Overview
Adds a persisted worktreePathTemplate server setting (default {worktreesDir}/{repoName}/{branch}) with a General settings field to edit and reset it.

Worktree creation no longer hardcodes the centralized layout: GitVcsDriverCore.createWorktree resolves paths via new resolveWorktreePathTemplate / matchesWorktreePathTemplate helpers, and bootstrap, VCS RPC, and PR-thread flows pass the setting (with fallback on read failure).

Review diff preview widens allowed cwd values: besides the workspace and legacy worktrees dir, paths under persisted thread worktrees or paths matching the template against active project repo roots are accepted. The WS handler loads getActiveProjectWorkspaceRoots and getActiveThreadWorktreePaths from projection SQL (without shell snapshot hydration) and forwards them to ReviewService.

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

Note

Make worktree placement configurable via a path template setting

• Adds a worktreePathTemplate field to ServerSettings (default: {worktreesDir}/{repoName}/{branch}) with UI controls in the General settings panel to view, edit, and reset it.
• GitVcsDriverCore.createWorktree and GitWorkflowService.createWorktree now accept an optional pathTemplate and resolve the worktree path by expanding template placeholders ({worktreesDir}, {repoRoot}, {repoName}, {branch}) instead of using a hardcoded path join.
• New resolveWorktreePathTemplate and matchesWorktreePathTemplate utilities in worktreePathTemplate.ts handle expansion and pattern matching against candidate paths.
• ReviewService.getDiffPreview now accepts optional repositoryRoots and knownWorktreePaths; workspace boundary validation allows cwds inside known worktree paths or matching the configured template against any provided repository root.
• ProjectionSnapshotQuery gains getActiveProjectWorkspaceRoots and getActiveThreadWorktreePaths methods, which the WS RPC layer uses to supply these paths to the review service.
• Risk: createWorktree may now fail earlier with a GitCommandError if repository root canonicalization fails when no explicit path is given.

^{Macroscope summarized b8aa507.}

[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 Plus

Run ID: 9ef36ed5-f453-4078-94cb-59ef58caf1d5

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.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature (configurable worktree path templates) with new settings UI, path template resolution logic, and validation changes across multiple services. New features that introduce user-facing behavior warrant human review.

^{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.}

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

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

Configurable worktree placement changes path ownership, cleanup, revival, and collision behavior. That risk is too large for a location preference while #4742 is handling worktree inventory and cleanup.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

[colonelpanic8]

What Changed

• Add a persisted worktreePathTemplate server setting.
• Expand {worktreesDir}, {repoRoot}, {repoName}, and {branch} when creating worktrees.
• Keep {worktreesDir}/{repoName}/{branch} as the default, preserving the existing centralized layout.
• Add a General settings control with a one-click reset to the default.
• Apply the setting to new-session, explicit VCS, and pull-request worktree creation flows.
• Normalize relative repository roots and allow review previews for worktrees matching the configured template.

Why

Some users keep worktrees alongside each repository, while others prefer T3 Code's centralized worktree directory. A configurable template supports both layouts without changing existing behavior.

For example, {repoRoot}/.worktrees/{branch} creates repository-local worktrees.

UI Changes

The General settings panel now exposes the worktree path template and documents its available variables. Browser verification covered the default value, persisting a repository-local template, and resetting to the default.

Default centralized template	Repository-local template persisted after reload

These current screenshots were recaptured from PR head 366d6e021814242392c778d49fd195397a8cbf11 in the combined package 0.0.29-patched-main-20260724 (integration 4dd4cef4039303179929a1dbdbf0c9b358c076f9).

Checklist

• pnpm exec vp test run packages/contracts/src/settings.test.ts apps/server/src/serverSettings.test.ts apps/server/src/vcs/GitVcsDriverCore.test.ts apps/server/src/server.test.ts -t 'bootstraps first-send worktree turns|ServerSettings worktree path template|ServerSettingsPatch string normalization|server settings|uses the configured repository-local worktree path template|keeps the centralized worktree path as the default' (21 passed)
• pnpm exec vp test run apps/server/src/review/ReviewService.test.ts apps/server/src/vcs/GitVcsDriverCore.test.ts (40 passed)
• Targeted vp check for the final review-fix files (no warnings)
• pnpm exec vp check (passes with 12 pre-existing warnings in untouched files)
• pnpm --filter t3 typecheck
• pnpm --filter @t3tools/contracts typecheck
• Integrated web verification in an isolated authenticated environment against the exact combined package; default value, repository-local edit, and persistence after reload verified
• pnpm exec vp run typecheck (workspace baseline fails in untouched web/mobile files: existing implicit-any and unknown AtomRegistry errors; the affected server and contracts package checks pass)

---

Note

Medium Risk
Touches worktree creation, review path sandboxing, and persisted settings across Git/VCS/WS layers; default template preserves prior behavior but misconfigured templates or template-matching edge cases could block previews or place worktrees unexpectedly.

Overview
Adds a persisted worktreePathTemplate server setting (default {worktreesDir}/{repoName}/{branch}) with a General settings field to edit and reset it.

Worktree creation no longer hardcodes the centralized layout: GitVcsDriverCore.createWorktree resolves paths via new resolveWorktreePathTemplate / matchesWorktreePathTemplate helpers, and bootstrap, VCS RPC, and PR-thread flows pass the setting (with fallback on read failure).

Review diff preview widens allowed cwd values: besides the workspace and legacy worktrees dir, paths under persisted thread worktrees or paths matching the template against active project repo roots are accepted. The WS handler loads getActiveProjectWorkspaceRoots and getActiveThreadWorktreePaths from projection SQL (without shell snapshot hydration) and forwards them to ReviewService.

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

Note

Make worktree placement configurable via a path template setting

• Adds a worktreePathTemplate field to ServerSettings (default: {worktreesDir}/{repoName}/{branch}) with UI controls in the General settings panel to view, edit, and reset it.
• GitVcsDriverCore.createWorktree and GitWorkflowService.createWorktree now accept an optional pathTemplate and resolve the worktree path by expanding template placeholders ({worktreesDir}, {repoRoot}, {repoName}, {branch}) instead of using a hardcoded path join.
• New resolveWorktreePathTemplate and matchesWorktreePathTemplate utilities in worktreePathTemplate.ts handle expansion and pattern matching against candidate paths.
• ReviewService.getDiffPreview now accepts optional repositoryRoots and knownWorktreePaths; workspace boundary validation allows cwds inside known worktree paths or matching the configured template against any provided repository root.
• ProjectionSnapshotQuery gains getActiveProjectWorkspaceRoots and getActiveThreadWorktreePaths methods, which the WS RPC layer uses to supply these paths to the review service.
• Risk: createWorktree may now fail earlier with a GitCommandError if repository root canonicalization fails when no explicit path is given.

^{Macroscope summarized b8aa507.}

[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 Plus

Run ID: 9ef36ed5-f453-4078-94cb-59ef58caf1d5

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.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature (configurable worktree path templates) with new settings UI, path template resolution logic, and validation changes across multiple services. New features that introduce user-facing behavior warrant human review.

^{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.}

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

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

Configurable worktree placement changes path ownership, cleanup, revival, and collision behavior. That risk is too large for a location preference while #4742 is handling worktree inventory and cleanup.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

[colonelpanic8]

What Changed

• Add a persisted worktreePathTemplate server setting.
• Expand {worktreesDir}, {repoRoot}, {repoName}, and {branch} when creating worktrees.
• Keep {worktreesDir}/{repoName}/{branch} as the default, preserving the existing centralized layout.
• Add a General settings control with a one-click reset to the default.
• Apply the setting to new-session, explicit VCS, and pull-request worktree creation flows.
• Normalize relative repository roots and allow review previews for worktrees matching the configured template.

Why

Some users keep worktrees alongside each repository, while others prefer T3 Code's centralized worktree directory. A configurable template supports both layouts without changing existing behavior.

For example, {repoRoot}/.worktrees/{branch} creates repository-local worktrees.

UI Changes

The General settings panel now exposes the worktree path template and documents its available variables. Browser verification covered the default value, persisting a repository-local template, and resetting to the default.

Default centralized template	Repository-local template persisted after reload

These current screenshots were recaptured from PR head 366d6e021814242392c778d49fd195397a8cbf11 in the combined package 0.0.29-patched-main-20260724 (integration 4dd4cef4039303179929a1dbdbf0c9b358c076f9).

Checklist

• pnpm exec vp test run packages/contracts/src/settings.test.ts apps/server/src/serverSettings.test.ts apps/server/src/vcs/GitVcsDriverCore.test.ts apps/server/src/server.test.ts -t 'bootstraps first-send worktree turns|ServerSettings worktree path template|ServerSettingsPatch string normalization|server settings|uses the configured repository-local worktree path template|keeps the centralized worktree path as the default' (21 passed)
• pnpm exec vp test run apps/server/src/review/ReviewService.test.ts apps/server/src/vcs/GitVcsDriverCore.test.ts (40 passed)
• Targeted vp check for the final review-fix files (no warnings)
• pnpm exec vp check (passes with 12 pre-existing warnings in untouched files)
• pnpm --filter t3 typecheck
• pnpm --filter @t3tools/contracts typecheck
• Integrated web verification in an isolated authenticated environment against the exact combined package; default value, repository-local edit, and persistence after reload verified
• pnpm exec vp run typecheck (workspace baseline fails in untouched web/mobile files: existing implicit-any and unknown AtomRegistry errors; the affected server and contracts package checks pass)

---

Note

Medium Risk
Touches worktree creation, review path sandboxing, and persisted settings across Git/VCS/WS layers; default template preserves prior behavior but misconfigured templates or template-matching edge cases could block previews or place worktrees unexpectedly.

Overview
Adds a persisted worktreePathTemplate server setting (default {worktreesDir}/{repoName}/{branch}) with a General settings field to edit and reset it.

Worktree creation no longer hardcodes the centralized layout: GitVcsDriverCore.createWorktree resolves paths via new resolveWorktreePathTemplate / matchesWorktreePathTemplate helpers, and bootstrap, VCS RPC, and PR-thread flows pass the setting (with fallback on read failure).

Review diff preview widens allowed cwd values: besides the workspace and legacy worktrees dir, paths under persisted thread worktrees or paths matching the template against active project repo roots are accepted. The WS handler loads getActiveProjectWorkspaceRoots and getActiveThreadWorktreePaths from projection SQL (without shell snapshot hydration) and forwards them to ReviewService.

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

Note

Make worktree placement configurable via a path template setting

• Adds a worktreePathTemplate field to ServerSettings (default: {worktreesDir}/{repoName}/{branch}) with UI controls in the General settings panel to view, edit, and reset it.
• GitVcsDriverCore.createWorktree and GitWorkflowService.createWorktree now accept an optional pathTemplate and resolve the worktree path by expanding template placeholders ({worktreesDir}, {repoRoot}, {repoName}, {branch}) instead of using a hardcoded path join.
• New resolveWorktreePathTemplate and matchesWorktreePathTemplate utilities in worktreePathTemplate.ts handle expansion and pattern matching against candidate paths.
• ReviewService.getDiffPreview now accepts optional repositoryRoots and knownWorktreePaths; workspace boundary validation allows cwds inside known worktree paths or matching the configured template against any provided repository root.
• ProjectionSnapshotQuery gains getActiveProjectWorkspaceRoots and getActiveThreadWorktreePaths methods, which the WS RPC layer uses to supply these paths to the review service.
• Risk: createWorktree may now fail earlier with a GitCommandError if repository root canonicalization fails when no explicit path is given.

^{Macroscope summarized b8aa507.}

[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 Plus

Run ID: 9ef36ed5-f453-4078-94cb-59ef58caf1d5

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.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature (configurable worktree path templates) with new settings UI, path template resolution logic, and validation changes across multiple services. New features that introduce user-facing behavior warrant human review.

^{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.}

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

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

Configurable worktree placement changes path ownership, cleanup, revival, and collision behavior. That risk is too large for a location preference while #4742 is handling worktree inventory and cleanup.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.