Add a node

In this tutorial you turn a spare Linux machine, VM or GPU box into a node: a headless AI Workbench that runs agents for you or your team. At the end the node is approved, running as a service, and serving a repository. Allow twenty minutes.

The steps use Linux. macOS is the same; on Windows, use PowerShell and the commands in Install a node.

Before you startCopy Anchor Link

• A Linux (x64 or arm64) machine you can reach with a terminal, with outbound HTTPS.
• Git, and at least one agent tool installed and signed in on that machine as the user the node will run as, for example Claude Code: npm i -g @anthropic-ai/claude-code, then sign it in.
• The address of your install source, where the node's packages are published. Ask your administrator or Mojo Up for it.
• For Mojo Up AI Cloud: an account at cloud.ai.mojoup.com.au. For a self-hosted organisation: someone who may approve nodes, or that permission yourself.

1. InstallCopy Anchor Link

curl -fsSL <source>/install-node.sh | sh

The script downloads the package for your machine, checks it against its published digests, installs it to ~/.local/share/mojoup/node, links mojoup-node from ~/.local/bin, and then starts the setup wizard.

2. JoinCopy Anchor Link

The wizard asks How does this node find your organisation?

  Sign in to Mojo Up with the organisation this node is for active — your personal one or a team — and approve it:

    Code  ABCD-EFGH
    Open  https://…

When it is approved, the wizard says Approved: this node is … in ….

3. Finish the setupCopy Anchor Link

The wizard then asks:

1. Node name, Tags (comma-separated, such as tag:gpu,tag:linux; teams place work on nodes by tag) and What is this node for? Keep teams ticked: "run agent teams on its repositories".
2. Home folder: where the node clones repositories and runs agent tools from. Keep your home folder, or choose another.
3. Repositories: choose Clone a repository, paste a repository's URL, and pick the folder to clone into. Choose Done when you have added what you want.
4. Start this node when the machine starts? Answer yes. The wizard installs the node as a systemd service, and starts it.

4. Check itCopy Anchor Link

mojoup-node status
mojoup-node doctor

status shows the organisation the node joined, its repositories and the service. doctor checks every part and names the fix for anything that is not right: an agent tool that is not signed in, for example.

Now run mojoup-node with no arguments. The node's console opens: a live pane with each repository's host and its agents, and a status bar like gpu-box-1 · joined Contoso · 1 host · service: running. Type / to see its commands, and /exit to leave. The node keeps running.

5. Use itCopy Anchor Link

The node now appears among your organisation's nodes in the console. On a self-hosted organisation, an administrator assigns who may use it under Nodes → Who may use it. From AI Workbench, add a repository and choose AI Workbench node under Where, and the agents run on the node.

What you learntCopy Anchor Link

• mojoup-node installs with one command and sets itself up with a wizard.
• A node is live only once a person approves it, and serves exactly one organisation or team.
• status, doctor and the node's console tell you what it is doing.

Next stepsCopy Anchor Link

• Run a node as a service: start, stop and logs.
• Work with a running node: approvals, chat and repositories.
• Join keys, to add nodes without a code.
• The command line.