browser-use · mathisdittrich · May 7, 2026
diff --git a/docs/cloud/bux/authentication.mdx b/docs/cloud/bux/authentication.mdx
@@ -0,0 +1,27 @@
+---
+title: "Authentication"
+icon: "lock"
+---
+
+A BUX is only as useful as the accounts it can reach. Authentication uses [Browser Use Profiles](https://cloud.browser-use.com/profiles): reusable bundles of cookies and storage attached to your account. You can sync them from your local Chrome ([here](/cloud/guides/profile-sync)) or build them by hand from the dashboard ([here](https://cloud.browser-use.com/profiles)).
+
+We highly encourage you to either sync your local cookies or create profiles manually from the dashboard ahead of time. If you have not done that, or the agent needs access to a site you have not authorised yet, the live login flow kicks in.
+
+## Live login
+
+When the agent hits a login wall, it sends you a live URL from the VM's remote browser. You sign in once and BUX saves the cookies for next time.
+
+<Steps>
+  <Step title="Agent hits a login wall">
+    Claude Code detects the credential prompt and pauses.
+  </Step>
+  <Step title="BUX sends you a live URL">
+    The URL streams the VM's actual Chrome to your laptop or phone. Open it in any browser.
+  </Step>
+  <Step title="You sign in">
+    Type your password, complete 2FA, do whatever the site asks. The site sees a real browser with a real user.
+  </Step>
+  <Step title="BUX captures the session">
+    Cookies and storage are saved into a profile attached to your account. The agent picks up where it left off, and every later run reuses the profile.
+  </Step>
+</Steps>
diff --git a/docs/cloud/bux/images/bux-setup.png b/docs/cloud/bux/images/bux-setup.png
diff --git a/docs/cloud/bux/images/web-terminal.png b/docs/cloud/bux/images/web-terminal.png
diff --git a/docs/cloud/bux/interfaces.mdx b/docs/cloud/bux/interfaces.mdx
@@ -0,0 +1,28 @@
+---
+title: "Interfaces"
+icon: "signal"
+---
+
+The interfaces we ship pre-built are simple: set up a [Telegram bot](#telegram) once and text it from your phone, open the [web terminal](#web-terminal) hosted in our cloud, or [SSH](#ssh) in from your local terminal like any other cloud machine. All three share the same context, so switching mid-task does not lose state.
+
+Because it is a cloud computer, you can wire up any other interface on top: Slack, Discord, or anything you need. The [`bux`](https://github.com/browser-use/bux) repo is open source, so if your bridge would help others, send a PR.
+
+## Telegram
+
+The primary interface for most users. After you link a bot during [setup](/cloud/bux/quickstart), every message you send becomes a prompt, and the agent's replies (text and screenshots) come back in the same chat.
+
+In our Telegram setup, you can have a forum where each topic is its own Claude Code or Codex session. That way you can run several sessions in parallel and context does not get mixed up.
+
+## Web terminal
+
+On [cloud.browser-use.com/bux](https://cloud.browser-use.com/bux) you can access the terminal of your cloud computer. This is useful for making fundamental changes or working from your laptop. You can of course also use Claude Code in the normal setup there. It's also handy to reach your cloud computer's terminal from the smartphone.
+
+<Frame>
+  <img src="/cloud/bux/images/web-terminal.png" alt="The cloud.browser-use.com/bux web terminal. Claude Code running inside the BUX VM, with session info and SSH access in the sidebar." />
+</Frame>
+
+
+## SSH
+
+If wanted, you can also SSH into your BUX from your local terminal. The SSH endpoint is shown in the dashboard once your VM is running.
+
diff --git a/docs/cloud/bux/introduction.mdx b/docs/cloud/bux/introduction.mdx
@@ -0,0 +1,51 @@
+---
+title: "Introduction"
+icon: "cube"
+---
+
+## What is BUX?
+
+Browser Use Box (BUX) is a 24/7 cloud computer with an agent (for example Claude Code, Codex, Hermes or Openclaw) and [Browser Harness](https://github.com/browser-use/browser-harness), controlled from anywhere (for example Telegram, the web, or SSH).
+
+<Frame>
+  <img src="/cloud/bux/images/bux-setup.png" alt="BUX setup. Smartphone (Telegram bot), Browser Use Cloud web terminal, and SSH from your local terminal on the left; the BUX VM (EC2 on AWS, 24/7) running Claude Code and Browser Harness on the right." />
+</Frame>
+
+## What to use it for
+
+You can use BUX purely as a cloud agent infrastructure: a box for Hermes, Openclaw, Claude Code, or Codex to run on while your laptop is shut. But the combination of your agent and Browser Harness is what makes it magical, because that way your agent can do any task on the web.
+
+BUX completes tasks in complicated dashboards (Microsoft Azure, Google Workspace, anything behind SSO) where browser agents have historically struggled. From a phone on the go, between meetings, or anywhere with a network, you can throw any task at it:
+
+> "deploy PR #235 to staging and test the new flow"
+
+> "book the earliest flight Zurich to SF next Wednesday"
+
+> "take a picture of our granola, order this on Amazon"
+
+> "cancel my Paramount+ subscription"
+
+Across the team, we have yet to find a work-related or everyday-web task that BUX cannot complete.
+
+## How it works
+
+Because BUX is a real cloud computer that you have full access to, it is extremely flexible. You can drive it from any interface, install your own software on it, and modify it however you want.
+
+In the beginning, a BUX VM boots in 30 to 60 seconds from a pre-baked AMI running the open-source [`bux`](https://github.com/browser-use/bux) stack: Claude Code, Browser Harness, the Telegram bridge, and the web terminal, all under systemd. Once you log in to Claude and connect a Telegram bot, you have a 24/7 personal agent.
+
+The VM runs under a locked-down IAM role with zero AWS permissions, so it cannot touch your infrastructure or ours. The browser session inside the VM rotates every 240 minutes as a security measure.
+
+Agent state lives in `/home/bux` and survives reboots, so cookies, learned skills, and chat history all persist.
+
+Prefer to run it yourself? Point the [bux installer](https://github.com/browser-use/bux) at any Ubuntu VPS, Mac mini, or Raspberry Pi (anything with ≥2 GB RAM). It's the same software the managed VMs run.
+
+## Giving your agent access
+
+BUX is only as useful as the accounts it can reach. Use [Browser Use Profiles](https://cloud.browser-use.com/profiles) to sync your local Chrome cookies or build new ones by hand.
+
+When the agent hits a login wall, it sends you a live URL from the remote browser. You sign in, it picks up where it left off, and saves the cookies for next time.
+
+## Next
+
+- [Quickstart](/cloud/bux/quickstart): set up your BUX in under five minutes.
+- [Authentication](/cloud/bux/authentication): give the agent access to your accounts.
diff --git a/docs/cloud/bux/quickstart.mdx b/docs/cloud/bux/quickstart.mdx
@@ -0,0 +1,25 @@
+---
+title: "Quickstart"
+description: "Set up a BUX in a few clicks. It takes less than five minutes."
+icon: "rocket"
+---
+
+You need a Browser Use account and access to Claude Code or Codex. Then:
+
+<Steps>
+  <Step title="Start your VM">
+    Go to [cloud.browser-use.com/bux](https://cloud.browser-use.com/bux) and start a box. The VM boots in 30 to 60 seconds from a pre-baked AMI with Browser Use and Claude Code pre-installed.
+  </Step>
+  <Step title="Connect a Telegram bot">
+    Two ways to set this up:
+
+    - Scan the QR code displayed and we do the Telegram setup for you.
+    - Create the bot on your own (via [@BotFather](https://t.me/BotFather)) and paste in the bot token.
+  </Step>
+  <Step title="Log in to Claude Code / Codex">
+    The web terminal prints a one-time login link. Open it, authorise, paste the token back. From here on, every Telegram message goes into the same resumed agent session, so context persists.
+  </Step>
+  <Step title="Start using it">
+    Send a message to your Telegram bot to fire off your first task. You can also drive a BUX from the web terminal or over SSH; see [Interfaces](/cloud/bux/interfaces).
+  </Step>
+</Steps>
diff --git a/docs/docs.json b/docs/docs.json
@@ -99,6 +99,16 @@
                         ]
                       }
                     ]
+                  },
+                  {
+                    "group": "BUX",
+                    "icon": "cube",
+                    "pages": [
+                      "cloud/bux/introduction",
+                      "cloud/bux/quickstart",
+                      "cloud/bux/interfaces",
+                      "cloud/bux/authentication"
+                    ]
                   }
                 ]
               },