[ENHANCEMENT] Per mode auto-approve.

[AI-Vectoring]

Problem (one or two sentences)

auto-approve settings are rarely the same for all modes.

Context (who is affected and when)

auto-approving something for my coder mode also changes the setting for any other mode.

Desired behavior (conceptual, not technical)

auto-approve is global by default, but i get a toggle or a setting to make it specific to the current mode.
This could be implemented in different ways...

Constraints / preferences (optional)

No response

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

[roomote-v0]

I've analyzed this issue and here's my proposed implementation plan for per-mode auto-approve settings:

Current Architecture

Auto-approve settings (alwaysAllowReadOnly, alwaysAllowWrite, alwaysAllowExecute, alwaysAllowMcp, alwaysAllowModeSwitch, alwaysAllowSubtasks, alwaysAllowFollowupQuestions, plus related options like allowedCommands, deniedCommands, autoApprovalEnabled, etc.) are stored as flat fields in GlobalSettings (packages/types/src/global-settings.ts). They are checked in src/core/auto-approval/index.ts via checkAutoApproval() which reads from the global ExtensionState. The same values apply regardless of which mode (code, architect, ask, debug, etc.) is active.

Meanwhile, the codebase already supports per-mode API config profiles via modeApiConfigs and ProviderSettingsManager.setModeConfig/getModeConfigId, so there is precedent for mode-specific settings.

Proposed Approach

Add a new modeAutoApproveOverrides field to GlobalSettings that maps mode slugs to per-mode auto-approve overrides. When a user opts into per-mode auto-approve for a given mode, that mode gets its own set of auto-approve flags. Otherwise, the global defaults apply (backward-compatible).

1. Types (packages/types/src/global-settings.ts)

Add a new schema and field:

const modeAutoApproveSchema = z.object({
  autoApprovalEnabled: z.boolean().optional(),
  alwaysAllowReadOnly: z.boolean().optional(),
  alwaysAllowReadOnlyOutsideWorkspace: z.boolean().optional(),
  alwaysAllowWrite: z.boolean().optional(),
  alwaysAllowWriteOutsideWorkspace: z.boolean().optional(),
  alwaysAllowWriteProtected: z.boolean().optional(),
  alwaysAllowExecute: z.boolean().optional(),
  alwaysAllowMcp: z.boolean().optional(),
  alwaysAllowModeSwitch: z.boolean().optional(),
  alwaysAllowSubtasks: z.boolean().optional(),
  alwaysAllowFollowupQuestions: z.boolean().optional(),
  followupAutoApproveTimeoutMs: z.number().optional(),
  allowedCommands: z.array(z.string()).optional(),
  deniedCommands: z.array(z.string()).optional(),
  allowedMaxRequests: z.number().nullish(),
  allowedMaxCost: z.number().nullish(),
})

// Add to globalSettingsSchema:
modeAutoApproveOverrides: z.record(z.string(), modeAutoApproveSchema).optional(),

2. Auto-approval resolution (src/core/auto-approval/index.ts)

Update checkAutoApproval() to accept the current mode slug and the overrides map. When checking a flag, if the current mode has an override entry, use those values (falling back to the global value for any field not explicitly set in the override).

3. State wiring (src/core/webview/ClineProvider.ts)

• Include modeAutoApproveOverrides in getStateToPostToWebview() and pass the resolved (merged) auto-approve state to checkAutoApproval().
• When saving auto-approve settings, if per-mode is enabled for the current mode, write to the mode-specific override instead of the global settings.

4. Webview UI

• Settings panel (webview-ui/src/components/settings/AutoApproveSettings.tsx): Add a toggle/indicator like "Use per-mode settings" near the top of the auto-approve section. When enabled, the settings shown and saved apply only to the current mode. Add a visual indicator of which mode the settings apply to.
• Chat dropdown (webview-ui/src/components/settings/AutoApproveDropdown.tsx): When per-mode overrides are active, show the resolved values for the current mode rather than the global values.
• Toggle bar (webview-ui/src/components/settings/AutoApproveToggle.tsx): Toggling individual auto-approve flags should save to the mode override when per-mode is enabled.

5. Import/Export (src/core/config/importExport.ts)

Include modeAutoApproveOverrides in the settings export/import flow so per-mode auto-approve settings survive backup/restore.

6. Tests

• Unit tests for the override merge logic in src/core/auto-approval/
• Unit tests for the UI components reflecting per-mode state
• Ensure backward compatibility (no overrides = existing behavior unchanged)

Benefits

• Fully backward-compatible: no overrides means everything works as before
• Follows the existing pattern of modeApiConfigs for per-mode settings
• Users can opt in per-mode without being forced to configure every mode
• Global settings remain the default fallback

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.