https://web.archive.org/web/20260516145550/https://planetsca...
https://web.archive.org/web/20260910204345/https://planetsca...
30 karma · joined January 20, 2026
https://web.archive.org/web/20260516145550/https://planetsca...
https://web.archive.org/web/20260910204345/https://planetsca...
I wonder if it would even get flagged in that case, because wouldn't the probability distribution of a token when the LLM is suggesting an edit to your writing be different than the distribution of that token once it is in the context of the text it's editing?
You would think, but the initial implementation of this stripped ICC profiles (https://github.com/oven-sh/bun/issues/30197), and while that was fixed in time for the release, it still currently doesn't understand EXIF rotation metadata (https://github.com/oven-sh/bun/issues/30235) or high-bit-depth images (https://github.com/oven-sh/bun/issues/30462)
All you have to do is attach to the process before it does that, and then prevent this call from going through.
I was wondering about that statement. Shouldn't it restrict sampling to only tokens that produce valid JSON matching the schema during a tool call? On the other hand, I have heard a lot about how even production LLM providers don't always call tools accurately, so I suppose either it's hard to implement what I described or there's something I haven't thought of that makes it impossible.
> More direct control over updates, including the ability to pause updates for as long as you need
So it does sound like you'll be able to pause updates forever and also therefore not automatically reboot.
Still a good read though.