[FEATURE] Improved permission system or sandboxing on windows

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Our company is currently using Cursor for most day-to-day development, and I would like to migrate developers to Claude Code.

The main blocker right now is the permissions and sandboxing experience on Windows. Even with a strong allowlist in place, Claude Code still prompts for approval too frequently, which creates a lot of friction for developers. While I personally use “skip permissions” in private workflows, that is not a viable option in a company environment.

Moving to a Windows WSL-based sandbox would also be a much bigger operational change for us, so it is not an easy workaround.

The core issue is that this level of interruption does not seem to exist to the same extent in competing tools. In Cursor, this is much less disruptive, and even Codex CLI feels smoother and requires fewer confirmations. Claude Code needs a better approach here, because this is currently blocking adoption.

Proposed Solution

Review how competing tools handle permissions and sandboxing, especially on Windows, and improve the experience to at least match that level of usability.

I prefer Claude Code over Codex overall, but the current permission flow is a blocking issue for rollout in a company setting.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_