Potential session/cache leakage between workspace instances or consumer accounts
1–10 of 151 posts
Re: Potential session/cache leakage between workspace instances or consumer accounts
#2Relevant comment from the OP which makes a hallucination more likely:
> There is one tool call result that includes a string that printed a pathname including minecraft.py because it was listing the files in a Python virtual environment and the Pygments package has a lexer called minecraft.py
Re: Potential session/cache leakage between workspace instances or consumer accounts
#3Re: Potential session/cache leakage between workspace instances or consumer accounts
#4Sounds like a hallucination unless proven otherwise, even the leading LLMs can do those from time to time, and they will always appear plausible like that. Also could be the session having a lot previous context, like 800K+, which (I think) makes hallucinations more likely. Relevant comment from the OP which makes a hallucination more likely: > There is one tool call result that includes a string that printed a pathn…
It's unfortunate that there is so little transparency that even if they deny there was a leak we will never know for certain.
Re: Potential session/cache leakage between workspace instances or consumer accounts
#5Oh yes, we do not need programmers any more…
Re: Potential session/cache leakage between workspace instances or consumer accounts
#6Oh yes, we do not need programmers any more…
Re: Potential session/cache leakage between workspace instances or consumer accounts
#7"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?
Re: Potential session/cache leakage between workspace instances or consumer accounts
#8We 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. Move that to the first user message if needed.