I'll never understand why anyone would want to restrict themselves to a terminal interface instead, and I say this as a Vim user.
I'll never understand why anyone would want to restrict themselves to a terminal interface instead, and I say this as a Vim user.
It is shown in Claude Desktop if you care to check in Settings > Usage, sure - but not in Claude Code, updated as you work with it.
> I'll never understand why anyone would want to restrict themselves to a terminal interface instead, and I say this as a Vim user.
I usually work with Claude in tandem, that is: The agent is actively working while I am either reviewing code or making changes myself in other places. So this means I want to work within my IDE. If you use Claude Code to vibe-code without interacting with the codebase at all, the Desktop app is probably fine, but for all other purposes, you'll need to run it either in the CLI or integrated into your editor.
And since I use different editors and don't like using either a sub-par U integration or locking myself into the harness of my IDE's vendor, I prefer the CLI as a universal way of running Claude Code.
What? Claude Code shows you context window and session limits right next to the text input box.
The app has a context wheel on the right of the chat box, showing both current conversation context breakdown and 5h as well as weekly limits.