Sprites

No. The exec tool runs commands inside a Sprite, which Fly.io describes as a hardware-isolated Firecracker microVM in its cloud, not on your computer. Nothing executes locally, and the connector reaches only Sprites owned by the Fly.io organization you pick during the OAuth flow.

Anything. Sprites documents outbound access as unrestricted by default, so a fresh Sprite can resolve and reach any domain. Tightening it is opt-in through a network policy, a DNS-based allowlist applied from outside the Sprite. The policy_network_update tool is how the connector applies that restriction.

Not by itself. Every Sprite has an HTTPS URL, but Sprites documents it as private by default and reachable only by members of your organization. Switching a URL to public is a separate sprite config update command, and no tool in the connector's 18 published names performs that switch.

No. Sprites states plainly that destroy_sprite permanently deletes a Sprite and its data with no undo. Checkpoints protect against a bad command inside a surviving Sprite, not against the Sprite being removed. Restrict the connector token to a name prefix so it can only reach Sprites you created for it.

The writable filesystem overlay. Sprites lists files, directories, installed packages, config files and on-disk databases as captured, and running processes, in-memory state and open network connections as not captured. Restoring replaces your current filesystem with the saved one, and the state you overwrite is not backed up for you.

Yes, and the default already does. Sprites issues a restricted token that can only create Sprites whose names begin with mcp- and caps how many. The consent screen lets you change the prefix, raise or lower the cap, or switch to full access across the organization. Sprites recommends staying restricted.

Yes, while they run. Sprites bills compute per second and only while a Sprite is active, so an idle Sprite costs no compute. Storage is billed on bytes actually written against a 100 GB per-Sprite ceiling, and kept checkpoint blocks bill separately. Fly.io publishes no pricing page in the Sprites documentation.

The Sprite was cold and is still waking. Sprites documents cold wakes as taking one to two seconds, and its troubleshooting tells you to wait a few seconds and run the same tool again. A warm Sprite resumes in 100 to 500 milliseconds instead, with running processes preserved.