Current evidence
The adapter has deterministic keyless lifecycle contract coverage. It has not completed a current private-staging credential smoke.
Create a Runloop sandbox
Authenticate to Wildflower Computer with its bearer key and send yourRunloop API key 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": "runloop", "image": "my-blueprint", "timeout": 300}'Capabilities and behavior
| Concern | Current behavior |
|---|---|
| Image | The image field is interpreted as a Runloop Blueprint name. The default starter image is used when omitted. |
| Lifetime | The timeout becomes the Devbox maximum lifetime and cannot exceed 172800 seconds. |
| Execution | The adapter waits for command completion and returns stdout, stderr, and the exit status. Truncated output is reported as an error. |
| Credential | Runloop API key; resolved from a project profile or supplied as an ephemeral inline override. |
Current limitations
- The timeout cannot exceed 172800 seconds.
- Truncated Runloop command output fails closed instead of returning a partial normalized result.
- Delete permanently shuts down the selected Devbox.
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 Runloop
- Use the Python SDK with Runloop
- Use the Rust SDK with Runloop
- Use the Go SDK with Runloop
- Use the Zig SDK with Runloop