g4cg54g54
Joined 1 year ago
Karma
57
Submissions
27
Member since
Aug 7
Recent submissions
Comment · 2 months ago
Comment · 6 months ago
funfact: enabling DNS sec NOW will fix your domain instantly if dnssec was disabled before
-> no idea if that also "heals" anyone who had dnssec on before.
-> no idea if maybe they need to roll back something and then rebreak the new dnssec i made a minute later lol...
Comment · 6 months ago
same vain as https://news.ycombinator.com/item?id=47952722 ?
HERMES.md in commit messages causes requests to route to extra usage billing
1203 points | 21 hours ago | 524 comments
Comment · 6 months ago
> Please keep the feedback coming
if only there were a place with 9.881 feedbacks waiting to be triaged...
and that maybe not by a duplicate-bot that goes wild and just autocloses everything, just blessing some of the stuff there with a "you´ve been seen" label would go a long way...
Comment · 6 months ago
chargers of that size generally have there own internal (sometimes even shared by multiple receptacles) batteries
Comment · 6 months 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
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
[BUG] /clear bleeds into the next session (what also breaks cache) #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
Comment · 6 months ago
seems we have been heard ;)
2.1.108
Added ENABLE_PROMPT_CACHING_1H env var to opt into 1-hour prompt cache TTL on API key, Bedrock, Vertex, and Foundry (ENABLE_PROMPT_CACHING_1H_BEDROCK is deprecated but still honored),
and FORCE_PROMPT_CACHING_5M to force 5-minute TTL
And this is "a bit better" - but seemingly still nowhere close to what subscribers get where main thread, agent, initial and follow-up messages may all get there own ?intelligent? 5min or 1h decision :/
Comment · 7 months ago
a git status + "recent commits" (that will _always_ change) https://github.com/anthropics/claude-code/issues/47107
and a missing cache-mark that will make skills & project-claude.md cachemiss every time too https://github.com/anthropics/claude-code/issues/47098
TLDR: for now launch using `CLAUDE_CODE_DISABLE_GIT_INSTRUCTIONS=1 claude "Hello"`
https://news.ycombinator.com/item?id=47754795Comment · 7 months ago
Honorable mention also to https://github.com/cnighswonger/claude-code-cache-fix which "addresses even more issues with /resume"
Comment · 7 months ago
not to mention that "the outlook failure" seems to have been a layer 8 problem?
(think i picked up some line about not being aware how to use it in offline mode / calling this out as an "error" while it was the expected configuration at the time)
and the toilet problem being as banal as "well, you need to wait for the green ready light to turn on..." (and this just taking a bit longer than expected on the first go)
Comment · 7 months ago
currently "clear makes it worse" https://github.com/anthropics/claude-code/issues/47098 + https://github.com/anthropics/claude-code/issues/47107
launching with `CLAUDE_CODE_DISABLE_GIT_INSTRUCTIONS=1 claude "Hello"` till those are fixed seems to be th way
Comment · 7 months ago
would like to know this too ;D
there is env.ENABLE_PROMPT_CACHING_1H_BEDROCK - but that is - as the name says "when using Bedrock"
for the raw API the docs are also clear -> "ttl": "1h" https://platform.claude.com/docs/en/build-with-claude/prompt...
but how to make claude-code send that when paying by API-key? or when using a custom ANTHROPIC_BASE_URL? (requests will contain cache_control, but no ttl!)
Comment · 7 months ago
from looking at the raw requests, that cant seem right?
its all "cache_control": { "type": "ephemeral" } there is no "ttl" anywhere.
// edit: cc_version=2.1.104.f27
- https://github.com/anthropics/claude-code/issues/47756 > [BUG] /clear bleeds into the next session (what also breaks cache)
- https://github.com/anthropics/claude-code/issues/47098 > [BUG] new sessions will *never* hit a (full)cache