What I see is that I have to read a bunch of stuff and go through a bunch of hassle to save money when the root of it is that if I tell an AI to do work on a task while I'm busy with something else and come back later I've doubled my cost because the cache expires too quickly?
The AI is so super intelligent that it can't optimize itself and instead burns through tokens needlessly. The people programming the AI are so good that they can write long winded articles about how to optimize their AI but can't get the AI to do these things by default. It's all so tiring. I care less and less about Claude every single day because of the usage caps and the constant optimizing that has to be done. Th…
Maximizing the value of your Claude Code sessions
161–170 of 206 posts
Re: Maximizing the value of your Claude Code sessions
#162This is all good to know, but funny how we are suddenly back to formal languages and commands. Aren't these things intelligent enough to figure these things out for us?
Re: Maximizing the value of your Claude Code sessions
#163What I want is a version of `/clear` that keeps the conversation but drops out things like bloated logs, error traces, etc that were only relevant in the immediate local context. I guess compacting somewhat does that but I want something more explicitly that trims out these extremely bloated artefacts while maintaining in full the actual conversation history.
Re: Maximizing the value of your Claude Code sessions
#164Re: Maximizing the value of your Claude Code sessions
#165Re: Maximizing the value of your Claude Code sessions
#166> @-mention files instead of naming them. The file gets attached to your message directly, which saves a Read call, or a search if Claude has to go find it. I've heard it argued that this is an antipattern. If the file is large, it will read the whole file. With Read or something similar, it can do a targeted search and read only the relevant portion. Is this still not the case? Also, since they mention /context: Can…
Re: Maximizing the value of your Claude Code sessions
#167Earlier quoted context omitted.
That's what is shown by default in the app. I'll never understand why anyone would want to restrict themselves to a terminal interface instead, and I say this as a Vim user.
> That's what is shown by default in the app. 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…
What? Claude Code shows you context window and session limits right next to the text input box.
Re: Maximizing the value of your Claude Code sessions
#168Earlier quoted context omitted.
> That's what is shown by default in the app. 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…
> 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. What? Claude Code shows you context window and session limits right next to the text input box.
Re: Maximizing the value of your Claude Code sessions
#169Considering that I'm mostly unable to reach the limit of my X5 subscription and we have 1M context, it is a guide to maximize Anthropic PnL pre-IPO
Re: Maximizing the value of your Claude Code sessions
#170Earlier quoted context omitted.
The AI is so super intelligent that it can't optimize itself and instead burns through tokens needlessly. The people programming the AI are so good that they can write long winded articles about how to optimize their AI but can't get the AI to do these things by default. It's all so tiring. I care less and less about Claude every single day because of the usage caps and the constant optimizing that has to be done. Th…
Three years ago, a computer that can write working C++ on the first try would have been considered to be a miracle. It's amazing how quickly the goalposts move.