Getting started — Docs · CommandAGI Developers

What CommandAGI is

CommandAGI is a workbench where people and agents plan, simulate and run real machines. Everything in it rests on four ideas:

Devices. A device definition describes one kind of machine as a set of channels — a G-code line, a servo bus, a video stream, a shell. A CNC mill, a laser, a printer, an arm, a drone, a phone, a camera and a computer are all devices.
Worlds. A world places devices as units, with positions, in a space. A world is either physical (it reaches hardware) or simulation (every channel runs in a simulator).
Runs. What devices do is recorded as streams in a run: one folder per run, one stream per unit's channel, all on one clock.
Grants. An agent or a person acts on physical hardware only inside a standing grant an account gave it.

All of it is plain files in a folder you choose.

Open the workbench

Go to commandagi.com. The workbench opens straight away — you do not need an account.

As a guest, your project lives in this browser's own storage. You can import a folder into it and export it as a zip at any time.
Signed in, your projects can live in the cloud and follow you between devices. Sign up or sign in from the foot of the left dock.
On the desktop app, the same workbench runs with this computer's host built in, so it can open any folder on disk and reach machines on USB and the local network. See Download.

Open a project

The folder you open is the project. Use the project menu at the top of the left dock:

open folder… — a folder on your computer (in browsers with the File System Access API, or in the desktop app);
project in this browser — the guest project;
import a folder into this browser… and export this browser project (.zip).

A new tab (+, or Mod+T) offers suggested files, recent files and the drives you can open from: the cloud, a local folder, local files, this browser and any host you have paired.

The workbench ships read-only example projects to explore: LED indicator boards (eda), a mechanical project, a biology workcell, a library of simulations, and a template library of dashboards.

Find your way around

The window has a centre of tabs split into panes, and three regions around it: left (navigation and the explorer), right (details of what is selected) and bottom (runs, events, terminal and logs). The pane you used last has focus and decides what the regions show.

Mod+Shift+P opens the command palette. Every action is there.
Mod+P opens a file by name.
Mod+Enter maximizes the focused pane.

Make a world

From the palette, run new world (simulation)…. A simulation world binds each channel to a simulator, so nothing in it can reach hardware.

Units are listed in the world's world.json. Select a unit in the 3D view or the list and edit its position, rotation and device in the Details tab on the right. To add units, add them to world.json — see File formats.

Run a simulation

Open the world and choose simulate on a unit's channel in the devices view.
Connecting starts a session run in that world (or joins the one already open). Every command and state is written to the run as it happens.
Worlds that name a simulation file also offer force drag: grab a body and push it. The force is recorded with your name.
Use close run when you are done.

A simulation world says so on screen: channels run in the simulator only; nothing here reaches hardware, and simulated results never count as physical evidence. In a read-only example, runs are not recorded — open a folder of your own to keep them.

Replay and fork

Every run can be replayed on the time bar at the foot of the window, at 0.25× to 8× speed, or followed live.

Mod+Alt+P play or pause · Mod+Alt+L go live · Mod+Alt+, and Mod+Alt+. step five seconds.
The runs tab in the bottom region lists a world's runs.
fork starts a new simulation run from the playhead — the same moment, a different future.

When you are ready for real hardware, read Connecting a machine. To let an agent drive it, read Agents and standing grants.

Getting started.