bcherny

5 ms·

61.
by bcherny 6mo ago
Thanks for the feedback. To make it actionable, would you mind running /bug the next time you see it and posting the feedback id here? That way we can debug and see if there's an issue, or if it's within variance.
62.
by bcherny 6mo ago
Hey all, Boris from the Claude Code team here. I just responded on the issue, and cross-posting here for input. --- Hi, thanks for the detailed analysis. Before I keep going, I wanted to say I appreciate the depth of thinking & care tha
63.
by bcherny 8mo ago
Boris from the Claude Code team here. Some of the engineers working on the app worked on Electron back in the day, so preferred building non-natively. It’s also a nice way to share code so we’re guaranteed that features across web and deskt
64.
by bcherny 8mo ago
That is more verbose — under the hood, it’s now an enum (think: debug, warn, error logging)
65.
by bcherny 8mo ago
Hit ctrl+o
66.
by bcherny 8mo ago
Yeah, in hindsight, we probably should have renamed it.
67.
by bcherny 8mo ago
"Is verbose mode the same as the old mode, where only file paths are spoken?" -- yes, this is exactly what the new verbose mode is.
68.
by bcherny 8mo ago
Hey -- we take accessibility seriously, and want Claude Code to work well for you. This is why we have repurposed verbose mode to do what you want, without the other verbose output. Please give it a try and let me know what you think.
69.
by bcherny 8mo ago
Yep, this is what we landed now, more or less: verbose mode is just file paths, then ctrl+o gives you thinking, agent output, and hook output.
70.
by bcherny 8mo ago
That's a cool idea!
71.
by bcherny 8mo ago
> I don't want verbose mode. I want Claude to tell me what it's reading in the first 3 seconds, so I can switch gears without fear it's going to the wrong part of the codebase. By saying that my use case requires verbose m
72.
by bcherny 8mo ago
fwiw, I wrote it 100% by hand. Maybe I talk to Claude too much..
73.
by bcherny 8mo ago
Have you tried verbose mode? /config > verbose. It should do exactly what you are looking for now, without extraneous thinking/subagent/hook output. We hear the feedback!
74.
by bcherny 8mo ago
It's a balance -- we don't want to hide everything away, so you have an understanding of what the model is doing. I agree that with future models, as intelligence and trust increase, we may be able to hide more, but I don't t
75.
by bcherny 8mo ago
Yes totally. ctrl+o used to show all messages, but this is one of the tricky things about building in a terminal: because many terminals are quite slow, it is hard to render a large amount of output at once without causing tearing/stut
76.
by bcherny 8mo ago
You want verbose mode for this -- we evolved it to do exactly what you're asking for: verbose file reads, without seeing thinking traces, hook output, or (after tomorrow's release) full subagent output. More details here: https:&
77.
by bcherny 8mo ago
I think folks might be crossing wires a bit. To make it so you can see full file paths, we repurposed verbose mode to enable the old explicit file output, while hiding more details behind ctrl+o. In effect, we've evolved verbose mode t
78.
by bcherny 8mo ago
VSCode (xterm.js) is one of the worst, but there's a large long tail of slow terminals out there.
79.
by bcherny 8mo ago
Hey, Boris from the Claude Code team here. I wanted to take a sec to explain the context for this change. One of the hard things about building a product on an LLM is that the model frequently changes underneath you. Since we introduced Cla
80.
We've rewritten Claude Code's terminal rendering to reduce flickering by 85%(github.com)
3 points by bcherny 10mo ago|3 comments
81.
by bcherny 10mo ago
We wanted to share more about why this was so difficult, how the fix works and how we used Claude Code to fix it
82.
by bcherny 10mo ago
Since we released the last major version of Claude Code, Claude writes its plan to a file automatically for that reason! It also means you can continue to edit your plan as you go.
83.
by bcherny 10mo ago
Add it to your CLAUDE.md. Claude will automatically read that file every time it starts up
84.
by bcherny 10mo ago
Yeah, adherence is a hard problem. It should be feeling much better in newer models, especially Opus 4.5. I generally find that Opus listens to me the first time.
85.
by bcherny 10mo ago
You might be misunderstanding what a CLAUDE.md is. It’s not about fighting the model, rather it’s giving the model a shortcut to get the context it needs to do its work. You don’t have to have one. Ours is 100% written by Claude itself.
86.
by bcherny 10mo ago
Try to keep it under 1k tokens or so. We will show you a warning if it might be too big. Ours is maybe half that size. We remove from it with every model release since smarter models need less hand-holding. You can also break up your CLAUDE
87.
by bcherny 10mo ago
Hey, Boris from the Claude Code team here. A few tips: 1. If there is anything Claude tends to repeatedly get wrong, not understand, or spend lots of tokens on, put it in your CLAUDE.md. Claude automatically reads this file and it’s a great
88.
by bcherny 11mo ago
Fair feedback — commented https://github.com/anthropics/claude-code/issues/3648#issuec...
89.
by bcherny 11mo ago
We started by using Ink, and at this point it’s our own framework due to the number of changes we’ve made to it over the months. Terminal rendering is hard, and it’s less that we haven’t modified the renderer, and more that there is this pr
90.
by bcherny 11mo ago
Hey, Boris from the Claude Code team here. We try hard to read through every issue, and respond to as many issues as possible. The challenge is we have hundreds of new issues each day, and even after Claude dedupes and triages them, practic

More ›