# Disconnecting a machine

> Take it off the fleet from the panel, or off its cabinet from the machine. The seat frees for reuse at once; nothing on the machine is deleted.

There are two directions, and they are not the same thing.

## Off the fleet, from the panel

**Take off this fleet** on the machine's card takes the row off your workspace.
The machine stops appearing, nobody can open it from here any more, and **its
seat is free for another machine immediately** — so connecting a replacement
costs nothing. It is still paid for until your renewal; see
[and the bill](#and-the-bill).

This is what you do when the server is gone, or is being replaced.

## Off its cabinet, from the machine

```sh
sudo beafk cloud forget    # Linux
beafk cloud forget         # Mac
```

Run on the machine, this is the break-glass: the machine stops answering to any
cabinet at all, and **every browser it had let in is out at once** — no waiting
for anything to expire.

It asks you to **type the machine's own name** first. It ends everybody's
access, and the way back is a fresh code from a panel somebody may no longer be
able to reach. In a script, where there is nobody to type, pass `--yes`.

The agents are not touched. Chats carry on running on the machine
exactly as before; what has gone is the way in.

This is what you do when you no longer want us involved with a box you own.

## Which one cuts somebody off now

The machine does. Taking the row off here stops us signing anybody in from this
moment, but a browser already inside keeps what the machine gave it for up to an
hour — see
[cutting somebody off takes up to an hour](https://beafk.app/docs/reaching-your-machine.md#cutting-somebody-off-takes-up-to-an-hour).
`cloud forget`, run on the machine, is the one that is immediate.

## What is not deleted

Everything. Your repositories, your chats, the agents and their
sign-ins, the logs, the environment variables — all of it stays on the machine,
exactly where it was. Disconnecting is about who may open it, not about what is
on it.

Reconnecting later is [Connect a machine](https://beafk.app/docs/your-first-machine.md) again. The
machine still knows itself: same fingerprint, same projects, same history.

## And the bill

The seat frees on disconnect, so a replacement machine takes it at no charge and
you never pay twice for a swap.

What it does **not** do is make this month cheaper. Disconnecting is not
cancelling, and people meet that difference as a surprise on an invoice. See
[changing your plan](https://beafk.app/docs/changing-your-plan.md).

## Removing it entirely

If you are done with the server, disconnect it here and then destroy it at your
provider. Nothing in beafk can do that second part: we have no way to stop,
resize or delete a machine you own.

---

beafk documentation · Machines · https://beafk.app/docs/disconnecting-a-machine

In this section:
- What the install puts on your machine — https://beafk.app/docs/what-the-install-does.md
- Is the machine all right? — https://beafk.app/docs/is-the-machine-all-right.md
- Keeping every machine up to date — https://beafk.app/docs/keeping-machines-updated.md
- Disconnecting a machine — https://beafk.app/docs/disconnecting-a-machine.md (this page)
- Everything it wrote — https://beafk.app/docs/what-the-install-wrote.md

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