Add configurable default access mode for new threads

[JustMarkDev]

What Changed

Added a persisted defaultRuntimeMode client setting and exposed it in apps/web settings UI as Default access. New draft threads now initialize with that setting instead of always starting in full-access.

Also updated the relevant settings and persistence tests to cover the new field.

Why

This makes the app remember the user’s preferred permission mode for new threads, so they do not have to reselect it every time. The change is scoped to client-side defaults and preserves existing behavior for saved data by falling back to the current full-access default when the new setting is absent.

UI Changes

Progetto.senza.titolo.mp4

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

Closes #2662

---

Note

Medium Risk
Changes the default permission mode for newly created threads, which affects how much autonomy agents get on first send; mitigated by unchanged schema default and no retroactive changes to existing threads.

Overview
Adds a persisted defaultRuntimeMode client setting and a Default access control in settings (Supervised, Auto-accept edits, Full access).

New draft threads and composer fallbacks now use that preference instead of always full-access. Existing saved settings without the field still decode to the same DEFAULT_RUNTIME_MODE (full-access), so behavior for users who never change the setting stays the same.

Wiring updates ChatView, useHandleNewThread, and related persistence tests; DEFAULT_RUNTIME_MODE is no longer imported directly in those paths for new-thread defaults.

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

Note

Add configurable default access mode for new threads in General Settings

• Adds a defaultRuntimeMode field to ClientSettings and ClientSettingsPatch in settings.ts, defaulting to DEFAULT_RUNTIME_MODE.
• Adds a "Default access" selector to the General Settings panel in SettingsPanels.tsx, with support for reset and restore-defaults.
• Updates ChatView.tsx and useHandleNewThread.ts to initialize new draft threads with settings.defaultRuntimeMode instead of the hard-coded DEFAULT_RUNTIME_MODE.
• Behavioral Change: existing sessions where defaultRuntimeMode is unset continue to use DEFAULT_RUNTIME_MODE via the decode fallback, so existing threads are unaffected.

^{Macroscope summarized f25091f.}

[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: ee8aa382-c5d6-494c-a754-79ecd2bb3612

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 allowing configuration of the default access/permission mode for new threads. While well-implemented with tests, new features that add user-configurable behavior affecting runtime permissions warrant human review.

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