[BUG] Claude ignored the definition in settings.json to not create a new branch when assisting in code

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

I came across this small bug where Claude-Code ignores the settings defined in its folder (eg.: user/.claude)
The setting defined was to not allow Claude-Code to create new branches spontaneously as it was assisting coding in a closed project with a defined branch to work on.
It ignored the settings once, so I restarted Claude (desktop app) and started a new thread. Yet, it keep ignoring the configuration defined.

The settings used:

"autoCommit": false,
 "createBranchPerTask": false

Claude itself acknowledged that it ignored that configuration and recommended me to open a bug.

What Should Happen?

Claude should have respected the configuration in its settings file and not created automatic branches to work and then asked that branch to be merged with main/master.
It should have respected the current branch set, as it once did, and kept the work within its boundaries.
The configurations in its settings file were trampled over.

Error Messages/Logs

Steps to Reproduce

Include the settings as follows in the settings.json, in a user/.claude folder.

"autoCommit": false,
 "createBranchPerTask": false

Have a project with any Git versioning system.
Create a new branch.
Open the Claude app for Windows (Windows 11).
Start any thread with any coding request.

Claude will create an automatic branch, work the changes in said branch, and open it to be merged in master/main

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

v1.6608.1

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

_No response_