When we started Claude Code, it was just a few of us using it

In what terminals is rendering slow? I really think GPU acceleration for terminals (as seen in Ghostty) is silly. It's a terminal. Edit: I can't post anymore today apparently because of dang. If you post a comment about a bad terminal at least tell us about the rendering issues.

This is an insanely good response. History, backstory, we screwed up, what we're doing to fix it. Keep up the great work!

There are so many config options. Most I still need to truly deeply understand. But this one isn't? I'd call myself a professional. I use with tons of files across a wide range of projects and types of work. To me file paths were an important aspect of understanding context of the work and of the context CC was gaining. Now? It feels like running on a foggy street, never sure when the corner will come and I'll hit a fence or house. Why not introduce a toggle? I'd happily add that to my alisases. Edit: I forgot. I don't need better subagent output. Or even less output whrn watching thinking traces. I am happy to have full verbosity. There are cases where it's an important aspect.

I can’t count how many times I benefitted from seeing the files Claude was reading, to understand how I could interrupt and give it a little more context… saving thousands of tokens and sparing the context window. I must be in the minority of users who preferred seeing the actual files. I love claude code, but some of the recent updates seem like they’re making it harder for me to see what’s happening.. I agree with the author that verbose mode isn’t the answer. Seems to me this should be configurable

> this resulted in an experience that most users preferred I just find that very hard to believe. Does anyone actually do anything with the output now? Or are they just crossing their fingers and hoping for the best?

I'm a screen reader user and CTO of an accessibility company. This change doesn't reduce noise for me. It removes functionality. Sighted users lost convenience. I lost the ability to trust the tool. There is no "glancing" at terminal output with a screen reader. There is no "progressive disclosure." The text is either spoken to me or it doesn't exist. When you collapse file paths into "Read 3 files," I have no way to know what the agent is doing with my codebase without switching to verbose mode, which then dumps subagent transcripts, thinking traces, and full file contents into my audio stream. A sighted user can visually skip past that. I listen to every line sequentially. You've created a situation where my options are "no information" or "all information." The middle ground that existed before, inline file paths and search patterns, was the accessible one. This is not a power user pr…

> We can no longer design for ourselves, and we rely heavily on community feedback to co-design the right experience. We cannot build the right things without that feedback. How can that be true, when you're deliberately and repeatedly telling devs (the community you claim to listen to) that you know better than they do? They're telling you exactly what they want, and you're telling them, "Nah." That isn't listening. You understand that, right?

I am not a programmer and detest the terminal environment, while I design complexity, i need simple interfaces, claude is now guiding all dev based on my initial design spec, makes beatuful notebooks that can be uploaded directly to colab or github, no UX at all, no usability issues, this is the lastet baby we made yesterday starborn.github.io/copp-notebook thank you Claude engineering team for something that is flying very high and takes me with it, starborn.github.io/copp-notebook