Ways to work · 3 of 3
Overnight
Close the laptop mid-thought. The session is not on the laptop; neither is the dev server, the database, or the build that was half done. In the morning they are where you left them, or further along.
This page is short because there is nothing to do. It says what is true when you are not there.
What keeps going
The environments. An environment's containers run until you stop them. A dev server that was up at midnight is up at six, and so is its database. The address answers whenever you open it.
The session. A Claude session on the box is a process in the workbench. If you gave it something long — a migration, a test suite, a /bettik-try of a large repository — it carries on after the phone locks, and its transcript is there when you come back. If it finished, it says so at the top of the conversation. If it is waiting on you — a question about a name, a destroy_environment it will not do alone — it is waiting.
The box. It is never suspended for being idle. It is a computer, and you do not hibernate somebody's computer.
What you come back to
You
What happened overnight?
Bettik
Box 6.2 of 16 GB used, 9.8 GB free Workbench [active] 110MB ssh <box>@home.<handle>.bettik.dev catan [active] node22-postgres17 app https://catan.home.<handle>.bettik.dev created 2d ago, last active 6h ago 610MB memory, 0.3% CPU catan-dark [active] node22-postgres17 app https://catan-dark.home.<handle>.bettik.dev cloned from catan created 9h ago, last active 7h ago Held right now: catan-dark write by "night-theme" since 9h ago [its session is not running just now — it can be revived, so the claim stands; ask its owner before taking it]
environment_status is the morning report: what is running, how much it holds, when it was last active, and who holds what. environment_logs is what an environment's containers printed while you slept — a build error, a crash loop, the query the app logged at 3 a.m.
You
Show me the last hundred lines of catan-dark's logs.
A session that stopped
A session with no process is asleep, not ended. Open it in the app and it revives with the same id and transcript. The claim it held is still held — which is why the report above says ask its owner rather than treating the environment as free. If the owner is you, take it back; that is what steal is for.
Two things worth doing before you close the laptop
Put the step you did by hand into seed or update. It costs one line at the time, and it is what makes the environment reproducible rather than a lucky copy — the one rule of the environment directory.
If the environment is one you would mind losing, save it. save_environment stops it for a few seconds and keeps it in your templates, where it survives the box.
Next: the box — the machine itself.