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)

Considering the ragefusion you're getting over the naming, maybe calling it something like --talkative would be less controversial? ;-)

> Another thing: is it possible to turn off the words like finagling and similar (I can't remember the spelling of any of them) ?

Big +1 on that. I find the names needlessly distracting. I want to just always say a single thing like “thinking”

You should be able to do something like this:

    "spinnerVerbs": {
      "mode": "replace",
      "verbs": ["Thinking"]
    }

https://code.claude.com/docs/en/settings#available-settings

Thank you for the config and the link, that's very much appreciated!

How absurd this is an option, but I’ll be using this config too.

I replaced my spinner verbs with thought-provoking Yodaese so my claude sessions are constantly making me think about my life decisions. Loving it. https://gist.github.com/topherhunt/b7fa7b915d6ee3a7998363d12...

> I want to just always say a single thing like “thinking”

As a counterview, I like the whimsical verbs. I'll be sticking with them. But nice to see there is an option.

I don't want my tools to make jokes, I want them to work.

I remember they shipped a feature so that’s configurable.

> To be clear: we re-purposed verbose mode to do exactly what you are asking for. We kept the name "verbose mode", but the behavior is what you want, without the other verbose output.

Verbose mode feels far too verbose to handle that. It’s also very hard to “keep your place” when toggling into verbose mode to see a specific output.

I think the point bcherny is making in the last few threads is that, the new verbose mode _default_ is not as verbose as it used to be and so it is not "too verbose to handle that". If you want "too verbose", that is still available behind a toggle

Yeah, I didn't realize that there's a new sort of verbose mode now which is different than the verbose mode that was included previously. Although I'm still not clear on the difference between "verbose mode" and "ctrl + o". Based on https://news.ycombinator.com/item?id=46982177 I think they are different (specifically where they say "while hiding more details behind ctrl+o".

Specifically do you mean when you say git history is sent? How much of it is included in each request?

It's the last 5 commits, not the full history. Here's what actually gets sent in the system prompt:

  gitStatus: This is the git status at the start of the conversation...
  Current branch: main
  Main branch: main
  Status: (clean)

  Recent commits:
  6578431 chore: Update security contact email (#417)
  0dc71cd chore: Open source readiness fixes (#416)
  ...

Enough for Claude to understand what you've been working on without sending your entire repo history.

As someone who loves all the non-AI portions of Graphite (the CLI and the reviewer UI) should I be worried about this acquisition? Or will the CLI and Reviewer Ui continue to be be maintained and improved?

Forgive some ignorance, but we use Graphite at work, and I don't dislike it or anything, but I haven't really been able to see its appeal over just doing a PR within Github, at least if you exclude the AI stuff.

What do you like about the non-AI parts? I mean it's a little convenient to be able to type `gt submit` in order to create the remote branch and the PR in one step, but it doesn't feel like anything that an alias couldn't do.

the stacked changes support, for me, was an absolute game changer. the auto rebasing, etc, is -really- nice. i found it especially useful for Gitops type stuff where you have to make lots of little PRs

Is it better than just using jj locally though?

Maintained, improved, and integrated.

With more resources than ever. We're building whole platform. That's a lot more than just AI.

No concerns! The plan is to maintain and improve both

This has terrible top suggestions for my city, looks like complete overpriced tourist traps.

> He's also implying that Rails does not use web sockets to communicate with frontend which is not only wrong it should be evidently wrong to anyone who built a Rails app in the last 3 years

Where is the article saying that? I only see " Those things are possible in Rails and Laravel, but they take a bit more effort to set up." which is a very different (and more nuanced/personal take) then what you're stating.

I wish someone would make a keyboard with keycaps that are like 80% size. I think that would make it much easier to hit some of the keys that are further away.

Have you tried using key tilters? It makes a significant difference for me: https://sites.google.com/view/keyboards/hardware/accessories...

> glove80 has far and away the most comfortable thumb cluster for my hands

If I'm reading your reply further down the page right then you only use two of the 6 keys. Is that right? For me, I think I'd want to use at least 4 or 5 keys in my thumb cluster before I could call it comfortable.