clawboo command does, and how to stop, update and remove it. To go straight to a working team, follow the Quickstart.
These docs track the latest code. The latest npm release is 0.9.0; anything newer is listed under Unreleased in the changelog.
Requirements
- Node.js 22.12 or newer. Check with
node --version. On an older Node,clawboostops right away with a message naming the version it found. Get Node from nodejs.org or a version manager such as nvm or fnm. - A terminal and a web browser. You type one command; everything after that happens in the browser.
- An AI provider, chosen during setup: an API key, a local Ollama, or a ChatGPT subscription. You don’t need one to install.
- Only if you add OpenClaw teammates: the OpenClaw release Clawboo installs needs Node 24.22.1 or later on the 24 line, or 26.12.1 or later. Node 22 and Node 25 cannot run it. OpenClaw runs on the Node.js Clawboo runs on, so start Clawboo with such a Node. Clawboo checks it before it installs OpenClaw, and installs nothing on a Node outside that range.
Run Clawboo
- Try it with npx
- Install it globally
@latest: a bare npx clawboo can reuse an older copy from npm’s cache. An npx run cannot update itself from the dashboard; see Update Clawboo.Add Claude Code teammates (optional)
The Claude Code runtime needs the Claude Agent SDK, which theclawboo package does not include because it would add about 210 MB to every install. Install it from the dashboard: in Settings → Runtimes, click Install on the Claude Code row. That works for every way of running Clawboo, a one-off npx run included, and puts the SDK in Clawboo’s own runtimes folder (see Where your data lives). Then connect Claude Code on the same row; see Claude Code.
What the clawboo command does
- Checks your Node.js version.
- Says whether an OpenClaw Gateway answers on its default port (18789). This is information only; you don’t need a Gateway.
- Finds the Clawboo server if it is already running, or starts it. If the running server is older than the command you ran, it offers to restart it on the new version.
- Opens your browser at the dashboard, signed in.
clawboo again to reopen the dashboard: it finds the running server instead of starting a second one.
The dashboard is locked to your computer. On its first start the server makes an access token and saves it in ~/.clawboo/access-token, which only your user account can read. Every browser needs a sign-in, and clawboo gives yours one: it opens the dashboard with a one-time link that works once, within two minutes. The terminal shows only the plain address. A browser that is not signed in shows “This dashboard is locked to your computer”; run clawboo open to open a signed-in one. To open Clawboo in another browser, use Open on another device at the bottom of the sidebar. It also shows a QR code for a phone once the phone can reach the server, which takes setup: see Reach Clawboo from another machine. Security explains what the token protects, and what it does not.
The CLI reference covers how the command finds the server, and every flag.
Stop and restart
clawboo stopstops the server. Running it when nothing is running is safe.clawboo restartstops the server, starts a fresh one on the same port and opens the browser. Add--no-opento skip the browser.clawboo openopens the running dashboard in your browser, signed in.clawboo open --printprints a one-time link instead, for a computer with no browser.clawboo backupsaves a one-file copy of the database in the folder you run it from, even while the server runs.
npx clawboo@latest stop and so on.
Update Clawboo
When a newer version is on npm, an Update available chip appears at the bottom left of the dashboard.- Global install: click the chip (Click to update). Clawboo installs the new version, waits up to 10 minutes for any agent runs still going to finish, restarts the server and reloads the page. Runs still going after 10 minutes are interrupted; Restart now on the chip skips the wait.
- npx run: click the chip (Copy command) to copy
npx clawboo@latest, then run it in a terminal. It notices the older server still running and offers to restart it. - A global install your user cannot write (such as a root-owned
/usr/local): the chip copies the command too. Run it withsudo, or update Clawboo the way it was installed.
CLAWBOO_DISABLE_SELF_UPDATE=1 (see Pin settings for everyone).
To update a global install from a terminal instead:
clawboo -y restarts it without asking. Your data stays where it is: a newer version adds what it needs to your existing database when it opens it.
Uninstall
- Optional: in Settings → Providers, click Disconnect on each key you added there. Keys saved in that panel are also written in plain text to OpenClaw’s
~/.openclaw/.envand to each OpenClaw agent’s key file, and Disconnect removes every copy. - Stop the server and remove the package with the two commands below.
- To delete your data as well, remove the data folder:
~/.clawboo, or the folderCLAWBOO_HOMEnames. Then remove the work folder, with your agents’ files: the folderCLAWBOO_WORK_DIRnames, else<CLAWBOO_HOME>-workwhenCLAWBOO_HOMEis set, else~/clawboo-work. Remove the work folder only when no other Clawboo install uses it; for a shared one, see Reset everything. - To remove the runtimes Clawboo installed for you (OpenClaw, Claude Code’s Agent SDK, Codex and Hermes), remove the runtimes folder with the server stopped: the folder
CLAWBOO_RUNTIMES_DIRnames, else<CLAWBOO_HOME>-runtimeswhenCLAWBOO_HOMEis set, else~/clawboo-runtimes. Stop an OpenClaw Gateway that Clawboo started first; see Move or remove it.
npx clawboo@latest stop, then remove the folders in steps 3 and 4 if you want, with the same care for a work folder another install shares. OpenClaw, Codex, Claude Code and Hermes are separate programs, and uninstalling Clawboo leaves them in place. The ones Clawboo installed for you stay in the runtimes folder until you remove it (step 4).
Where your data lives
Clawboo keeps its data in~/.clawboo (set CLAWBOO_HOME to use another folder): the database, settings, the access token, the encrypted key vault and the server log. Your agents’ work, each team’s folder (with a folder for each task inside it) and the task worktrees, goes in a separate work folder, ~/clawboo-work (set CLAWBOO_WORK_DIR to use another). The runtimes Clawboo installs for you (OpenClaw, Claude Code’s Agent SDK, Codex and Hermes) go in a third folder, ~/clawboo-runtimes (set CLAWBOO_RUNTIMES_DIR to use another), never in npm’s global folder. Setting up OpenClaw, and saving keys under Settings → Providers, also write to OpenClaw’s ~/.openclaw folder. Data and state lists every file and covers backup and reset.
Troubleshooting
Clawboo requires Node.js 22.12 or newer
Clawboo requires Node.js 22.12 or newer
Your Node is too old for Clawboo. Install Node 22.12 or newer from nodejs.org, or switch with a version manager (
nvm install 22 or fnm use 22), then run the command again.Dashboard is taking too long to start.
Dashboard is taking too long to start.
The first start can be slow, especially on Windows while antivirus software scans the new files. The command waits up to 45 seconds. When it gives up, it prints the last lines of
~/.clawboo/server.log and the log’s full path: read the log for the reason, fix it, then run clawboo again.Could not find the Clawboo server.
Could not find the Clawboo server.
The installed package is incomplete. Run
npx clawboo@latest, or reinstall with npm install -g clawboo.This dashboard is locked to your computer
This dashboard is locked to your computer
This browser is not signed in: it has no access cookie, or the server’s token changed. Run
clawboo open on the computer running Clawboo to open a signed-in browser. A sign-in link works once, within two minutes, so a link you opened before shows this screen too. On a computer with no browser, clawboo open --print prints a link to open yourself.A Clawboo server is running on port N, but it requires an access token.
A Clawboo server is running on port N, but it requires an access token.
The server was started with a
STUDIO_ACCESS_TOKEN that the shell you ran the command in does not have, so the command cannot talk to the server. Set STUDIO_ACCESS_TOKEN to the server’s token in this shell and run the command again; clawboo open, clawboo stop and clawboo restart then work too. To open the dashboard in your browser without the CLI, visit http://localhost:18790/?access_token=YOUR_TOKEN once (use the port the message names). Without the token, clawboo stop and clawboo restart print a command that stops the server by hand.Could not open a browser on this computer.
Could not open a browser on this computer.
The computer has no desktop, or no program to open a browser with (
xdg-open on Linux). The server is running. Run clawboo open --print for a one-time sign-in link and open it in a browser that can reach this computer, such as through an SSH tunnel; see Reach Clawboo from another machine.The dashboard opened on an unexpected port
The dashboard opened on an unexpected port
If your shell sets a
PORT variable, Clawboo uses that port instead of 18790. Unset it, or choose a port with CLAWBOO_API_PORT. The address Clawboo prints is always the right one.The update chip says the update failed
The update chip says the update failed
The chip shows npm’s own reason. A permission error means npm cannot write to its global folder, which is common with a system-wide Node. The chip then suggests running the update with
sudo in a terminal. To avoid sudo, install Node with a version manager such as nvm or fnm, which keeps global packages in your home folder, and install Clawboo again under it. If the update installed but the page did not come back, run clawboo restart.Next steps
- Quickstart: connect an AI provider and deploy your first team.
- Data and state: every file Clawboo keeps, backup and reset.
- CLI reference: every command and flag.
- Remote access: reach Clawboo from another machine.