Auto mode enabled by default on fresh launch (2.1.241), contradicting `tengu_auto_mode_default_on: false`

Status Open
Reported on v2.1.241
Maintainer reply None cached
Activity 0 comments · opened Aug 24, 2026

Auto mode is on by default immediately on a fresh claude launch with no arguments and no prior interaction — footer shows "auto mode on (shift+tab to cycle)" before typing anything.

Repro:

  1. Update to 2.1.241 (installed 2026-08-24)
  2. Launch claude with no arguments, from a plain terminal
  3. Footer immediately shows "auto mode on (shift+tab to cycle)" — no keypress, no prior session, no flag

Also observed in a separate session on the same machine: auto mode was active from the first turn (a single message, no tool-permission prompts before non-trivial file edits began), with no "manual mode" indicator having been seen beforehand — inconsistent with prior version's footer behavior.

What doesn't explain it:

  • No autoMode or permissionMode key in ~/.claude/settings.json, ~/.claude.json, or project .claude/settings*.json
  • Launched with no CLI flags (ps confirms bare claude, no --permission-mode)
  • ~/.claude.json has a locally cached flag tengu_auto_mode_default_on: false
  • CHANGELOG.md / code.claude.com/docs/en/changelog entries for 2.1.239–2.1.241 don't mention any default permission-mode change (2.1.240/2.1.241 are both just "Bug fixes and reliability improvements")

Why this matters: auto mode skips per-action confirmation prompts. A silent default flip for existing users (not an explicit opt-in) is a safety-relevant regression, not cosmetic.

Version: 2.1.241 (also present after updating from 2.1.239)
Platform: macOS (Darwin 24.6.0)

View original on GitHub ↗