Current evidence
An inline credential completed create, idempotent replay, get, persistent commands, file write/read, list, delete, and deletion confirmation on private staging on July 28, 2026.
Create a Fly.io Sprites sandbox
Authenticate to Wildflower Computer with its bearer key and send yourFly.io Sprites API token separately in X-Provider-Api-Key. No additional provider routing header is required.
curl --fail-with-body "$WILDFLOWER_URL/v1/sandboxes" \ -H "Authorization: Bearer $WILDFLOWER_API_KEY" \ -H "X-Provider-Api-Key: $PROVIDER_API_KEY" \ -H "Content-Type: application/json" \ --data '{ "provider": "sprites"}'Capabilities and behavior
| Concern | Current behavior |
|---|---|
| Image | Sprites uses a fixed environment. The adapter rejects image rather than silently ignoring it. |
| Lifetime | Sprites automatically sleeps and persists until deletion. The adapter rejects timeout. |
| Execution | The adapter preserves separate stdout and stderr frames and returns the command exit code. |
| Credential | Fly.io Sprites API token; resolved from a project profile or supplied as an ephemeral inline override. |
Current limitations
- Image selection is not supported by the current adapter.
- A sandbox lifetime timeout is not supported by the current adapter.
- A cold Sprite can initially report stopped and wakes on its first command.
Tested compatibility
The adapter tests pin the request and response shapes used by Wildflower Computer. These labels describe the tested upstream contract; callers do not select a provider API version.
Use a generated SDK
Every generated client exposes the same lifecycle and typed provider creation inputs. The packages are generated from the versioned OpenAPI document and source model.
- Use the TypeScript SDK with Fly.io Sprites
- Use the Python SDK with Fly.io Sprites
- Use the Rust SDK with Fly.io Sprites
- Use the Go SDK with Fly.io Sprites
- Use the Zig SDK with Fly.io Sprites