Documentation is sparse, or not even available? The API docs don’t tell you much about the service itself, and a Google search for docs returns an inaccessible website as the first result (https://docs.sprites.dev). Blog posts and forum threads and Claude skills shouldn’t be a substitute.

The snappiness of the sprites is very cool and I can definitely see it integrating into future Claude Code workflows. But the lack of a base container images means you’re still doing setup work on the sprite before you can begin development. I understand the philosophy is that sandboxes should be persistent, but Claude Code sessions also work better when isolated from each other, so it’d be nice to have some precepts to get a workspace setup quickly (given agentic coding is clearly a target).

I also found the CLI unintuitive but maybe that was just me!

So very cool idea but left with the impression that the Fly.io team’s should have spent a couple weeks on polish before shipping.

It neatly did so and "registered" it as a sprite service. Then I exited my session, waiting for the sprite to go idle, but I don't think it ever does.. Still have it active. Don't know how to idle it.

Can't tell for sure if this means I'm losing credits as there is no billing usage shown anywhere.

Also waiting for the moment where I can launch a sprite from another's checkpoint.

tpmjs is a registry of ai sdk npm packages (i created them for sprites), which you can add to personal collections, we automatically server your collections as mcp servers if you want.

Creating sprites in an example chat bot -> https://imgur.com/a/ETNxR1o

Creating sprites in claude desktop -> https://imgur.com/myC0U28

Listing out my sprites in claude desktop -> https://imgur.com/rgBU0jm

---

You can view the collection of tools here -> https://tpmjs.com/ajax/collections/sprites (fork it to use it yourself)

I'm looking into exe.dev and sprites.dev to build out extra features into tpmjs, agent sandboxes make a lot of sense.

Of course you can do similar with a VPS, but this makes it very easy (and cheap!) to spin up an entire new machine with a public url and HTTPS whenever you want to.

The Fly Machines orchestrator goes through some trouble to keep the source of truth for each VM decentralized, owned by the physical it runs on. But there's still global state --- apps, organizations, services. That stuff is all on Postgres. Postgres keeps up with it just fine but I'd be lying if I didn't say we're always looking out the corner of our eyes on metrics.

The global state for Sprites is on object storage. Each organization gets a separate SQLite database, and that database is synchronized to object storage with Litestream.io (Lightstream is load bearing in a bunch of places here; solid as a rock for us).

I think people really still sleep on the "multiple SQLite database" backing store design.

Tried with xterm, tilix and ghostty, all of which support the title setter escape sequence locally. For some reason, these get messed up (smells like edge case with escaping) and the result looks like this:

    $ sprite c  ": history-search-backward'
    \]\u@\h\[\]:\[\]\w\[\]\$ '                           ": history-search-forward'sprite@sprite:~$
    "sprite@sprite:~$

Also I like a lot of what you get built-in with Fly machines(ex:Grafana). So I am curious how this would fit in my workflow. Maybe Sprites for rapid development and toy projects, and move to a Fly machine when I need something a little more beefy?

Looking forward to checking this out.

While looking into giving fly another shot as a cloud provider even though I think it's still pretty much a commodity for me, I found an issue in Google: I searched for "fly.io sao paolo" and the title of the first result on fly.io is "Regiones · Fly Docs", translated from english to Spanish. While I find the translation in titles on Google annoying, I haven't often seen the characters messed up like this. I reproduced this in Incognito at this URL: https://www.google.com/search?hl=es&q=fly.io%20sao%20paolo

I realize this is all very fresh, but still wondering…

I just want an easier way to connect to and launch sprites from my phone.

any ideas there?

Is that what you guys are thinking of? I get that Sprites are a new primitive, but I feel confused as hell about what exactly I'd want to do with it.

I believe currently the sprites CLI is using websockets to handle the connection, and the external proxy when you make a sprite public doesn’t handle websockets correctly?

Does that sound right?

[1] https://github.com/danthegoodman1/checker

>Now, today, under the hood, Sprites are still Fly Machines. But they all run from a standard container.

So its basically a faster VM?

What are some use cases for this that benefit from the faster boot time?

What did the bracket in the slack channel determine was “Chicago’s best sandwich”? Or the top three, even? I’m always looking for new sandwiches.

Off the top of my head, I might nominate,

- the pork tenderloin at JT’s

- the Big L from Fontano’s (hot take, I know; it might go to Graziano’s if they hinge-cut the bread, but not doing so is a fatal flaw to me)

- the Cambodian fried chicken sandwich that’s occasionally available at Hermosa

- honorable mention: the comically oversized chicken torta at Migos

(Edit: I inexcusably transposed Bari and Fontano’s; the nomination is intended for Fontano’s)