feat(settings): add shared project defaults and scoped overrides

[maria-rcks]

project settings live in settings → projects, with machine tabs and a project dropdown. machine defaults apply unless a project overrides them; reset restores inheritance.

shared action persistence now handles defaults and checkout overrides once, removing 147 lines of duplicated save, shortcut, and editor logic without adding a helper module. the layout and shared-default behavior are preserved. merged main without rewriting branch history and updated the existing projection test mock. review fixes preserve defaults in settings search, native script menus, bootstrap threads, and onboarding imports. the final net code reduction is 101 lines. the patch remains large: 37 files, +2,220/-643 versus the starting 35 files, +2,204/-526; code reuse and review fixes add line churn despite reducing the code.

verified web/server/mobile typechecks, 117 focused tests, real-browser default create/edit plus project inherit → override → delete → reset, and both settings-search entry points. targeted lint reports existing warnings in untouched code. both reviewers approve toggle fix 9d1b9a871. ci is blocked by the new main-branch IntegrationsSettings.test.tsx rendering a settings link without a router; toggle typecheck, lint, and live checks pass.

before

original layout capture, using the earlier project fixture.

after

automatically pull now disables only its own setting while saving. verified both toggle directions with a live disabled-attribute observer: workspace, model, and browser controls remain active; the name and icon rows remain muted. web typecheck and targeted lint pass.

action persistence after trimming

recorded the interaction walkthrough, but its file is on the desktop browser host and cannot be retrieved from this environment. video transfer and playback remain unverified. native simulator runtime was not exercised; evidence is not complete.

built with gpt-5.6-sol in t3 code.

---

Note

Medium Risk
Changes effective auto-pull, setup scripts, and agent browser MCP issuance based on new server settings and projection lookups; misconfiguration or missing settings layers could alter background git behavior or tool access for running sessions.

Overview
Introduces Settings → Projects with machine and project scope pickers, replacing the standalone project settings route (which now redirects). All projects edits machine-wide defaults; selecting a project configures per-checkout overrides with inherit/reset semantics.

Server settings gain defaultModelSelection, defaultProjectScripts, defaultAutoPull, and per-project override maps for scripts, auto-pull, and agent browser access. Web, mobile, and server paths resolve effective values via resolveProjectScripts, resolveProjectAutoPull, and resolveProjectAgentBrowserAccess instead of relying only on project records.

Project actions are persisted as projectScriptOverrides on the server (null resets to defaults); setup scripts on worktree create use the same resolution. Auto-pull at startup and in VCS status refresh now consults server settings layers. Agent MCP browser credentials are issued or revoked based on the thread’s project override, not just the global toggle.

Composer and new-thread flows fall back to the target environment’s defaultModelSelection and workspace defaults. General/Integrations settings link out to Projects for model, workspace, and browser access; defaultThreadEnvMode is no longer synced as a shared preference across machines.

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

Note

Add shared project defaults and per-project scoped overrides for scripts, browser access, auto-pull, and model selection

• Introduces a new /settings/projects page with scope pickers for configuring defaults across all projects or overrides for a specific project and machine
• Adds server-side resolvers (resolveProjectScripts, resolveProjectAgentBrowserAccess, resolveProjectAutoPull) that layer per-project overrides on top of server-wide defaults; applyServerSettingsPatch merges override maps entry-by-entry so omitted projects are preserved
• Moves inline settings from General and Integrations pages (New threads workspace mode, Agent browser access) into the projects settings page; old /projects/:projectKey route now redirects to /settings/projects\n- Model selection now falls back to the environment's server-configured defaultModelSelection when a project has no explicit model, affecting bootstrap, new-thread creation, draft hero, and mobile new-task flow
• Reclassifies defaultThreadEnvMode as a machine-local setting in SHARED_SERVER_SETTING_KEYS, removing it from shared-settings patching and comparison
• Risk: ProviderService.makeProviderService now requires ProjectionSnapshotQuery to resolve project browser-access overrides; provider-only runtimes or unresolved threads with configured project overrides return false for browser access. ProjectSetupScriptRunner.make now requires ServerSettingsService and returns a typed ProjectSetupScriptOperationError with readSettings on settings-load failure

^{Macroscope summarized c663ec2.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This is a large product feature introducing persisted machine/project defaults and overrides that affect thread creation, automatic pulls, browser credentials, and worktree setup actions across web, mobile, and server runtimes. The broad behavior change and unresolved risks around bootstrap failure, partial multi-machine saves, and discarded actions require human review.

Not approved because:

• 3 blocking correctness issues found at or above your repo's Minimum Blocking Severity

^{Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.}

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Cursor Bugbot has reviewed your changes using default 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 767464a. Configure here.}

[cursor]

Bugbot is paused — on-demand spend limit reached

Bugbot uses usage-based billing for this team and has hit its on-demand spend limit.

A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue.

[cursor]

Bugbot is paused — on-demand spend limit reached

Bugbot uses usage-based billing for this team and has hit its on-demand spend limit.

A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue.

[macroscopeapp]

🟡 Medium src/serverRuntimeStartup.ts:203

A getSettings failure now aborts resolveAutoBootstrapWelcomeTargets before it looks up or creates the CWD project/thread, so an unavailable redacted provider secret leaves completeAutoBootstrapWelcome publishing a completed payload with no bootstrap targets. Read the settings with a fallback to getAutoBootstrapThreadModelSelection() when materialization fails.

-    const settings = yield* (yield* ServerSettings.ServerSettingsService).getSettings;
-    const defaultModelSelection =
-      settings.defaultModelSelection ?? getAutoBootstrapThreadModelSelection();
+    const settings = yield* (yield* ServerSettings.ServerSettingsService).getSettings.pipe(
+      Effect.catchAll(() => Effect.succeed(undefined)),
+    );
+    const defaultModelSelection =
+      settings?.defaultModelSelection ?? getAutoBootstrapThreadModelSelection();

🤖 Copy this AI Prompt to have your agent fix this:

In file @apps/server/src/serverRuntimeStartup.ts around lines 203-205:

A `getSettings` failure now aborts `resolveAutoBootstrapWelcomeTargets` before it looks up or creates the CWD project/thread, so an unavailable redacted provider secret leaves `completeAutoBootstrapWelcome` publishing a completed payload with no bootstrap targets. Read the settings with a fallback to `getAutoBootstrapThreadModelSelection()` when materialization fails.

[macroscopeapp]

🟡 Medium settings/ProjectDefaultActionsSettings.tsx:38

A multi-machine save can leave permanently divergent default actions when a later updateSettings fails: earlier machines are updated, but the failed machine is not. Retrying Add action then appends again on the already-updated machines while applying only the retry's action to the failed machine. Make useProjectScriptSettings roll back prior updates on failure or make the operation idempotent.

🤖 Copy this AI Prompt to have your agent fix this:

In file @apps/web/src/components/settings/ProjectDefaultActionsSettings.tsx around line 38:

A multi-machine save can leave permanently divergent default actions when a later `updateSettings` fails: earlier machines are updated, but the failed machine is not. Retrying `Add action` then appends again on the already-updated machines while applying only the retry's action to the failed machine. Make `useProjectScriptSettings` roll back prior updates on failure or make the operation idempotent.

[macroscopeapp]

🟡 Medium components/ChatView.tsx:7907

Unprojected threads now receive activeProjectScripts=[], so ProjectScriptsControl renders its “Add action” button even though saveProjectScript exits successfully without persisting when activeProject is absent. Users can therefore create an action that is silently discarded; preserve undefined when no project is active (or disable editing in that state).

Suggested change

	activeProjectScripts={activeProjectScripts}
	activeProjectScripts={activeProject ? activeProjectScripts : undefined}

🤖 Copy this AI Prompt to have your agent fix this:

In file @apps/web/src/components/ChatView.tsx around line 7907:

Unprojected threads now receive `activeProjectScripts=[]`, so `ProjectScriptsControl` renders its “Add action” button even though `saveProjectScript` exits successfully without persisting when `activeProject` is absent. Users can therefore create an action that is silently discarded; preserve `undefined` when no project is active (or disable editing in that state).