The workbench in a tab.
Open commandagi.com/app and the whole shell is there, with your account's Drive and the platform's agents. Plug a printer or an arm into the computer, and the page talks to it through the browser's own serial and Bluetooth.
What runs in the page
Nothing to install, the browser is the host.
In a tab, the page runs the shell, the editors and each code part in a Web Worker of its own. Your files are in your account's Drive (cloud://home/…) or in this browser's own storage (browser://…). A device plugged into this computer is reached through the browser, after you pick it.
Fetched for this page
One page, 39 files.
The study fetched /app from production and every first-party script and stylesheet its HTML names, as a browser does on its first visit.
- the page's HTML
- 5,481 bytes
- first-party scripts and stylesheets it names
- 39
- their size uncompressed (3,263,595 bytes)
- 3.26 MB
https://commandagi.com/appOutput case-studies/browser-tab/stats.jsonTool scripts/sites/case-studies.mjs browser-tabRan on This computer (dell-gb10-1), fetching productionWhen Devices from the page
16 drivers run in the tab.
Grbl, Marlin and Smoothie printers and mills, Feetech and Dynamixel servo buses, a toy drone's radio and DeskAssistant's body speak over Web Serial. A BLE HID relay and an IronOS soldering iron speak over Web Bluetooth. The screen, a USB camera and the microphone come through the browser's media.
The person picks the port or the device in the browser's own dialog; the page never sees one it was not given. For a machine that must keep running when the tab closes, use this computer's host.
- built: 9 verified on loopback, 3 media drivers not yet verified
- 12
- planned
- 4
- over Web Serial, 3 over Bluetooth, 4 media
- 9
packages/domain/world/drivers.jsOutput case-studies/browser-tab/stats.jsonTool scripts/sites/case-studies.mjs browser-tabRan on This computer (dell-gb10-1), reading the checkoutWhen Open it in this tab.
Sign in, and your Drive, your agents and your worlds are there.