[BUG] /config: toggling "Open agents view by default" reports false changes to Auto-compact and Theme

Resolved 💬 1 comment Opened May 15, 2026 by Martini991 Closed May 21, 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?

In the interactive /config menu, toggling "Open agents view by default" causes two unrelated side-effects in the UI/output without actually writing those changes to disk:

  1. The Auto-compact row in the TUI flips from false to true (or vice versa) alongside the intended toggle.
  2. The exit banner printed to the terminal claims Enabled auto-compact and Set theme to dark, even though neither setting was changed.

On disk, only the intended setting (defaultToAgentsView) is actually written — the reported auto-compact and theme changes are phantom.

What Should Happen?

  • TUI shows only "Open agents view by default" as changed.
  • Exit banner reports only Enabled/Disabled open agents view by default.
  • .claude.json diff shows only defaultToAgentsView flipped.

Error Messages/Logs

Exit banner:

Set theme to dark
Enabled auto-compact
Disabled open agents view by default

TUI: Auto-compact row shows as flipped to true.

.claude.json diff (only real change):

- "defaultToAgentsView": true,
+ "defaultToAgentsView": false,

No autoCompact* key exists in .claude.json before or after the toggle. No theme key was written either. The banner and the TUI row for Auto-compact are misreporting state.

Steps to Reproduce

  1. Run Claude Code with a known-stable config (auto-compact and theme already at their desired values).
  2. Snapshot ~/.claude/.claude.json (this is where /config actually writes — not ~/.claude/settings.json).
  3. Open /config.
  4. Toggle "Open agents view by default" (either direction).
  5. Exit /config.
  6. Observe the exit banner and diff ~/.claude/.claude.json against the pre-toggle snapshot.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.142 (Claude Code)

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

Impact

  • Users can't trust the /config TUI or its exit banner to reflect what was actually changed.
  • A user who sees "Enabled auto-compact" in the banner may believe auto-compact is now on when it isn't (or vice versa).

Environment

  • Terminal: Ghostty 1.3.1
  • Claude Code version: 2.1.142
  • OS: Pop!_OS 24.04 LTS (Ubuntu 24.04 noble base)
  • Kernel: Linux 6.18.7-76061807-generic
  • Running inside rootless podman container (claude-code image), but the bug is in the TUI/state layer, not host-specific.

Notes

  • ~/.claude/settings.json is not touched by /config for these toggles — the destination is ~/.claude/.claude.json. (Mentioning this in case it helps narrow the code path.)
  • The same misreporting affects the theme line in the exit banner — it echoes the current theme value rather than only reporting actual changes, suggesting the banner re-emits state for multiple settings rather than only the toggled one.
  • Feedback to Anthropic UUID: 4d4ad542-bc0b-48d3-8a4c-fe0b46c4dca5

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗