Start · about ten minutes
Quick start
You have an account and your box is running. By the end of this page Claude is on the box, the box is in your Claude app, and an environment of yours answers at its own address. Nothing here needs a terminal.
1. Sign Claude in on your box
Open the dashboard and tap your box — home.<handle>. That is the box's page, and its Claude Code card says Claude is not signed in. Tap sign in, then Start.
- The box runs the sign-in and the card shows you a link. Tap it.
- Sign in with your Claude account and approve. It gives you a code.
- Come back to the box's page, paste the code into the field that is waiting for it, and tap Finish.
That is all. Within a minute the box appears in the Claude app as a device called <box>.bettik.ai, and any session you start there runs on the box, in the workbench, with everything already set up.
A code belongs to the link it came from and works once. If you press Start again you get a fresh link, and the old code stops being accepted — so go through it in one pass.
2. Add the connector
Signing Claude in gives you sessions on the box. The connector gives every session — on the box, in the app, in Claude Code on a laptop — the tools to provision it. One address, added once:
https://mcp.bettik.ai/mcp
Settings → Connectors → add a custom connector, name it Bettik, paste the address. It asks you to sign in with your Bettik account the first time; after that it knows which boxes are yours.
With one box, nothing needs naming. With more than one, say which — Claude passes it as box: "<box>".
3. Say what you have
Start a session — on your phone, from the box's entry in the Claude app — and ask.
You
What do I have running?
Bettik
Box 4.1 of 16 GB used, 11.9 GB free Workbench [active] 98MB ssh <box>@home.<handle>.bettik.dev You have no environments. Use install_environment to install one — list_templates shows what is available.
The first line is the one that matters most as you go: memory is what limits how many environments run at once.
4. Install an environment
You
Make me somewhere to build a Next.js app with Postgres.
Claude
There are two starter kits: empty, an app container and nothing else, and node22-postgres17, Node 22 with Postgres 17 beside it. I'll use node22-postgres17. What should it be called? The name becomes the address — <name>.home.<handle>.bettik.dev — which you'll type and share for months.
You
catan
Bettik
Environment "catan" installed from "node22-postgres17". Runtime Node 22 (node:22-trixie-slim), listening on $PORT Services Postgres 17 at <environment>-db:5432, database app, role app projects/ empty -- create a project or clone one in, then start it from start Address https://catan.home.<handle>.bettik.dev will answer once there is a project and start starts it; nothing is running there yet. In the workbench it is ~/environments/catan.
Claude asks for the name rather than inventing one, on purpose: a box full of environments named after what they were installed from is a box nobody can navigate. Anything is accepted; punctuation becomes hyphens, and if the name had to change, it says so.
5. Put something in it
A starter kit, an environment template of kind kit, is a place to start. The project is yours to create or clone in.
You
Start a new Next.js app in it and get it running.
Claude
Claims the environment, runs create-next-app under projects/app, puts the start line in start, bounces the environment, and reads the logs until the dev server is up.
Bettik
https://catan.home.<handle>.bettik.dev answers. The first page takes a moment: a dev server compiles on first request.
Or hand it a repository:
You
/bettik-try https://github.com/you/some-repo
which reads what the repository says about itself, writes the environment's files, and builds until the address answers.
6. Save it
When the environment is the way you want it — the setup right, a project in it, fixtures loaded — save it as a template.
You
Save this as next-starter, a kit.
Bettik
Saved environment next-starter@s1 saved from "catan", a kit. projects/ app data as it was, contents included
It stops for a few seconds while its whole directory is captured, starts again, and becomes one of your templates, where it outlives the box. Now install_environment next-starter gives you the same thing again in a few seconds — on this box, or on the next one.
Where to go next
- From your phone — the session you just started, and what it is like to keep it going while you walk.
- Environments — everything you can do to one, and what is where inside it.
- The tools — every verb, as Claude sees it.