Mastodon Feed
jonny@neuromatch.social ("jonny (nonvenomous)") wrote:
I have actually experienced this one - it is supposed to have some tool to spawn background tasks so that it can cancel them, but like all its tools, it prefers to just do everything via the shell and routinely just forks a shell and forgets about it. It seems like it can also fork another agent session and forget about it, and then it becomes invisible to every mechanism of reporting to the user "you have an active session burning tokens"
So like, at every level, even the ones that should be totally deterministic like "the active logged in sessions for your account" are also somehow nondeterministic.