Computers for BB threads

Boxes have the thread's Git access, its variables and BB itself. You and the agent share them: the agent works in the box, and you can open its desktop or terminal at any time.

• Each thread gets its own computerstry it

  Boxes

  • proud-craneLinuxDesktopContainer

    Ready in 0.8 s · BB machine in 4.6 s · 4 cores · 8 GiB

  • clear-cometLinuxmicroVM

    Ready in 1.4 s · BB machine in 9.2 s · 2 cores · 4 GiB · 32 GiB

  Select a box's name for its details, or try its buttons.

  Boxes have the thread’s Git access, its variables and BB itself.

• Any providertry it

  System

  LinuxServers and desktopsmacOSOn a Mac with Apple siliconWindowsWindows 11 desktops

  Type

  ServerTerminalDesktopScreen · Terminal · Computer use

  Resources

  Small2 cores · 4 GiBMedium4 cores · 8 GiBLarge8 cores · 16 GiB

  Provider

  First with roomAny of the 9 below, in orderDockerContainers on the machine that runs BB, another host over SSH, or a BB machine with Docker, such as a Windows PC with WSLmicrosandboxMicroVMs, each with a kernel of its own, on a Linux host with KVM or a Mac with Apple silicon: an option beside Docker, not the defaultProxmox LXCContainers on a Proxmox VE hostProxmox QEMUVirtual machines on a Proxmox VE hostTartVirtual machines on your Macs with Apple siliconSSH host poolMachines over SSH, physical or a VPSHetzner CloudContainers on x86 or Arm Docker hosts BB Box rents in your Hetzner Cloud project as boxes need them, and deletes when idleNamespaceA Namespace machine for each box, a Mac or a Linux machine, rented by the minute in your Namespace workspace, within its plan’s limitsboat.devA boat.dev sandbox for each box, a Linux VM forked from BB Box’s template in seconds and billed by the second

  Create box

  Choose a system, a type, a size and where it goes.

  Docker, Proxmox, microsandbox, Macs with Tart, machines over SSH, or Hetzner Cloud, Namespace and boat.dev.

• Shared desktopstry it

  proud-craneThe agent has control.Take control

  Applicationsexample.com — Browser09:41

  example.com

  Example DomainContinue

  agent

  The agent is using the desktop. Take control to use it.

  You and the agent use the same screen. The agent waits while you have control.

• Recordings that show the work

  

  An agent records its test run as a short clip, with each step and its result captioned. See Recordings.

• Every machine at a glancetry it

  Watching proud-crane

  BusyLinux · x86_64host up 1h 12m

  CPU

  100%

  busy · 4 cores

  MemoryNormal

  52%

  4.2 of 8 GiB

  Live-looking numbers from a sample box. Try the menus.

  CPU, memory, disk, GPU and processes of every box and machine, in BB’s sidebar. See the Monitor.

• Ready in seconds. A box is usually ready in seconds, and a warm box at once.
• Phones and tablets to test apps on. An iPhone or iPad in the iOS Simulator, or an Android device in its emulator. See device boxes.
• GPUs. A box can share an NVIDIA card or have one to itself, with nvidia-smi, CUDA and PyTorch ready, on supported backends. See GPU boxes.
• Snapshot, undo and fork. Save a box before a risky change, restore it with an undo, or fork it into a fresh box with its own identity. See snapshots.
• Resize as you go. More cores, memory, disk or a GPU when a build needs them, from the Box panel, the box’s page or the agent. See resizing a box.
• Keep boxes as your own machines. Threads can run on them, such as an always-on agent with its own desktop.
• Files. Browse, search and edit a box’s files in a tab. See a box’s files.

Paste this into a BB thread. Its agent installs BB Box, sets up a backend and proves it with a box.

Set up BB Box for me: the BB plugin that gives threads computers of their own, called boxes.

1. Install it: bb plugin install git:https://github.com/ahkohd/bb-box.git@main --yes
2. Follow its bb-box-setup skill. If your skills do not list it yet, find it with bb skill list and read it with bb skill show <id>.
3. Look at the machine that runs BB with bb box doctor, and set up the backend the skill suggests for it: Docker on Linux or in WSL 2 on Windows, microsandbox on a Mac with Apple silicon.
4. Ask me first before anything that needs root, changes BB's settings, or makes Docker boxes privileged containers, which can take over the machine they run on.
5. Prove it: bb box kinds, then bb box acquire with the Linux kind it lists, then bb box run <box> "uname -a", then bb box release <box>.
6. Tell me what you set up, what bb box doctor says, and what is left for me to do.

The quick start: https://bbbox.dev/start/quick-start.md