# Closing the tab

> Nothing stops. Agents run in processes of their own on the machine, so a lost phone, a closed tab or an update leaves them working.

## What keeps running

Every chat runs in a process of its own on your machine, under a
resource budget of its own so that one runaway agent cannot take the box down
with it. That process does not belong to your browser and does not know about
it.

So all of these leave the work running:

- closing the tab;
- locking your phone;
- losing signal, or going into a tunnel;
- your battery dying;
- beafk restarting to install an update;
- the machine's panel service being restarted;
- a crash at three in the morning.

## What happens when you come back

You open the same chat and the panel reattaches. A turn that was running
is still running, and you see it carry on. Whatever happened while you were away
is in the thread, in order.

Nothing has to be replayed and nothing has to be resumed by hand.

## Questions survive too

If the agent stopped to ask you something while you were gone, the question is
still open when you get back. It is not timed out in seconds and the process is
not tidied away: with nobody looking, a question is held for twelve hours — a
night, rather than a weekend. See
[when an agent needs you](https://beafk.app/docs/when-an-agent-needs-you.md).

And an answer you tapped just as the connection died is delivered when the
connection comes back.

## What does end a chat

- You stopping it.
- The machine itself going down — a reboot, or the server being destroyed. A
  reboot brings beafk back, but a process that was mid-turn is gone; the thread
  is still there and you can carry on from it.
- **Logging out of a Mac that is the machine.** On a Mac, beafk runs while you
  are logged in. Close the *phone* tab and nothing stops; log out of the Mac
  itself and the panel stops answering until you log in again. See
  [everything it wrote](https://beafk.app/docs/what-the-install-wrote.md).

Notably **not** on that list: `sudo beafk cloud forget`. It shuts every browser
out of the machine at once, and the agents inside carry on working — see
[disconnecting a machine](https://beafk.app/docs/disconnecting-a-machine.md).

## What about beafk cloud going down

Your machines keep working and your agents keep going — they never talk to us to
do their work.

What stops is **opening a new one**: that needs a fresh certificate, and those
come from us. A panel already open carries on until its hour runs out, and the
agents behind it carry on regardless.

If a machine cannot reach us for more than a day, it closes its door until it
can — again, without stopping the agents. See
[when a subscription lapses](https://beafk.app/docs/when-a-subscription-lapses.md).

---

beafk documentation · Agents · https://beafk.app/docs/closing-the-tab

In this section:
- Which agents beafk runs — https://beafk.app/docs/which-agents-beafk-runs.md
- Models, effort and permission — https://beafk.app/docs/models-effort-and-permission.md
- When an agent needs you — https://beafk.app/docs/when-an-agent-needs-you.md
- Closing the tab — https://beafk.app/docs/closing-the-tab.md (this page)

Every page, one line each: https://beafk.app/docs/llms.txt
All of it in one file: https://beafk.app/docs/llms-full.txt