Claude Code no longer asks permission? Return to Manual and set the default mode

Why execution became automatic after upgrading

If the current indicator shows Auto, switch back to Manual, then configure the next session's starting mode separately. Claude Code's v2.1.284 release notes on September 28, 2026 state that the Auto default for terminal and VS Code interactive sessions without a configured permission mode expanded to all plans and providers. This is not a new policy launched on October 4, nor does it grant access to previously ineligible accounts.

Current permission documentation summarizes the built-in Auto default for interactive sessions as applying from v2.1.283 onward. Actual startup may still depend on existing settings, organizational policy, model support, and the first session after upgrading. Auto uses a classifier to check actions; it does not mean permission checks are completely bypassed. This article focuses on local terminals and the VS Code panel, without applying the same rule to all SDK, desktop, and cloud sessions.

Terminal: confirm focus before returning to Manual

In the normal conversation input interface, pressing Shift+Tab once from Auto enters Manual. Check that the status bar says manual mode on before continuing the task. Do not press repeatedly without looking for the target mode; every press may enter a different mode.

If a file-permission dialog is open, handle it first: Esc can reject the current request. Switch modes after returning to the normal input interface. In that dialog, Shift+Tab may close the comment input or select an option allowing operations for the session, unlike its meaning at normal input. Interrupting with Esc also does not undo completed work.

Confirm “the mode switched” separately from “whether earlier actions occurred.” Inspect existing changes before deciding on subsequent work; changing permissions is not a file rollback. This article is based on official documentation and has not installed or tested the client.

Terminal: start the next session in Manual too

To specify a single launch, run claude --permission-mode default. The CLI reference says --permission-mode determines the permission mode for that session; default corresponds to Manual in the interface. Confirming behavior with an explicit launch argument helps distinguish session behavior from persistent configuration.

To make future terminal sessions use it by default, set "defaultMode": "default" inside the permissions object of the user-level ~/.claude/settings.json. Merge this field while retaining the file's other settings; do not overwrite the original file with an empty configuration. The official settings reference says this field applies to new sessions, while the current launch's --permission-mode argument takes precedence.

After saving, create a new session and check the mode indicator before resuming the original task. Record which file you changed and which launch arguments you used. If old and new sessions differ, you then have a concrete comparison without repeatedly reinstalling.

VS Code: handle panel settings separately from the integrated terminal

In the extension's chat panel, click the mode indicator below the input box and select Manual. To fix the initial mode for new conversations, set claudeCode.initialPermissionMode to default in VS Code user settings. The extension reads this only from User settings; workspace values are ignored. Writing it into the project's .claude/settings.json does not establish that the extension has applied it.

The extension panel bundles its own CLI, while claude in the integrated terminal is a separate usage path. Identify whether you are operating the panel or terminal and inspect the corresponding version. In Manual, the panel generally shows file diffs for approval, but exact behavior still depends on permission rules.

Open a new panel conversation to verify its initial mode and record that separately from the integrated-terminal result. If only one is fixed, continue checking the other interface's own setting rather than combining both into a single issue.

Why an action may still run without asking in Manual

Permission mode establishes only the baseline behavior. Official permission guidance says Allow rules let specified tools run without manual approval, Ask rules require a prompt, and Deny rules block execution. Evaluation order is Deny, Ask, Allow. Manual therefore does not mean every read or already-authorized action must display a prompt.

Use /permissions to inspect effective rules and their source files. Find the specific tool and matching rule first, then decide whether that authorization needs changing. “It did not ask me” is insufficient to locate the cause. Record the mode, tool name, and matching rule together. Do not clear every allow and deny setting merely to restore one prompt.

For help, provide the version, interface, mode, and a redacted rule excerpt. Do not include keys, complete environment files, or client material. Have administrators compare actual and intended policy for organization-managed settings.

Confirm the result at two checkpoints

The first checkpoint is the current session: the indicator shows Manual, and you understand which earlier changes were completed. The second is a new session: restarting through the usual entry point still shows the expected mode. This is a suggested troubleshooting sequence, not a test result obtained for this article.

If only a new session returns to Auto, prioritize launch arguments and configuration scope. If the mode is correct but one tool runs directly, return to rule matching. Separate these two cases before changing the corresponding settings, rather than mixing client upgrades, session state, and individual tool authorization.