Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Maximizing the value of your Claude Code sessions

claude.com

Post reply on HN
Print view View original

131–140 of 206 posts

Re: Maximizing the value of your Claude Code sessions

#131

Post by poseva »

3371 wrote: post #113
superasn wrote: post #69

Recently I came across the /handoff skill, which I've been using a lot. I find it much better than /compact. Basically: - /handoff file creates a short document with the important context from your current session and maybe next steps as checklist. - You can then start a fresh session with /continue file - You can also hand the work from Claude to ChatGPT, or the other way around. Very useful at time of session limit…

> Plus your handoff files becomes a useful piece of project memory that you can reference later. I've been doing this since I started agentic development, and have a whole framework based on this; Simply put I define workflow s that output templated files for everytype of tasks that happens in development. It's a powerful pattern I'd recommend everyone.

Can you please add more details? Thank you in advance!

Re: Maximizing the value of your Claude Code sessions

#132

Post by watwut »

guessmyname wrote: post #38
rhaksw wrote: post #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 be…

> Opened issue for this and it was automatically closed: […] Clarification: It wasn’t closed on submission though. It sat open ~17 days, a bot marked it stale, and it closed when nobody responded to the stale label. The two-phase thing is the part I didn’t know until recently: the stale label is basically asking “is this still relevant?”, and answering it makes the bot back off next time around. nixpkgs does the same…

The stale bots are such a crap.

Re: Maximizing the value of your Claude Code sessions

#133

Post by cellularmitosis »

janalsncm wrote: post #16
jnwatson wrote: post #9

Can anyone explain why the prefix cache is tied to effort? I frequently run Fable at xhigh effort to run statistical modeling way above my undergraduate understanding. Claude Fable produces Masters-degree level output, and then I spend lots of round trips asking it to explain different parts to me. The first part absolutely uses the extra effort, but the interrogation exercise is something a much simpler model, or th…

I’m guessing that there’s a system prompt at the top telling the model about its reasoning budget. So when you switch reasoning effort it busts the cache.

Maybe switching effort routes you to a different rack of gpu’s which don’t have the cache

Re: Maximizing the value of your Claude Code sessions

#135

Post by moebrowne »

dpkirchner wrote: post #95

TIL the prompt cache lasts 1 hour. I thought it was reduced to 5 minutes.

It depends. If you have a Claude Code subscription then it defaults to an hour, if you use Claude via an API or third party then it defaults to 5 minutes. You can opt-in to the 1 hour TTL but it obviously costs more.

> 5-minute cache write tokens are 1.25 times the base input tokens price > 1-hour cache write tokens are 2 times the base input tokens price

https://code.claude.com/docs/en/prompt-caching#on-a-claude-s...

https://platform.claude.com/docs/en/build-with-claude/prompt...

Post reply on HN