# beafk

> Be afk. Keep shipping. Run Claude Code, Codex, Grok Build and Kimi Code together on your machine. Steer them from one chat on your phone.

beafk runs the agent CLIs their makers ship — Claude Code from Anthropic, Codex
from OpenAI, Grok Build from xAI and Kimi Code from Moonshot — on a machine you
own, and puts that machine on your phone. The agents are processes on your
hardware rather than tabs in a browser, so the work does not stop when you close
one. Nothing of yours is sent to us: your code, your conversations and the
agents' keys stay on your machine, and your browser talks to it directly.

The models are billed by whoever you already pay for that CLI, and the machine
is billed by whoever you rent it from. beafk sells a seat per connected machine
and nothing else.

## What it does

- **Not API wrappers. The real CLIs.** — Claude Code, Codex, Grok Build and Kimi Code run on your machine, signed in with your own accounts.
- **One prompt. A whole coding crew.** — Talk to one agent. It delegates scouting, building and review to the right CLIs, then brings every result back to the same thread.
- **No agent writes over another.** (you lose no work) — An agent takes the files before it edits them. The next one is told who is in there, by name, and waits.
- **More than a terminal. Your coding control room.** (one workspace) — Review diffs, inspect screenshots, answer blockers and steer every agent from the same mobile workspace.
- **Sketch twice. Build once.** (compare before you commit) — Get two clickable directions right in the chat. Compare them, choose the stronger one, and only the winner gets the full build.

## The site

- [The landing, as markdown](https://beafk.app/index.md): Be afk. Keep shipping.
- [Pricing](https://beafk.app/pricing): per connected machine, monthly or yearly; the first machine is free for a week
- [Mac app](https://beafk.app/mac): a beafk window on your own Mac, with no private network to configure — being built, not signed or downloadable yet
- [Terms of service](https://beafk.app/terms)
- [Privacy](https://beafk.app/privacy)

## Documentation

Every page is a screen at `/docs/<name>` and the same page as plain markdown at
`/docs/<name>.md`, which is what these link to. https://beafk.app/docs/llms-full.txt is all
of it in one fetch.

### Start here

- [What beafk is](https://beafk.app/docs/what-is-beafk.md): The agent CLIs you already pay for, kept working while you are away from the keyboard — on a machine you own, watched from your phone.
- [What it costs](https://beafk.app/docs/what-it-costs.md): Per machine, per month. Yearly is cheaper. The models and the servers are billed by other people.
- [What beafk does not do](https://beafk.app/docs/what-beafk-does-not-do.md): The honest list, so you can decide before you pay rather than after.
- [Questions people ask](https://beafk.app/docs/questions-people-ask.md): The ones asked before signing up, answered straight.
- [Moving from Cursor](https://beafk.app/docs/moving-from-cursor.md): beafk is not an editor and does not ask you to give one up. What carries over, what does not, and why there is no arrangement here that two other companies can end.
- [What you need before you start](https://beafk.app/docs/what-you-need.md): A machine, a Tailscale account, a subscription to at least one agent, and a phone. Nothing else.

### Your first machine

- [Your first machine](https://beafk.app/docs/your-first-machine.md): Press Connect a machine, paste the one line it gives you into the box, and open it on your phone — with a picture of every screen you will meet.
- [How your phone reaches it](https://beafk.app/docs/reaching-your-machine.md): Over your own private network, straight to the machine. Nothing you look at travels through beafk cloud.
- [Signing an agent in](https://beafk.app/docs/signing-an-agent-in.md): From your phone, in settings → providers. A code, a browser, done — and the key never leaves the machine.
- [A chat](https://beafk.app/docs/a-chat.md): One thread, one agent, and the folders you point it at. It keeps running whether or not you are looking, stopping a turn is one button, and you can have several at once.

### Agents

- [Which agents beafk runs](https://beafk.app/docs/which-agents-beafk-runs.md): The real Claude Code, Codex, Grok Build and Kimi Code, plus one more that does not chat — all on your own subscriptions.
- [Models, effort and permission](https://beafk.app/docs/models-effort-and-permission.md): Three knobs on every chat — which model, how hard it thinks, and what it may do without asking you first.
- [When an agent needs you](https://beafk.app/docs/when-an-agent-needs-you.md): The chat waits as long as it takes, the one that stopped says so, and an answer you tapped on a dead connection still arrives.
- [Closing the tab](https://beafk.app/docs/closing-the-tab.md): 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.

### Crew

- [What a crew is](https://beafk.app/docs/what-a-crew-is.md): Talk to one agent. It hands pieces to the right CLIs, and brings every result back to the same thread.
- [Writing a role](https://beafk.app/docs/writing-a-role.md): A name, a sentence about when to use it, an agent, a model, an effort — written once, so you stop describing the same colleague every morning.
- [Watching a crew](https://beafk.app/docs/watching-a-crew.md): A card for every piece of work handed out, the full transcript behind each, and one thread that tells you when they land.

### The panel

- [The home screen](https://beafk.app/docs/the-home-screen.md): One machine, one folder, and a row of seven tiles. Everything you see is scoped to the folder in the header, and moving folder moves the lot.
- [Settings](https://beafk.app/docs/settings.md): The settings screen pane by pane — how big the type is, what a new chat opens with, which chats keep running, and whether this machine is well.
- [Pictures, both ways](https://beafk.app/docs/pictures-both-ways.md): Send a screenshot into the thread, and get renders back in it — the agent posts what it made, not a description of it.
- [Seeing it before it is built](https://beafk.app/docs/seeing-it-before-it-is-built.md): Two clickable stubs in the chat for a minute of tokens. One tap picks the right one, and only that one gets built.
- [Running a line yourself](https://beafk.app/docs/the-terminal.md): A real terminal on the machine, from a phone — the modifiers a soft keyboard does not have, more than one pane at a time, and output that is still there tomorrow.
- [The keys a phone does not have](https://beafk.app/docs/keys-a-phone-does-not-have.md): ctrl, esc, tab and the arrows, as a row above the keyboard that does not scroll away — and a latch instead of a chord, because you cannot hold two keys with one thumb.

### Projects

- [Tasks](https://beafk.app/docs/tasks.md): Ask an agent to break the work into tasks, line a CLI up on each, and start them together — then one list shows who has what, what is waiting on you, and what finished while you were out.
- [Git](https://beafk.app/docs/git.md): Every branch, the diff, the graph, and a chat that works them — read the change on the train and send it up before your stop.
- [Commands](https://beafk.app/docs/commands.md): The lines your project is run by, as buttons on a phone — kept in the repository, so every machine has them.
- [Two agents, one file](https://beafk.app/docs/holding-files.md): Every agent on the machine takes the files it is about to edit, so a second one queues instead of writing over an hour of the first one's work.

### Articles

- [Articles](https://beafk.app/docs/articles.md): The SEO app writes pages into your repository as files, and your own site builds them — what it does, what it does not, and how the wiring goes.

### Skills and variables

- [Keeping every CLI in sync](https://beafk.app/docs/keeping-every-cli-in-sync.md): Skills, tool servers, roles and variables described once and delivered to Claude Code, Codex, Grok and Kimi in whatever shape each of them wants.
- [Variables](https://beafk.app/docs/variables.md): Every project's secrets — its database URL, its keys, any credentials the .env holds — kept once per folder and per machine, delivered where they are needed, encrypted, and masked until you ask.
- [Tool servers](https://beafk.app/docs/tool-servers.md): The outside services your agents can use — described once, delivered to every CLI, with the credentials kept out of the file.
- [Connecting Gmail](https://beafk.app/docs/connecting-gmail.md): The Gmail MCP server, the two Google Cloud gates that let a sign-in succeed and every call still fail, and the one thing it cannot do.
- [Skills](https://beafk.app/docs/skills.md): A page of instructions an agent reads before a certain kind of job — written once, read by every agent on the machine.

### Logs and usage

- [Logs and timings](https://beafk.app/docs/logs.md): Everything the machine said and everything that took time, in one searchable store — filtered down to what one chat actually did.
- [Telemetry](https://beafk.app/docs/telemetry.md): Send your machines' access events to an OpenTelemetry endpoint you own — PostHog, Better Stack, Datadog, Honeycomb, Grafana, Axiom or your own collector. Logs and traces stay on the machine.
- [Usage](https://beafk.app/docs/usage.md): What the agents spent, by model — on this machine, and across the whole fleet.
- [The trash](https://beafk.app/docs/the-trash.md): Nothing is deleted on your machine. Everything is moved, with a receipt, and one press brings it back for thirty days.

### Machines

- [What the install puts on your machine](https://beafk.app/docs/what-the-install-does.md): An account for the agents, a service on loopback, an address on your own network, the agents you pick, and a folder of state.
- [Is the machine all right?](https://beafk.app/docs/is-the-machine-all-right.md): The card on your fleet, the system screen — processor, memory, disk and which chat is spending them — and a health check that answers in sentences.
- [Keeping every machine up to date](https://beafk.app/docs/keeping-machines-updated.md): One screen for the whole fleet: what each machine runs, whether anything is behind, and one press to bring it up.
- [Disconnecting a machine](https://beafk.app/docs/disconnecting-a-machine.md): 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.
- [Everything it wrote](https://beafk.app/docs/what-the-install-wrote.md): The audit — every file the install put outside a home directory, what it never touches, and the handful of things a Mac does differently. For whoever answers for the box.

### Team

- [Workspaces](https://beafk.app/docs/workspaces.md): Who you share machines with. On your own you have one and never think about it; with a team it is the team.
- [Inviting people](https://beafk.app/docs/inviting-people.md): Invite by email with a role, change it, revoke it, remove somebody — and the two rules that stop a workspace locking itself out.
- [Who may open what](https://beafk.app/docs/who-may-open-what.md): Per-machine access — a machine belongs to whoever connected it, you name who to share it with, and read-only is for people who should not have a terminal. A colleague who cannot see a machine is not on its list.
- [The access log](https://beafk.app/docs/the-access-log.md): Who has opened what, by person — chained so it cannot be edited quietly, signed so you can keep the proof, and exportable.

### Security and privacy

- [What beafk can see](https://beafk.app/docs/what-beafk-can-see.md): Your machines' names and addresses, who is in your workspace, and who opened what. Not your code, your chats or your agents' keys.
- [Signing in](https://beafk.app/docs/signing-in-to-beafk.md): Google, GitHub or a password. Your browser gets one opaque cookie and nothing it could decode.
- [Two-factor](https://beafk.app/docs/two-factor.md): An authenticator app, enrolled in two steps on purpose — nothing is kept until six digits have proved you can read it.
- [Your browsers](https://beafk.app/docs/your-browsers.md): Every browser holding a session, and throwing one out — which takes effect on its very next request.
- [Deleting your account](https://beafk.app/docs/deleting-your-account.md): Immediate, with no grace period — and it tells you exactly what happens to each workspace before you confirm.

### Plans and billing

- [Plans](https://beafk.app/docs/plans.md): Individual, Teams and Enterprise. The unit is a machine, not a person, and the models are billed by whoever you already pay.
- [Changing your plan](https://beafk.app/docs/changing-your-plan.md): Add machines, move between Individual and Teams, switch to yearly, or stop — all from the billing screen.
- [When a subscription lapses](https://beafk.app/docs/when-a-subscription-lapses.md): A declined card or a cancelled plan closes the door, and nothing else. The agents keep running, nothing is deleted, and the machine is still yours.

### Reference

- [When something is wrong](https://beafk.app/docs/when-something-is-wrong.md): The dozen things that actually go wrong, what each one looks like, and where the fix is.
- [When a machine will not open](https://beafk.app/docs/a-machine-will-not-open.md): The card said it did not answer, and pressing try again did not help. What that is, in the order it usually is.
- [Glossary](https://beafk.app/docs/glossary.md): Every word this documentation uses, alphabetically, in one sentence each.
- [The command line](https://beafk.app/docs/every-command.md): The lines worth knowing on the machine itself, one each, in plain English. You can use beafk without ever opening this page.
- [Legal](https://beafk.app/docs/legal.md): Who you are dealing with, the proprietary licence, the terms you agreed to, what we hold, and who to write to.
- [The licence](https://beafk.app/docs/license.md): beafk is proprietary, both halves — the full text of what may and may not be done with the software, published rather than left in a repository nobody outside can open.