[BUG] claude config set would write a boolean value as a string into config file.

Resolved 💬 4 comments Opened Sep 26, 2025 by codemee Closed Jan 9, 2026

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?

While Using claude config set -g todoFeatureEnabled false to disable the todo feature, claude code still plan the todo list. After viewing the config file, I found the boolean value false was written as a string "false" so the boolean test is true.

<img width="657" height="319" alt="Image" src="https://github.com/user-attachments/assets/12df06ab-8f36-4fe6-a539-8cf30ee6ecd7" />

You can see the differences from command line output:

➜ claude config get -g todoFeatureEnabled
false
➜ claude config set -g todoFeatureEnabled false
➜ claude config get -g todoFeatureEnabled      
"false"
➜ claude -v
1.0.126 (Claude Code)

In fact, the claude config set write any value as string. This should be corrected or some configures can only be set by editing the config file.

What Should Happen?

The false value should be written as a boolean, not a string.

Error Messages/Logs

Steps to Reproduce

Editing the config file directly.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

1.0.126

Platform

Other

Operating System

Windows

Terminal/Shell

Warp

Additional Information

_No response_

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗