Add a node

In this tutorial you turn a spare machine, VM or GPU box, on Windows, macOS or Linux, 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.

Before you startCopy Anchor Link

• A machine you can reach with a terminal, with outbound HTTPS: Windows (x64), macOS (Apple silicon) or Linux (x64 or arm64).
• 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.
• 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

The node is a single signed executable, mojoup-node, installed by one command. It downloads the newest release from Mojo Up AI Cloud, checks the package's digest against the release manifest (and on Windows the Mojo Up code signature), lays it out so it can update itself, and hands over to its setup wizard.

irm https://ai.mojoup.com.au/releases/v1/install/install-node.ps1 | iex

& ([scriptblock]::Create((irm https://ai.mojoup.com.au/releases/v1/install/install-node.ps1))) -Root D:\Tools\MojoUpNode -NoSetup

Options, for any of them: MOJOUP_NODE_CHANNEL=nightly (Windows -Channel nightly) takes nightly builds; MOJOUP_NODE_SOURCE=<url or folder> (-Source) installs from a self-hosted organisation's own feed, https://<your aioe>/releases/v1, or a folder you were given; MOJOUP_NODE_ROOT and MOJOUP_NODE_BIN (-Root) change where it goes; MOJOUP_NODE_NO_SETUP=1 (-NoSetup) skips the 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 service (a Scheduled Task on Windows, a launchd agent on macOS, a systemd service on Linux), 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. Keep it currentCopy Anchor Link

The node checks the release feed every six hours and says in mojoup-node status when a newer release is out. The node.autoUpdate setting decides what happens next: notify (the default) only tells you; install applies the update after a trial run and rolls back if the new version does not start; off never looks. mojoup-node update does it now. On a self-hosted organisation, the organisation decides which release each ring of nodes is offered, from the console's Updates page.

6. 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 on Windows, macOS or Linux, 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.