Track Sprites Dev Progress

Is there anywhere publicly posted to track the development of sprites or when certain features/tasks are completed? I’m really excited to use it, but there is a bit of friction that is preventing me from adopting it heavily.

Not having an ability to fork a checkpoint to another machine (creating a base image so I don’t have to reinstall/reconfigure the sprite) or easily transfer files via the cli to my sprite makes initial setup tedious.

Some amount of docs on the sprite-env command would be nice as well as an llms.txt or something so I can point claude code or other agentic tool at so it gets more context on the tool. Seems like there are a lot of cool possibilities of claude code using a sprite subagent to spin up some tasks or test and providing context that way. I’ve tried to do some simple stuff but seems like a little bit more documentation would help with making the agents more aware of the capabilities.

Being able to do some simple work in the browser would be really nice (being able to login to sprites.dev and being able to work there would be really cool and a great way to do work on the go on mobile devices or on the go).

3 Likes

Hi… Their docs site is back up now, at least, although it’s missing some pages that used to be there. It does still feature a large section on the sprites CLI, though, which was invisible for a while:

https://docs.sprites.dev/cli/commands/

This one is coming soon, according to an HN post, and it was said then that there’s already an API that works for such transfers.

This is also planned, but maybe not arriving as quickly. (Apparently, there are internal debates about what exactly the commands are and how ambitious they get.)

Hope this helps a little!

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.