Add per-project settings (wip)#2567
Conversation
- add project details/settings RPCs and persistence - use project remote overrides for source control detection - add project details page and sidebar navigation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
ApprovabilityVerdict: Needs human review 2 blocking correctness issues found. This PR introduces a new per-project settings feature with a new UI page, new RPC endpoints, schema changes, and modifications to source control provider detection. New features of this scope require human review, and there are three unresolved review comments identifying potential bugs in the new code. You can customize Macroscope's approvability policy. Learn more. |
- Replace sidebar rename action with project settings access - Show detected remotes and project path in settings - Extract remote override parsing into shared server helper
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes 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 c5048e6. Configure here.

Suggested PR title:
Add per-project settings and remote overridesWhat Changed
Added a per-project settings page that can be opened from the project row in the sidebar.
/projects/$projectIdWhy
Git remote detection can fail for self-hosted providers where the remote URL does not clearly identify the host, such as a self-hosted GitLab instance without
gitlab.comin the URL.This gives users a project-level fallback instead of requiring the app to guess correctly. The project name change is also scoped to T3 Code metadata only; it does not rename or move the directory on disk.
UI Changes
Checklist
Note
Medium Risk
Adds new persisted per-project settings and changes source-control provider detection to honor user overrides, which could affect Git/provider resolution across workflows if mapping to the correct project/root is wrong.
Overview
Adds per-project settings persisted in server settings (
ServerSettings.projectSettings) and exposes them via new WS RPCsprojects.getDetailsandprojects.updateSettings.Introduces a new web route
/projects/$projectIdfor viewing/editing project name and configuring a manual Git remote/provider override, and updates the sidebar so clicking a project navigates to this page while a separate caret button controls expand/collapse.Updates source-control provider resolution to prefer the per-project
remoteOverride(with newRemoteOverrideparsing/helpers) before falling back to detecting from Git remotes, and wires this into bothSourceControlProviderRegistryandGitManagerhosting-provider detection.Reviewed by Cursor Bugbot for commit c5048e6. Bugbot is set up for automated code reviews on this repo. Configure here.
Note
Add per-project settings with remote override configuration and project settings route
/projects/$projectIdsettings page in the web UI where users can view detected git info (branch, remotes) and configure a manual remote override (provider, URL, web URL) and project title.projects.getDetailsandprojects.updateSettingsWebSocket RPC endpoints backed by on-demand git inspection andServerSettingsService.ServerSettingswith aprojectSettingsmap keyed by project ID, storingProjectRemoteOverrideand related fields.SourceControlProviderRegistrynow checks per-project remote overrides before falling back to git remote inference.Macroscope summarized c5048e6.