← Back to context Comment by CjHuber 10 days ago And how to get to the old verbose mode then...? 5 comments CjHuber Reply bcherny 10 days ago Hit ctrl+o bostonvaulter2 10 days ago Wait so when the UI for Claude Code says “ctrl + o for verbose output” that isn’t verbose mode? bcherny 10 days ago That is more verbose — under the hood, it’s now an enum (think: debug, warn, error logging) 1 reply → x4132 9 days ago ctrl + o isn't live - that's not what users want, what users want is the OPTION to choose what we want to see.
bcherny 10 days ago Hit ctrl+o bostonvaulter2 10 days ago Wait so when the UI for Claude Code says “ctrl + o for verbose output” that isn’t verbose mode? bcherny 10 days ago That is more verbose — under the hood, it’s now an enum (think: debug, warn, error logging) 1 reply → x4132 9 days ago ctrl + o isn't live - that's not what users want, what users want is the OPTION to choose what we want to see.
bostonvaulter2 10 days ago Wait so when the UI for Claude Code says “ctrl + o for verbose output” that isn’t verbose mode? bcherny 10 days ago That is more verbose — under the hood, it’s now an enum (think: debug, warn, error logging) 1 reply →
bcherny 10 days ago That is more verbose — under the hood, it’s now an enum (think: debug, warn, error logging) 1 reply →
x4132 9 days ago ctrl + o isn't live - that's not what users want, what users want is the OPTION to choose what we want to see.
Hit ctrl+o
Wait so when the UI for Claude Code says “ctrl + o for verbose output” that isn’t verbose mode?
That is more verbose — under the hood, it’s now an enum (think: debug, warn, error logging)
1 reply →
ctrl + o isn't live - that's not what users want, what users want is the OPTION to choose what we want to see.