claude-code - 💡(How to fix) Fix [Bug] `/status` displays spurious warning with empty invalid settings file list [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46060Fetched 2026-04-11 06:30:02
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×3commented ×1

Code Example

[]
RAW_BUFFERClick to expand / collapse

Bug Description /status shows a spurious warning: "Found invalid settings files: . They will be ignored." The colon is followed only by a period — no file path is listed.

Environment:

  • Claude Code version: 2.1.98
  • OS: Windows 11 Home (10.0.26200)
  • Shell: Git Bash
  • Login: Claude Max account

What I verified:

  • Only two settings files exist on disk, both valid JSON:
    • C:\Users\tkash.claude\settings.json
    • C:\Users\tkash.claude.json
  • No project-level .claude/settings.json, no .claude/settings.local.json, no managed settings under C:\ProgramData.
  • No CLAUDE_* env var overrides a settings path.
  • /status itself reports "Setting sources: User settings" correctly.

Expected: no warning, since there are no invalid settings files. Actual: the warning fires with an empty file list, suggesting the "print warning" branch runs even when the invalid-files list is empty.

Environment Info

  • Platform: win32
  • Terminal: null
  • Version: 2.1.98
  • Feedback ID: b1cfff40-a6e3-437b-ac49-b9709eb078d8

Errors

[]

extent analysis

TL;DR

The issue can likely be resolved by modifying the warning message logic to check for an empty list of invalid settings files before printing the warning.

Guidance

  • Verify that the invalid-settings list is indeed empty when the warning is printed by adding a debug log or console output to inspect the list's contents.
  • Check the code path that generates the warning message to ensure it correctly handles the case where the list of invalid settings files is empty.
  • Consider adding a conditional statement to only print the warning if the list of invalid settings files is not empty.
  • Review the settings file loading and validation logic to ensure it is correctly identifying and handling valid settings files.

Example

if (invalidSettingsFiles.length > 0) {
  console.log(`Found invalid settings files: ${invalidSettingsFiles.join(', ')}. They will be ignored.`);
}

Notes

The issue seems to be related to the warning message logic, and modifying this logic to handle the empty list case should resolve the issue. However, without access to the codebase, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: Modify the warning message logic to check for an empty list of invalid settings files before printing the warning, as this is a more targeted and less invasive change than upgrading to a potentially non-existent fixed version.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING