Apps, Functions and Containers · 7 November 2026
Volumes are mounted
A version whose spec.volumes names a volume now mounts it in each copy before its process starts. Before, the version failed with deploy_build_failed: volumes cannot be read here yet. A volume that is still being created is waited for; one that does not exist, or was deleted after the request was accepted, fails the version with not_found. A POST, PUT or PATCH that sets spec.volumes needs volumes:attach; without it, the request returns 403.
Same day.
- Desktops: capture the screen with POST /v2/desktops/{id}:screenshot and drive it with POST /v2/desktops/{id}:actA screenshot returns the whole screen as base64, as png or jpeg (set quality, 1 to 100), with its width and height.
- Sandboxes: mount a volume through v2POST /v2/sandboxes accepts spec.volumes, a list of at most one {volume, path} entry naming a volume of the same project by its ID (vol_...).