albedo docs

Remote, Colab, browser, and desktop

An agent can work on other machines over SSH, on Google Colab GPUs, in a headless browser, and in native desktop windows. You ask in plain words; this page covers what each needs from you first.

On this page: Remote machines over SSH, Google Colab runtimes, Browser, Desktop apps, and Code review images and web search.

Remote machines over SSH

Enabled by default. Albedo signs in to a host once and keeps that connection for everything it does there, so a hardware key is touched once rather than once per command.

nginx on deploy@box keeps restarting and i can't work out why. can you hop on and have a look with me?

i think the nginx config on box has drifted from the one in this repo. could you compare them and tell me what you'd keep?

Google Colab runtimes

Enable colab in /extensions to let an agent provision Colab GPU or TPU runtimes (T4, L4, A100) and work on them like any other remote machine. It needs an SSH public key in ~/.ssh.

let's try the fine-tune in train.py. can you grab a T4 on colab, run it, and bring the adapter home? stop the runtime when you're done so we don't burn units.

A runtime consumes compute units until it is stopped, so ask Albedo to stop it when the work is done. Have it copy results back first, because stopping discards the machine.

Browser

Enabled by default. Albedo drives Chrome or Chromium to load pages, click, type, and take screenshots. The Nix package bundles Chrome Headless Shell, so this works without setup.

the dev server is up at localhost:5173. can you look at the settings page at phone width, light and dark, and tell me honestly how it feels?

could you try signing up on staging like a new person would and tell me where you got stuck?

Desktop apps

Enable cua in /extensions to let an agent see and operate native desktop windows through cua-driver, in the background.

can you walk through onboarding in the simulator and screenshot each screen? i want to see it the way you saw it.

Put cua-driver on PATH, or set executable and socket in the "cua" section of extensions.json, or use $ALBEDO_CUA_DRIVER / $CUA_DRIVER_PATH / $ALBEDO_CUA_SOCKET.

Previous remote kernels Next daemon lifecycle