Live data from Hacker News

Potential session/cache leakage between workspace instances or consumer accounts

github.com

1–10 of 151 posts

Re: Potential session/cache leakage between workspace instances or consumer accounts

#2
Sounds 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 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

#4
post #2

Sounds 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…

I don't disagree but this sort of thing has to be investigated regardless.

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

#7
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?

Re: Potential session/cache leakage between workspace instances or consumer accounts

#8
Caching 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. Move that to the first user message if needed.

Re: Potential session/cache leakage between workspace instances or consumer accounts

#9
post #5
post #3

Oh yes, we do not need programmers any more…

"Coding is largely solved"

I love that quote, especially considering the insane amount of bugs that are produced. It’s as easy to debunk as someone claiming ”I can jump to the moon”.

Re: Potential session/cache leakage between workspace instances or consumer accounts

#10
post #5
post #3

Oh yes, we do not need programmers any more…

"Coding is largely solved"

While abused by LLM vendors, that phrase in one form or another I've been hearing since the early '00s and it's likely way older.
Post reply on HN