skip to content
superbot.gg
superbot.gg / docs / agent-computer

Install Superbot on an agent computer

This page is for an agent that has its own Linux computer: xAI Grok Bot, Meta Muse, OpenAI dots, Manus, or any Linux VM an agent drives. It installs the Superbot Helper on that computer and links it to the user's Superbot account. The user's request usually reads "Install Superbot from superbot.gg/agent".

Vendor notes: Grok Bot, Muse, dots, Manus.

Not for session sandboxes

Codex cloud tasks and Claude Code on the web run in a container that is thrown away when the session ends, so a Helper installed there would be linked to a computer that no longer exists. Do not run the command there. Connect the remote MCP server instead:

Prerequisites

The command

Run this as one shell command. Set V to grok-bot, muse, dots or manus, or leave it empty.

sh
O=https://beta.superbot.gg; V=grok-bot; cd "$(mktemp -d)" && curl -fsSo S "$O/download/helper/asset/sha256sums?via=origin" && curl -fsSo agent-bootstrap.sh "$O/download/helper/agent-bootstrap.sh" && grep '[ *]agent-bootstrap.sh$' S | sha256sum -c >&2 && sh agent-bootstrap.sh --origin="$O" --vendor="$V" --helper-sha256-x64="$(awk '$2=="superbot-helper-linux-x64"{print $1}' S)" --helper-sha256-arm64="$(awk '$2=="superbot-helper-linux-arm64"{print $1}' S)"

It fetches the release checksums and the Helper's install script from https://beta.superbot.gg, checks the script against its checksum line, and runs it. The script downloads the Helper build for this computer's uname -m, checks it against the pinned sha256, installs it at ~/.superbot/bin/superbot-helper, starts it in the background and asks for a link. It finishes in about 30 seconds and never reads from a terminal.

Where https://beta.superbot.gg/bootstrap.sh answers (a self-hosted origin, or once the beta opens), curl -fsSL https://beta.superbot.gg/bootstrap.sh | sh -s -- --agent=grok-bot runs the same steps and also refuses to run in a session sandbox.

A computer linked this way gets link-level access. The checks prove the bytes match what https://beta.superbot.gg serves over TLS, nothing more, so this path is never granted access to the user's data. That access comes only from the command the Superbot app hands out.

If the user pastes a command from the Superbot app

It starts with curl -fsSLo sba.sh and carries --link=lnk_…. Run it exactly as given, as one command, instead of the command above. The app pinned every download to a hash it verified, and the one-time link carries the access the user approved in the app. Never print, log, store or repeat the --link value.

What to show the user

Standard output is one block of KEY=value lines. Progress goes to standard error.

code
SUPERBOT_BOOTSTRAP=v1
SUPERBOT_STATUS=awaiting_approval
SUPERBOT_LINK_URL=https://…/approve?user_code=…

One line is enough, for example Superbot Helper: linked to a***@example.com, or Superbot Helper: approve this computer at <SUPERBOT_LINK_URL>.

Verify

Run the same command again. With the Helper already current it downloads nothing, and once the user has approved it prints SUPERBOT_STATUS=linked. To check the Helper process itself:

sh
kill -0 "$(cat ~/.superbot/agent-helper.pid)" && echo running

Re-running

Running the command again is safe. When the computer is already linked (~/.superbot/key.json exists) it only restarts the Helper and never links again. To link to another account, add --relink after sh agent-bootstrap.sh. Running it again is also how the Helper updates to a new release, and what to do after the computer restarts or is updated.

Troubleshooting