Move project settings to contextual project routes

[juliusmarminge]

What Changed

• Moved project settings from /settings/projects to contextual /projects/$projectKey routes.
• Updated sidebar and command palette navigation to open settings for the relevant project.
• Reworked the settings page with breadcrumb navigation, project switching, Escape/back behavior, and checkout-specific script configuration.
• Updated project rename and deletion flows for the new route structure.
• Removed obsolete forked-rollout usage suppression and related tests, restored the usage cache version, and simplified asset response headers.
• Cleaned up the mobile control-pill handling and adjusted related server tests.

Why

Project settings are tied to a specific project, so they should open in the project context instead of through a separate settings listing. This keeps navigation consistent with the sidebar and command palette, supports grouped projects and individual checkouts more clearly, and avoids dead-end states after regrouping or deletion. The accompanying cleanup removes behavior that is no longer intended for usage scanning and simplifies related code paths.

UI Changes

Project settings now render as a contextual project page with a breadcrumb and project selector. Sidebar and command palette actions now link directly to the selected project. No before/after screenshots or video are included.

Before

After

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

Note

Move project settings from /settings/projects to contextual /projects/:projectKey routes

• Project settings are now served at /projects/$projectKey instead of /settings/projects, with a breadcrumb header and Escape-to-go-back behavior.
• The command palette 'Project settings' action and the sidebar per-project button both navigate to the new route, resolving the project from the current context.
• The 'Projects' section is removed from the settings sidebar nav and settings search index.
• Within the settings panel, scripts/actions and keybindings now apply only to the selected checkout rather than all members; group-wide rename updates all members' titles.
• Behavioral Change: /settings/projects routes are deleted; any bookmarks or direct links to those paths will no longer resolve.

^{Macroscope summarized b4840e8.}

---

Note

Medium Risk
Routing and deep-link breakage for old /settings/projects URLs, plus script/keybinding persistence now scoped per checkout instead of fan-out to all members—behavior change reviewers should validate for multi-checkout groups.

Overview
Project settings leave the global Settings area and become a dedicated /projects/$projectKey page (auth-gated). The old /settings/projects routes are removed, along with the Projects item in settings nav and settings search.

Navigation now targets the relevant project: the sidebar uses a Settings control (replacing the ellipsis) to open that route; the command palette Project settings action only appears when a contextual project exists and navigates to /projects/$projectKey, showing the project name as the description.

The UI is rebuilt around ProjectSettingsPage: workspace titlebar/breadcrumb with a project switcher, Escape / back to leave (home if no history). Group-level name, icon, default model, and new-thread workspace stay shared across checkouts; scripts/actions and keybindings are edited for the selected checkout only. Checkout section adds path copy, grouping override, optional remove-checkout, and import-from-t3.json menu. Deleting the whole group redirects to / instead of a projects listing.

Grouping labels: when all members share a custom title that is not the repo display/name, that title is used as the group label (tests added).

SettingsRow description is now optional.

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

[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: 2bc4ba8c-0c66-4830-8cd1-cab9e1a5b692

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

---

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

[cursor]

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

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

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

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.3 KiB	11.3 KiB	+17 B (+0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.5 KiB	5.5 KiB	+9 B (+0.2%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	5.9 KiB	+8 B (+0.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	49.7 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	16	16	0 (0.0%)	21	✅
Claude	Total thread wire	11.3 KiB	11.3 KiB	0 B (0.0%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	5.5 KiB	+2 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	5.9 KiB	−2 B (−0.0%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	50.6 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	16	16	0 (0.0%)	21	✅

Baseline: 9a1472d · PR result: b4840e8 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 94.6 KiB
• Claude decoded thread snapshot: 95.4 KiB

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

[macroscopeapp]

Approvability

Verdict: Needs human review

1 blocking correctness issue found. This PR restructures project settings routing and UI. Two unresolved review comments identify potential bugs: incorrect keybinding atom usage for non-primary environments, and a rename field that may incorrectly overwrite member titles. These correctness concerns warrant human review.

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