Repository navigation
Releases
BB Box 0.2.9
- One pointer at a time on Linux desktops. While the agent's pointer shows in the Box panel, the box's own small arrow no longer shows beside it: the video leaves the box's cursor out, and on Wayland the panel hides its copy. When the agent's place is forgotten (a person takes control, the box stops, restarts or is released), its pointer and click ring clear for every viewer and the box's own pointer comes back. A viewer that reconnects or joins with no agent place shows the box's pointer. See decision 105.
- Video viewers no longer freeze after a cursor switch. Switching the video's cursor could stop Selkies' capture for viewers that joined before it started, leaving a stale frame; bb-box now restarts video for every viewer that wants it and asks for a key frame once Selkies confirms the switch.
- On the agent's first action after its place was forgotten, the box's old arrow can show for a frame or a few (under about 150 ms) until the video restarts.
BB Box 0.2.8
- The live agent pointer changes shape on Linux desktops. In the Box panel, the agent's pointer now shows a hand after it clicks a link or button, an I-beam on a text field and while it types into one, and the arrow otherwise. It uses the same rules and hold times as recordings. A pixel click takes its element's role only from what that click read itself, so an old screenshot never gives a wrong shape; where the role is not known, the pointer stays the arrow. A viewer who opens the panel mid-action sees the same shape as one who was watching all along, and taking control clears the agent's pointer. See decision 105.
- Recordings show shapes for pixel clicks. A click by position now records its element's role when the click read it, so recordings on every OS show a hand or I-beam there too.
- macOS and Windows keep the cursor Cua Driver draws; device boxes have no live pointer.
BB Box 0.2.7
- GPU starts no longer refused by a half-read card. The host's GPU helper (bb-box-gpu 0.4.4) could get stuck reading only one of a host's GPUs after a single slow tick of nvidia-smi, and then refused every GPU box's start, even on a card that read fine, until it was restarted. It now keeps each card's last reading for up to 10 s, lets a missing card block only itself, retries a start on a missing card and refuses it after 60 s with the card named, and trusts only complete rows. The report names any unread card and clears its error at the next full reading, and the doctor counts that card's device nodes.
- A cancelled GPU start stays cancelled. When bb-box gives up on a start that is waiting for a card, it withdraws the request with a deadline of its own, even if Proxmox's answer was lost; if it cannot, it says the helper may still start the box.
- Updating the helper: run setup/proxmox-lxc/host/setup-gpu.sh on the host again to install 0.4.4.
BB Box 0.2.6
- Secrets are never printed back. Reading secrets from stdin printed the whole input when it refused it, and misread base64 ending in "=" padding as a bad line, so a valid credential file could be refused and then shown in the error. Values may now contain "=", and no message from the settings commands,
bb box config checkorapply, or a refused command line ever includes text read from a secret input or argument: not values, not names read from the input, not file paths. Errors name a line number, an argument's position or the setting it was meant for. - Config errors name places, not text. A rejected or unknown key or value in a configuration draft is named by its place; every backend's field checks name the field or the line, on the command line and on the settings page.
- A stricter secrets file. A line that is not
NAME=value, a comment or blank is now refused by its line number; it used to be skipped. - Names you choose, such as backend IDs, host names and box names, are still shown in listings and messages; never put a secret in a name.
BB Box 0.2.5
- The agent's pointer on Linux desktops. BB's desktop viewer now shows the agent's pointer and a ring where it clicks or scrolls on a Linux desktop, as on Windows and macOS. It is drawn only where Cua actually acted at a screen position; an action on a named element shows no pointer, because Linux gives no reliable place for it. It hides while you have control, and is forgotten when the box stops, restarts or is released. Recordings follow the same rule, and typing into a named field zooms only to what changed on the screen. At scale 2, element positions in recordings are no longer placed at half their size.
- iPhones stay offered on Namespace. A Mac released seconds after it started could cut BB Box's measurement short, which was read as "no iOS runtime" and withdrew iPhones for everyone. An unfinished measurement now counts as not known and is repeated; the offer follows the newest conclusive report of any kind of Mac; and reports saved by 0.2.4 are measured once more after the update. Tart and the SSH Mac pool use the same probe and get the same fix.
- No Files button over a screen. A box's screen bar no longer shows Files; it is in the bar's menu as Open files, and on the box's page and row.
BB Box 0.2.4
BB Box's own test suite now refuses to run on a machine that matters. This changes nothing for people using BB Box; it protects the machines of people working on it.
- Before any test runs, the suite checks the machine. It refuses where the user can run sudo without a password, runs as root, or has Tailscale installed, unless the machine is a BB Box box, a GitHub Actions run, or the person sets BBBOX_TESTS_MAY_BREAK_THIS_MACHINE=1. Every test file runs the check first, however it is started: npm test, node --test, node alone or Vitest. A sudo that does not answer in time counts as a refusal.
- The test fakes' stand-ins for privileged tools are stricter: file commands act only inside their own folders, and network and system tools run only in read-only forms.
- Earlier, tests run through a fake SSH host reached the machine's real sudo and logged it out of its tailnet. That can no longer happen on a machine the check protects.
BB Box 0.2.3
BB Box 0.2.3 brings Windows boxes back to their desktop. Install it from the plugin store, or pin it with git:https://github.com/ahkohd/bb-box.git@v0.2.3.
Windows boxes log in again
- The fault: the Windows images'
boxuser had a password that expired after Windows' default 42 days. On 13 November it did, and every new Windows box booted without signing in: no desktop, no computer use, and it could not join BB as a machine. Refreshes kept the old password date, so rebuilding did not help. - Images: the box user's password now never expires and the maximum password age is unlimited, set at first logon and at every refresh, on Proxmox QEMU and on Tart. The image check fails a build whose password can expire, and the doctor warns about an older image.
- Boxes already made: when a Windows box starts without its desktop because the password expired, BB Box sets both and restarts it once, only when Windows' own session list shows nobody logged in and both settings read back as set. Otherwise it changes nothing and the box's status says it is not ready for computer use, with the reason and the command to run.
The full list of changes: v0.2.2...v0.2.3
BB Box 0.2.2
BB Box 0.2.2 makes recordings work on every kind of box. Install it from the plugin store, or pin it with git:https://github.com/ahkohd/bb-box.git@v0.2.2.
Recordings on phones and Macs
- iPhone and Android:
box_recordnow makes a captioned clip on iOS Simulator boxes, including shared slots without root, and on Android emulators. Before, they had no ffmpeg and made no clip. - Macs: clips have their step captions again. The caption script read its text wrongly on macOS 26 and 27.
- How: when a box's own ffmpeg cannot make a clip, the box fetches a pinned ffmpeg 9.0.2 build from its publisher into the box user's own folder, checks its SHA-256, and checks it can encode one frame. BB Box itself publishes nothing; the builds and their GPL licences are listed in THIRD-PARTY.md.
- Safe on shared Macs: the cached build is used only while its folder and files are the box user's alone, unlinked and checked against their checksums; anything else is discarded and fetched again.
- Honest when it cannot: a device that cannot get a usable ffmpeg is refused at the start with the reason, and the doctor has a Recordings section for each kind of box.
- The clip page: an upright phone clip fits in the chat, and the video keeps its space however many steps there are.
The full list of changes: v0.2.1...v0.2.2
BB Box 0.2.1
BB Box 0.2.1 has no changes from 0.2.0 beyond its version number. It was cut by mistake before the recordings fix merged; that fix ships in 0.2.2.
The full list of changes: v0.2.0...v0.2.1
BB Box 0.2.0
BB Box 0.2.0 brings snapshots to almost every backend, more than one account per cloud, and steadier image rebuilds. Install it from the plugin store, or pin it with git:https://github.com/ahkohd/bb-box.git@v0.2.0.
Snapshots, restore and fork
- Docker: snapshots of a box's disk and Docker data, restore as a new container with an undo, forks that never come up as their source, and Keep, a snapshot that outlives its box on the same engine.
- Proxmox LXC: restore on ZFS, with a held copy as the undo.
- Proxmox QEMU: snapshots of Windows desktops and Android emulator boxes; restores recover from a node's restart.
- Tart: snapshots, restore, fork and Keep for dedicated iOS boxes, and snapshots of Windows desktops.
- Hetzner and Namespace: snapshots of Linux boxes on their host or machine.
- SSH host pool: machines now report whether they can snapshot. Snapshots there come in a later release.
- Every backend: a take says how long it will pause the box before it starts, measures the pause afterwards, and keeps listed sizes.
Accounts and projects
- Several Namespace workspaces and several boat.dev accounts, one backend each, so you can add capacity by adding an account.
- Backends kept for chosen BB projects: a project's threads use its backends first and fall back to the shared ones; other threads never use them.
- Namespace Macs:
box_grantworks on Mac boxes, and a size a workspace cannot fit is refused with a size that fits.
Images
- Rebuilds ride out busy hosts and archive outages: package downloads retry only when the archive fails, and a slow download is no longer cut off.
- Docker's first start is judged again from a fresh start when a busy host slowed the first, so healthy images no longer fail on a loaded host.
- An image is due again when any file it is built from changes, including after a failed rebuild once the build program changes.
- Wayland desktop images: the check waits for Sway before it reads its settings.
- Android: auto-rotate on in every posture of the Pixel Fold, and
bb-box-emulatorno longer mistakes the emulator's start for its end.
Computer use
- Password fields: where the platform marks a field as a password field (Android, iOS, Linux), screen reads show its value as
(hidden).
Monitor, docs and site
- Monitor: a card never steps back to an older reading of its box.
- Docs: a common questions page, platform requirements, and screenshots of a box's files.
- Site: landing page polish, a re-recorded demo, and docs with the Phosphor look.
The full list of changes: v0.1.0...v0.2.0