Getting started
From zero to a running playroom: create, connect, work, stop, start, and delete.
This guide walks you through the full playroom lifecycle end-to-end. You'll create a playroom, connect to it, run an AI agent, stop it, start it again, and finally delete it.
Prerequisites
Before you start, make sure you have:
Logged in to Avisi Cloud
acloud auth loginA Playhouse cluster available
list playrooms in a Playhouse to verify you have access (PLAYHOUSE > Your Playhouse slug)
acloud playroom list -p PLAYHOUSEAsk your team or platform admin for the Playhouse slug if you don't have one.
1. Create a playroom
Create your first playroom inside the Playhouse:
acloud playroom create my-first-room -p PLAYHOUSEThe CLI will wait until the playroom is ready. You'll see output confirming it's running.
The playroom is named my-first-room. It gets its own persistent home directory at /home/playroom, and data here survives stop/start.
See playroom create for all available flags: image, storage size, CPU/memory limits, git cloning, and more.
2. Connect
SSH into the running playroom:
Currently with the use of Tailscale, make sure it's running.
acloud playroom connect my-first-room -p PLAYHOUSEYou're now inside the playroom. It's a regular Linux shell, so you can run commands, clone repos, or start an agent.
See playroom connect for all available flags: SSH agent forwarding, custom user, port forwarding, and more.
3. Open in your editor
Prefer working in an editor? Open the playroom directly from your local machine:
acloud playroom open my-first-room -p PLAYHOUSE --editor vscodeacloud playroom open my-first-room -p PLAYHOUSE --editor intellijacloud playroom open my-first-room -p PLAYHOUSE --editor webstormSee playroom open for all available flags: editor selection, last-used playroom shorthand, and more.
4. Talk to an AI agent
Once you're inside, start the agent (run this in the playroom terminal, not your local one):
opencodeYou're now working with AI. Ask it to create something, for example a simple HTML page:
"Create a simple HTML file here in this folder that sells cookies"
5. Stop the playroom
Done for now? Stop the playroom to free up compute. Your files are kept.
acloud playroom stop my-first-room -p PLAYHOUSECheck the status:
acloud playroom list -p PLAYHOUSE --mineThe playroom shows as stopped. Storage, including the HTML file you created, is still there.
See playroom stop and playroom list for all available flags.
6. Start it again
Pick up where you left off:
acloud playroom start my-first-room -p PLAYHOUSEConnect again and verify your files are still there:
acloud playroom connect my-first-room -p PLAYHOUSE
ls /home/playroomSee playroom start for all available flags.
7. Delete the playroom
When you're done and no longer need the playroom, delete it to clean up all resources:
acloud playroom delete my-first-room -p PLAYHOUSEThis is permanent
Deleting removes the playroom and all its storage. There is no undo.
See playroom delete for all available flags, including --force to delete a playroom owned by another user.
What's next
Want to skip the manual create/connect steps next time? Use playroom play: it creates a playroom, uploads your local directory, and connects in one command.
- Playroom overview: what a playroom is and why to use it
- How it works: understand what's running under the hood
- Data and secrets: bring in files, repos, and API tokens
- Personal defaults: save your Playhouse and image so you never repeat flags