3 ms·

Only if you set `ENABLE_PROMPT_CACHING_1H`, which was mentioned in the release notes for a recent Claude Code release but doesn't seem to be in the official doc

Only if you set `ENABLE_PROMPT_CACHING_1H`, which was mentioned in the release notes for a recent Claude Code release but doesn't seem to be in the official docs.

andersa 6mo ago
Bruh. It's getting hard to track down all these MAKE_IT_ACTUALLY_WORK settings that default to off for no reason.
- deleted 6mo ago
  [deleted]
- ethbr1 6mo ago
  That's the beginning of Googlification of feature evolution, via population statistics rather than quality. If it increases a KPI by 5% for 95% of users but torpedos the experience for 5%? Ship it.
  - hnben 6mo ago
    that sounds like a win-win to me. on one hand 95% of users get an improved experience. While a competitor gets the chance to build a business for the remaining 5%.
- matheusmoreira 6mo ago
  For me it's gotten to the point where I have a wrapper script that applies like 5 environment variables and even patches the system prompt strings prior to every Claude Code invocation. After the Claude Code source code leak someone discovered that some variables are read directly from the process environment. Can't even trust that setting them in ~/.claude/settings.json will work! I've actually started asking Claude itself to dissect every Claude Code update in order figure out if it broke some part of the Rube Goldberg machine I was forced to set up.
g4cg54g54 6mo ago
subusers supposedly get it automatic again after the fix (and now also with `DISABLE_TELEMETRY=1`) but if you are api user you must set `ENABLE_PROMPT_CACHING_1H` as i understood and when using your own api (via `ANTHROPIC_BASE_URL`) ensure `CLAUDE_CODE_ATTRIBUTION_HEADER=0` is set as well... https://github.com/anthropics/claude-code/issues/50085 https://github.com/anthropics/claude-code/issues/50085 and check out the other neckbreakers ive found pukes lots of malicious compliance by feels... :/ [BUG] new sessions will *never* hit a (full)cache #47098 https://github.com/anthropics/claude-code/issues/47098 https://github.com/anthropics/claude-code/issues/47098 [BUG] /clear bleeds into the next session (what also breaks cache) #47756 https://github.com/anthropics/claude-code/issues/47756 https://github.com/anthropics/claude-code/issues/47756 [BUG] uncachable system prompt caused by includeGitInstructions / CLAUDE_CODE_DISABLE_GIT_INSTRUCTIONS -> git status https://github.com/anthropics/claude-code/issues/47107 https://github.com/anthropics/claude-code/issues/47107
plaguuuuuu 6mo ago
no way, I didn't realise this worked. My attention span is such that I get side tracked and wind up taking longer than 5 mins quite a bit :D

Only if you set `ENABLE_PROMPT_CACHING_1H`, which was mentioned in the release notes for a recent Claude Code release but doesn't seem to be in the official docs.

andersa 6mo ago

Bruh. It's getting hard to track down all these MAKE_IT_ACTUALLY_WORK settings that default to off for no reason.

deleted 6mo ago
[deleted]
ethbr1 6mo ago
That's the beginning of Googlification of feature evolution, via population statistics rather than quality. If it increases a KPI by 5% for 95% of users but torpedos the experience for 5%? Ship it.
- hnben 6mo ago
  that sounds like a win-win to me. on one hand 95% of users get an improved experience. While a competitor gets the chance to build a business for the remaining 5%.
matheusmoreira 6mo ago
For me it's gotten to the point where I have a wrapper script that applies like 5 environment variables and even patches the system prompt strings prior to every Claude Code invocation. After the Claude Code source code leak someone discovered that some variables are read directly from the process environment. Can't even trust that setting them in ~/.claude/settings.json will work! I've actually started asking Claude itself to dissect every Claude Code update in order figure out if it broke some part of the Rube Goldberg machine I was forced to set up.

g4cg54g54 6mo ago

subusers supposedly get it automatic again after the fix (and now also with `DISABLE_TELEMETRY=1`) but if you are api user you must set `ENABLE_PROMPT_CACHING_1H` as i understood and when using your own api (via `ANTHROPIC_BASE_URL`) ensure `CLAUDE_CODE_ATTRIBUTION_HEADER=0` is set as well... https://github.com/anthropics/claude-code/issues/50085 https://github.com/anthropics/claude-code/issues/50085 and check out the other neckbreakers ive found pukes lots of malicious compliance by feels... :/ [BUG] new sessions will *never* hit a (full)cache #47098 https://github.com/anthropics/claude-code/issues/47098 https://github.com/anthropics/claude-code/issues/47098 [BUG] /clear bleeds into the next session (what also breaks cache) #47756 https://github.com/anthropics/claude-code/issues/47756 https://github.com/anthropics/claude-code/issues/47756 [BUG] uncachable system prompt caused by includeGitInstructions / CLAUDE_CODE_DISABLE_GIT_INSTRUCTIONS -> git status https://github.com/anthropics/claude-code/issues/47107 https://github.com/anthropics/claude-code/issues/47107

plaguuuuuu 6mo ago

no way, I didn't realise this worked. My attention span is such that I get side tracked and wind up taking longer than 5 mins quite a bit :D