In order Fable 5 has rejected: "Recipe for red-braised pork, I have pork shoulder" "Write up a framework for MCP patterns I can give to claude code" "explain the biomechanics of motion in c. elegans" (I get this one, I mostly did it to test and it's related to my hobby project) Do we get an extra day of functional Fable 5 because it's down?
Potential session/cache leakage between workspace instances or consumer accounts
41–50 of 151 posts
Re: Potential session/cache leakage between workspace instances or consumer accounts
#42Re: Potential session/cache leakage between workspace instances or consumer accounts
#43>"Maybe my coworker was talking about this in another session?"
This would be a critical bug that would slash the market value of a T$ company significantly, go ask your coworker or close the ticket, why do you expect the devs to put an enormous amount of effort hunting a potentially inexistent if you can't make that minuscule debugging effort.
Re: Potential session/cache leakage between workspace instances or consumer accounts
#44Earlier quoted context omitted.
It'd be terribly compute inefficient to not share prefix caches (KV cache) across customers.
What is the probability that two customers will have exactly the same tokens in cache? Wouldnt it require using the exact same CLAUDE.md, skills, MCPs and context? After that it is even worse since the nondeterminism of LLMs and humans
Re: Potential session/cache leakage between workspace instances or consumer accounts
#45Re: Potential session/cache leakage between workspace instances or consumer accounts
#46In order Fable 5 has rejected: "Recipe for red-braised pork, I have pork shoulder" "Write up a framework for MCP patterns I can give to claude code" "explain the biomechanics of motion in c. elegans" (I get this one, I mostly did it to test and it's related to my hobby project) Do we get an extra day of functional Fable 5 because it's down?
What does this have to do with anything? Who are you talking to? This is Hacker News, not Anthropic support.
Re: Potential session/cache leakage between workspace instances or consumer accounts
#47Re: Potential session/cache leakage between workspace instances or consumer accounts
#48Re: Potential session/cache leakage between workspace instances or consumer accounts
#49The alternative explanation is that the inference engine, which batches several unrelated requests for parallel processing, messed up the unpacking and returned an unrelated user’s query. This one would be very scary as it will leak arbitrary content, but it seems much less likely here.
Re: Potential session/cache leakage between workspace instances or consumer accounts
#50Caching doesn’t work the way the bug reporter implies. Caches are shared (at least across the enterprise), but its key is always a function of the input before it. We achieved significant savings simply by moving everything that varies across individuals out of the system prompt so every session starts from a cache point. For example you never want your system prompt to start with the time that the session started. M…
Caching is not supposed to work like that, but that doesn’t preclude the cache key computation function from having bugs.