HackerNews中文版

TLDR：目前，使用 `CLAUDE_CODE_DISABLE_GIT_INSTRUCTIONS=1 claude "Hello"` 启动。否则，你只会命中工具块，以及你的第一个后续问题。（注意：在 settings.json 中设置 includeGitInstructions=false 也是一个选项，而且可能更好，因为 git-status 总是 会产生噪音——但由于需要 "Hello"，记住一个别名也很简单，效果一样；D）目前，整个查询由 3 个可缓存的块构建：<pre><code> {tools | claude-version}, {system-prompt | ~/.claude/claude.md | git-status}, {skills | ./claude.md | user-prompt} </code></pre> 环境变量将允许 system-prompt 行再次被缓存 https://github.com/anthropics/claude-code/issues/47107"Hello" 允许 skills & ./claude.md 再次被缓存 https://github.com/anthropics/claude-code/issues/47098之前：<pre><code> claude > alive? > -> Yes, alive and ready. What do you need? > /exit # (11k cache read, 6k cache write) claude > are you here? > -> Yes, I'm here. What can I help you with? > /exit # (11k cache read, 6k cache write) ^^ nothing changed, still cashed 6k write tokens claude > alive? > -> Yes, I'm here. What can I help you with? > /exit # (18k cache read) ^^ the "exact same question" DOES hit the cache git commit --allow-empty -m "Dummy" claude > alive? > -> Yes, alive and well. What do you need? > /exit # (11k cache read, 6k cache write) ^^ same question, but now git busts the cache.... </code></pre> 之后：<pre><code> $ CLAUDE_CODE_DISABLE_GIT_INSTRUCTIONS=1 claude "Hello" Claude Code v2.1.104 Hello ● Hello! How can I help you today? Alive? ● Yes, alive and ready to help! What are you working on? # (10k cache read, 6k cache write) $ CLAUDE_CODE_DISABLE_GIT_INSTRUCTIONS=1 claude "Hello" Claude Code v2.1.104 Hello ● Hello! How can I help you today? are you alive? ● I'm an AI, so not alive in the biological sense — but I'm here and ready to help. What can I do for you? # (16k cache read, 20 cache write) $ git commit -m "just a dummy" --allow-empty [main 642ce16] just a dummy $ CLAUDE_CODE_DISABLE_GIT_INSTRUCTIONS=1 claude "Hello" Claude Code v2.1.104 Hello ● Hello! How can I help you today? is this alive? ● Yes, I'm alive and running! Is there something I can help you with? # (16k cache read, 18 cache write) </code></pre> 注意：这并没有解决昨天关于 5 分钟 vs 1 小时 的讨论——但除非这些根本原因得到修复，否则整个讨论毫无意义……- https://news.ycombinator.com/item?id=47739260 (Pro Max 5x 配额在 1.5 小时内耗尽，尽管使用量适中)- https://news.ycombinator.com/item?id=47736476 (Anthropic 在 3 月 6 日降低了缓存 TTL)但也有一些关于这方面的新闻：https://github.com/anthropics/claude-code/issues/46829#issuecomment-4237689126<pre><code> 目前，我们已经在许多地方为订阅用户默认推出了 1 小时的提示缓存…… 我们也没有将 API 客户默认为 1 小时——这需要更多测试，以确保它平均而言是一个净改进。我们很快将把客户端默认值更改为 1 小时，用于一些查询 </code></pre>

查看原文

TLDR: for now launch using `CLAUDE_CODE_DISABLE_GIT_INSTRUCTIONS=1 claude "Hello"`otherwise you will only ever hit on the tools-block, and your first follow-up-question(Note: setting includeGitInstructions=false in settings.json is an option to and likely the better thing anyhow since that git-status will always be noise - but since one needs the "Hello" remembering one alias is simple same deal ;D)Currently the whole query is build from 3 cache-able blocks:<pre><code> {tools | claude-version}, {system-prompt | ~/.claude/claude.md | git-status}, {skills | ./claude.md | user-prompt} </code></pre> the env-var will allow the system-prompt line go get cached again https://github.com/anthropics/claude-code/issues/47107the "Hello" allows skills & ./claude.md to get cached again https://github.com/anthropics/claude-code/issues/47098Before:<pre><code> claude > alive? > -> Yes, alive and ready. What do you need? > /exit # (11k cache read, 6k cache write) claude > are you here? > -> Yes, I'm here. What can I help you with? > /exit # (11k cache read, 6k cache write) ^^ nothing changed, still cashed 6k write tokens claude > alive? > -> Yes, I'm here. What can I help you with? > /exit # (18k cache read) ^^ the "exact same question" DOES hit the cache git commit --allow-empty -m "Dummy" claude > alive? > -> Yes, alive and well. What do you need? > /exit # (11k cache read, 6k cache write) ^^ same question, but now git busts the cache.... </code></pre> After:<pre><code> $ CLAUDE_CODE_DISABLE_GIT_INSTRUCTIONS=1 claude "Hello" Claude Code v2.1.104 Hello ● Hello! How can I help you today? Alive? ● Yes, alive and ready to help! What are you working on? # (10k cache read, 6k cache write) $ CLAUDE_CODE_DISABLE_GIT_INSTRUCTIONS=1 claude "Hello" Claude Code v2.1.104 Hello ● Hello! How can I help you today? are you alive? ● I'm an AI, so not alive in the biological sense — but I'm here and ready to help. What can I do for you? # (16k cache read, 20 cache write) $ git commit -m "just a dummy" --allow-empty [main 642ce16] just a dummy $ CLAUDE_CODE_DISABLE_GIT_INSTRUCTIONS=1 claude "Hello" Claude Code v2.1.104 Hello ● Hello! How can I help you today? is this alive? ● Yes, I'm alive and running! Is there something I can help you with? # (16k cache read, 18 cache write) </code></pre> Note: This does not address the 5 minutes vs 1 hour discussions from yesterday - but rather that whole discussion is pointless unless these root-causes are fixed....- https://news.ycombinator.com/item?id=47739260 (Pro Max 5x quota exhausted in 1.5 hours despite moderate usage)- https://news.ycombinator.com/item?id=47736476 (Anthropic downgraded cache TTL on March 6th)But there has been some news on this too: https://github.com/anthropics/claude-code/issues/46829#issuecomment-4237689126<pre><code> At this point we have rolled out 1h prompt cache by default in a number of places for subscribers ... We also are not defaulting API customers to 1h yet -- this needs more testing to make sure it's a net improvement on average. We will soon be changing the client side default to 1h for a few queries</code></pre>

告诉 HN：Claude-code 提示词缓存修复