4 ms·
Hasn't this been largely solved by auto-caching introduced recently by Anthropic, where you pass "cache_control": {"type": "ephemeral"} in your request and it p
by somesnm 7mo ago
Hasn't this been largely solved by auto-caching introduced recently by Anthropic, where you pass "cache_control": {"type": "ephemeral"} in your request and it puts breakpoints automatically? https://platform.claude.com/docs/en/build-with-claude/prompt-caching#automatic-caching https://platform.claude.com/docs/en/build-with-claude/prompt...
- stingraycharles 7mo agoYes, it has, this is a non-problem, and even if it was a problem, an MCP server would most definitely be one of the worst ways to fix it.
- philipp-gayret 7mo agoLooking at my own usage with claude code out of the box and nothing special around caching set up. For this month according to ccusage I have in tokens 0.2M input, 0.6M output, 10M cache create, 311M cache read for 322M total tokens. Seems to me that it caches out of the box quite heavily, but if I can trim my usage somehow with these kind of tools I'd love to know.
- stingraycharles 7mo agoThis is not about caching things for stuff that others built, it’s solely to modify code that you’re writing that will use Anthropic’s API endpoints.
- ermis 7mo ago[flagged]
- stingraycharles 7mo agoPlease don’t use AI for writing comments. Also, what this adds is mostly overhead at the wrong level of abstraction, not visibility.
- gostsamo 7mo agoIt is answered in the FAQ.