Personal defaults
Save your own defaults for playroom settings to avoid repeating flags every time.
Alpha
Playrooms are in active development. Commands, flags, and output may change between releases.
You can save your own defaults so you don't repeat flags every time. They're stored in ~/.acloud.yaml under defaults.playroom.*.
Precedence (highest wins): explicit flag > your config default > cached value (editor only) > built-in default
All available defaults
Prop
Type
Examples
acloud playroom config set image registry.avisi.cloud/library/playrooms/opencode:1.15.4-17
acloud playroom config set storage 20GiSEE ALSO
- Playroom overview: what a playroom is and why to use it
- playroom create: flags that personal defaults apply to
- playroom play: flags that personal defaults apply to
Lifecycle
Playrooms have a simple lifecycle: create/play, stop, start, and delete. Stopping a playroom keeps its storage but scales down compute to zero, while starting it again reuses the same storage. Deleting a playroom removes all its resources.
Data and secrets
How to get files, repos, environment variables, and SSH credentials into a playroom. It's all opt-in, and nothing leaks by default.