Reference · when Bettik is down

When Bettik is down

A box is a computer. If everything of ours between you and it is down at once — the sign-in, the dashboard, the connector — the machine keeps running, and it keeps being yours. This page is what still works, and how to reach it.

What keeps working

the environments

Yes. They are containers on the machine; nothing on the box calls us at runtime. A dev server that was up stays up.

ssh

Yes. home.<handle>.bettik.dev is a direct record to the machine; by address if DNS itself is gone.

Claude Code on the box

Yes. A session in the workbench talks to Anthropic, not to us, so the box stays in your Claude app and sessions there keep working — including the tools, once the connector is back.

an environment in the browser, by its address

No. The gate on the box asks us about each address and who is opening it, and gets no answer. The tunnel below gives you the same site at localhost.

the connector's tools

No, while mcp.bettik.ai is down. Everything a tool does is also a command in the workbench, below.

the dashboard, the box's page, sign-in

No. The box does not care: it reports to us and is told nothing it needs.

Reaching an environment by tunnel

Each environment listens on a loopback port on the box, and the port is in its .env as _BETTIK_PORT. Forward it:

ssh -L 3000:127.0.0.1:$(ssh <box>@home.<handle>.bettik.dev 'grep ^_BETTIK_PORT= ~/environments/catan/.env | cut -d= -f2') <box>@home.<handle>.bettik.dev

Then http://localhost:3000 is the environment. The same works for a database, or anything else you declared in ports: its number is _BETTIK_PORT_<NAME> in the same file.

Doing what the tools do, by hand

The tools are conveniences over things the box can do itself. As root on the machine, where an environment's containers are named bettik-<box>-<environment>-<service> — bettik-<box>-catan-web, bettik-<box>-catan-db:

see what is running

docker ps

read an environment's logs

docker logs --tail 100 bettik-…-catan-web

bounce an environment

docker restart bettik-…-catan-web

stop and start

docker stop and docker start, by name. Data stays where it is.

Installing, cloning and saving environments wait for the connector: they need Bettik's own bookkeeping — ports, secrets, the hostname — and are not worth doing by hand for the length of an outage.

What to expect afterwards

Nothing to do. When sign-in is back, the addresses answer; when the connector is back, the tools do. Claims held by sessions are still held. The box's fact sheet catches up on its next heartbeat, and the dashboard stops saying quiet.