Every sprite creation request fails with {"error":"failed to create sprite"}. Listing works fine.
# Works
sprite api /sprites
# {"sprites":[],"next_continuation_token":null,"has_more":true}
# Fails with 500
sprite api /sprites -X POST -H "Content-Type: application/json" -d '{"name":"test-sprite"}'
# {"error":"failed to create sprite"}
Tried fresh login, direct curl, cli, same result every time. I refreshed my account with credits as well.
2. Listing has significant lag / console mismatch
Sprites created by our backend (via the SDK) don’t appear in sprite list for what seems like hours. Last night our E2E tests created ~10 sprites, but this morning sprite list still showed empty. They eventually appeared, and I could destroy them successfully.
There also seems to be a mismatch between what the CLI reports and what the sprites.dev console shows.
What I expected
Create should return 201 with sprite details
List should show sprites within seconds of creation
Environment
CLI: sprite v0.0.1-rc30
Orgs: eno-reyes, factory-ai
Account created: Jan 18, 2026
The generic error message doesn’t tell me what’s actually wrong. Is there an account setup step I’m missing, or is something broken on the API side?
Hey folks! Think we’ve found what’s causing these 500s for you, we’re working on a fix.
@enoreyes The list latency is odd. It could possibly be related to the 500s though. Would you mind sharing the name of one of the sprites you saw the lag on?
same for the api: curl -X POST “``https://api.sprites.dev/v1/sprites``” -H “Authorization: Bearer $SPRITES_TOKEN” -H “Content-Type: application/json” -d ‘{“name”:“my-sprite”}’ {“error”:“failed to create sprite”}%
Ok the 500 errors should be fixed. @crro , @enoreyes and @onei please retry and let me know if you see any issues.
It looks like we had an underlying VM that was deleted but not correctly marked as such. We then tried to place your Sprites on those which failed for obvious reasons . That’s been fixed and we’ll make a change to handle this gracefully going forward.
@enoreyes I suspect this is unrelated to the 500 errors. I took a look at the Sprites you mentioned. They were created correctly and should have been returned immediately. I also didn’t find any errors on the backend that would have surfaced if there was an issue pulling them.
You mentioned you’re using two orgs, my suspicion is that the sprite cli was picking up the wrong org for the list command.
If you see this again, can you try using the -o or -org flag to explicitly specify the org you expect the Sprite would be in? sprite api -o <org> /v1/sprites will also show exactly what the CLI is getting from the API. If you see similar behaviour again using the explicit flags, please do let us know.
If you want, you can try using dev CLI releases channel using sprite upgrade --channel dev. That channel has some improvements to multi-org handling that haven’t yet made it to the general release.
. That’s been fixed and we’ll make a change to handle this gracefully going forward.