Live data from Hacker News

Maximizing the value of your Claude Code sessions

claude.com

21–30 of 206 posts

Re: Maximizing the value of your Claude Code sessions

#23

This feels like the Anthropic version of "You're holding it wrong" (1) 1) https://www.wired.com/2010/06/iphone-4-holding-it-wrong/

It feels worse. It's all noob level suggestions that any decent system would have optimized away already.

Re: Maximizing the value of your Claude Code sessions

#24

Bro: superintelligent machine line go up AI AGI software solved automate everything Also bro: Run /clearbetween tasks. This prevents prior irrelevant context from being sent back to the model, which can reduce token usage. Set your model and effort level before you start. Changing either one mid-conversation can bust your prompt cache, which can increase token cost. @-mention files instead of naming them. The file ge…

Author not bro, sorry misgender

I'd argue that women can be bros too, especially when using the word in this sense.

Re: Maximizing the value of your Claude Code sessions

#25
> @-mention files instead of naming them

Love Claude, but the @ mention is broken in the desktop app. For the same project if I type the same query "@ephem" I get:

CLI: https://imgur.com/a/VZMUCOa (good, relevant results)

Desktop: https://imgur.com/a/QLSo4Ms (bad, irrelevant)

Opened issue for this and it was automatically closed:

https://github.com/anthropics/claude-code/issues/71421

I could have written the issue better (using CLI as comparison instead of VS Code). But, no doubt in my mind Claude could fix this itself in a minute.

Re: Maximizing the value of your Claude Code sessions

#26
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?

Re: Maximizing the value of your Claude Code sessions

#27

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?

As a driver I want to spend the majority of the day optimizing my truck's gasoline usage so that I can focus on optimizing my productivity for an outcome I am too far disconnected from to care about anymore.

Re: Maximizing the value of your Claude Code sessions

#29
> @-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 anyone explain why /context takes so long to run? It usually takes several seconds, and I've had cases of it taking over a minute.

And why don't they just show the basics in a status line somewhere? Just a plain: "120K/200K tokens" I hate having to type /context just to get this. And I shouldn't need to install an extension.

Re: Maximizing the value of your Claude Code sessions

#30
post #5

I mean, it feels hard not to laugh at this type of blog post. My cynical interpretation is that this is a type of passing the buck to engineers in enterprise settings ("Stop spending tokens. Did you read the value maximization blog post? It is your fault.") Oh yes, Claude will do all sorts of different things -- it depends on how you use it! You should totally learn all of these little finicky things ... because now…

Through my weekend experiments, I've found I can get way better outcomes, and an order of magnitude less cost with my slapped together sandboxed omp setup plus ZDR openrouter models (DeepSeek, Kimi, etc) than I've ever seen from Claude Code at work.

Everything is version pinned and a deliberate choice to change, and a git revert away from changing back.

TBF the models may change underneath me to some extent still, but the cost benefit of running them myself doesn't pan out yet (for agentic coding at least, don't have enough local vram to get a usable context window and generation speed, self hosting on runpod or similar isn't economically sensible for my current consumption though I have tinkered with it)

Post reply on HN