[Feature]: store preference setting for permission mode

[pedro757]

Before submitting

• I searched existing issues and did not find a duplicate.
• I am describing a concrete problem or use case, not just a vague idea.

Area

apps/web

Problem or use case

This always resets to Full Access when creating a new thread

Proposed solution

Add a field in setting for default permission mode

Why this matters

Always asking the same question is annoying

Smallest useful scope

store the default setting

Alternatives considered

No response

Risks or tradeoffs

No response

Examples or references

No response

Contribution

• I would be open to helping implement this.

[benglewis]

@juliusmarminge Is this being considered? Could PR #3086 be considered? This is a blocker for my usage and I would prefer to use a blessed upstream version than maintain a fork with this behavior for my own usage alone

[robertnisipeanu]

I am preparing a focused contribution with a narrower shape than the closed global-only implementation in #3086.

Proposed scope: keep one configurable server fallback, plus optional defaults keyed by configured provider instance. Fresh threads resolve an explicit draft choice first, then the selected provider-instance default, then the server fallback. New chats will not inherit the permission mode of the currently viewed thread. Switching providers updates only an implicit mode; a mode explicitly chosen in that draft stays fixed. Existing threads, continuations, resumed sessions, and provider-native subagents remain unchanged. Web/desktop and mobile creation paths will both consume the server setting.

This allows configurations such as Codex = Auto and Claude = Full access without applying one permission policy indiscriminately to every provider.