Re:Claude Code Is Being Dumbed Down
by dimitri-vs on Wednesday February 11, 2026 @07:02PM
(#46983002)
Exactly. If a user wants a simpler experience there is now the Claude Cowork option.
That's a cool idea!
Honestly Tmux, vim, kitty, almost every terminal, shell, script is configurable. It’s what we’re used to. I wouldn’t know why you wouldn’t start allowing more config options.
Re:Claude Code Is Being Dumbed Down
by johnisgood on Wednesday February 11, 2026 @08:38PM
(#46983829)
I do not use CC (yet) but I think this is the right direction. We are hackers. We love hacking. We love to tinker about and configure! Please allow us.
(And yeah, I would love the verbose mode myself, but there could be various levels to it.)
Re:Claude Code Is Being Dumbed Down
by whodidntante on Thursday February 12, 2026 @07:06AM
(#46987735)
ok, I will be the dumbass here - I am a retired software engineer who has not used any of these tools, but when I as working on high volume web sites, all I wanted and needed was access to the log files. I would always have a small terminal session open to tail and grep for errors for the areas I was interested in. Had another small window to tail and monitor specific performance values. Etc.
I do not know how this concept would work in these agentic environments, but would seem useful, in an environment that has a lot of parallel things going on, with a lot of metrics that could be useful, you would want to have multiple monitors that can be quickly customized with standard linux utilities. Token usage, critical directory access, etc.
This, in conjunction with a config file to define/filter out the log stream should be all that's needed to provide as much or as little detail that would be needed to monitor how things are going, and to alert when certain things are going off the rails.
I actually miss being able to see all of the thinking, for example, because I could tell more quickly when the model was making a wrong assumption and intervene.