Global verbose setting not taking effect - reverts to false on each terminal session

Resolved 💬 2 comments Opened Sep 2, 2025 by javaboomBird Closed Sep 2, 2025

Bug Description

The global configuration setting does not persist across Claude Code terminal sessions. Despite setting globally, each new terminal session shows the setting as and verbose output is not displayed.

Steps to Reproduce

  1. Set global verbose configuration:

``bash
claude config set -g verbose true
``

  1. Verify the setting is saved:

``bash
claude config list -g
`
Shows:
"verbose": "true"`

  1. Open a new Claude Code terminal session
  1. Observe that verbose output is not displayed for bash commands
  1. The verbose setting appears to revert to false behavior despite being stored as true

Expected Behavior

When is set to globally, all new Claude Code sessions should display full bash and command outputs by default.

Actual Behavior

Despite the global setting showing , new terminal sessions behave as if verbose is false - bash command outputs are not fully displayed.

Environment Information

  • Claude Code Version: 1.0.100
  • Operating System: macOS 15.6.1 (24G90)
  • Platform: darwin
  • Shell: bash/zsh

Configuration Details

Global config shows:

{
  "verbose": "true",
  "theme": "dark",
  "autoUpdates": true,
  // ... other settings
}

Additional Context

  • The issue persists across multiple terminal restarts
  • No project-level configuration files found that might override the global setting
  • Configuration appears to be stored correctly but not applied during session initialization
  • Other global settings (like theme) work correctly

Possible Workaround

Currently need to use claude --verbose flag when starting each session, but this defeats the purpose of the global configuration.

Priority

This affects the user experience as verbose output is important for understanding what commands are being executed, especially for debugging and learning purposes.

View original on GitHub ↗

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