Feature Request: Customizable Verbose Output Fields
Current Behavior
When pressing Ctrl+O to toggle verbose output, Claude Code displays 3 fields of detailed information about tool usage and execution.
Requested Enhancement
I would like to configure the number and type of fields displayed in verbose mode. Specifically:
- Ability to display up to 10 fields instead of the current 3
- Configuration option in
settings.json to customize which fields are shown
- Ability to add custom fields with additional debugging/process information
Proposed Configuration
Something like this in ~/.claude/settings.json:
{
"verboseOutput": {
"fields": [
"toolName",
"executionTime",
"parameters",
"returnValue",
"memoryUsage",
"timestamp",
"workingDirectory",
"gitBranch",
"processId",
"modelUsed"
],
"maxFields": 10
}
}
Use Case
When debugging complex workflows or analyzing Claude Code behavior, having more detailed information readily available would significantly improve the development experience without needing to parse log files or add custom hooks.
Additional Context
Currently, the only workaround is to use hooks for logging, but real-time display of additional fields would be much more convenient for interactive debugging.
Feature Request: Customizable Verbose Output Fields
Current Behavior
When pressing
Ctrl+Oto toggle verbose output, Claude Code displays 3 fields of detailed information about tool usage and execution.Requested Enhancement
I would like to configure the number and type of fields displayed in verbose mode. Specifically:
settings.jsonto customize which fields are shownProposed Configuration
Something like this in
~/.claude/settings.json:{ "verboseOutput": { "fields": [ "toolName", "executionTime", "parameters", "returnValue", "memoryUsage", "timestamp", "workingDirectory", "gitBranch", "processId", "modelUsed" ], "maxFields": 10 } }Use Case
When debugging complex workflows or analyzing Claude Code behavior, having more detailed information readily available would significantly improve the development experience without needing to parse log files or add custom hooks.
Additional Context
Currently, the only workaround is to use hooks for logging, but real-time display of additional fields would be much more convenient for interactive debugging.