I noticed over the past few days that after using a sprite (Claude Code session), it gets slower and slower. For example, a ‘git status’ can take a minute to respond. After a while, a sprite often becomes completely non-responsive: >sprite c Error: failed to start sprite command: failed to connec…

@mayailurus I am still on the free plan, but it seems they do have support plans which are prorated, so I paid $10 for 10 days and messaged them about it. Thanks for reporting this - we’ve seen, and are investigating, other reports of similar Sprites behavior. We are preparing a new version of the…

At first, I thought that the unknown status correlated with the timeouts when trying to list checkpoint or to start the Sprite. But now I see a Sprite having the unknown status while it can be started correctly and changes to status running. But the broken Sprite still has the timeout issues. So, t…

Just raising my hand to say I am running into the same issue. One of the main draws of Sprites for me was the easy filesystem persistence and checkpoint features. Now I have a Sprite that has become unresponsive and throws errors if I try to restore a previous checkpoint. This is nowhere near accept…

[image] New sprites sometimes randomly won't respond after creation Hi All, Appreciate your patience, as this is a new product. We are aware of these reports and are tracking a number of Sprites bugs that we are working to fix quickly. We have new releases c…

I’m also experiencing this. My sprite became completely unresponsive. Without a way to reboot it, I’m not sure what else I can do.

One odd observation I have is that the sprites that end up becoming non-responsive have a hostname of “sprite”, so the console shows sprite@sprite:~$ while the ones that behave normally have a hostname that is the sprite name: “sprite@:~$ These sprites were all created with sprite version 0.0.1-…

I to have a sprite that I am unable to log back into, that was last night. This morning I’ve been sitting on this prompt fro 2+ mins. [image] Any way to diagnose what might be the issue. Happy to help.

Same issue here. I cannot connect to my existing running sprite. I can create new sprites no problem, and as soon as I disconnect it goes to a warm state. The original sprite is just running idle. I also cannot create a new checkpoint. If only there was a way to reboot it somehow.

Still cannot access the locked sprite, days later.

I’ve noticed a lot of this too. Some notes: I think if you create a sprite with a name you’ve used before it messes up something and that sprite usually doesn’t work Long-running non-tty sprite exec commands seem to be quite shaky, and sometimes seem to brick sprites If your client doesn’t close w…