[Bug] `/status` displays spurious warning with empty invalid settings file list

Resolved 💬 3 comments Opened Apr 10, 2026 by TsuyoshiKashiwazaki Closed Apr 13, 2026

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

[]

View original on GitHub ↗

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