Troubleshooting AI Workbench

Git is the one thing the wizard will not let you skip: every agent works in its own git worktree. Use the Git row's button to install it, then fill in your Git identity. Other rows (Git Credential Manager, WSL, Docker) can be left if you do not need them.

That is expected when a repository lives in a WSL distro, dev container or over SSH: each machine has its own git and its own identity, and the wizard checks git there.

Choose Retry in the terminal. A clone inside the wizard cannot ask for a password; the same clone in the terminal can, through your credential helper. Or sign in under Settings → Integrations → Accounts and pick the repository from your list.

The Tools step and Settings → Models → Runtimes list every agent tool with Install and Sign in. You need at least one. Most agent tools need Node.js 20 or later and npm; Settings → Setup checks them.

Projects marks it and offers Locate…, Clone again or Remove. If its WSL distro or container is gone too, use Find it again. See Projects.

Your email's domain does not publish a discovery record. Choose Enter the platform URL instead and type the address your administrator gave you. For Mojo Up AI Cloud, use Sign in with Mojo Up instead.

The workbench could not reach https://ai.mojoup.com.au. Check your network and any proxy, then try again.

Cloud approves a workbench into whichever organisation is active in its console at that moment. The sign-in lands in that organisation's own space. Switch to the right organisation at the top of the console's sidebar and sign in again from the right space. See Sign in and spaces.

Make sure you approved the code in the browser page that opened (or in the mobile app, with Enrol a workbench). The code expires ten minutes after it is shown; choose Cancel and sign in again for a new one.

The workbench's sign-in was revoked, for example from the console or the phone app. Sign in again from Settings → Organisation.

Settings shows the page that fits what the workbench is signed in to. Signed in to an organisation, including a Mojo Up AI Cloud team, it shows Organisation; on a team hub, it shows Team. To run a team hub as well, add it as its own space: Add a team hub of your own in the space switcher.

A repository folder belongs to one space. Choose Move it to this space to open it here from now on, or Cancel and open it from its own space.

The hub listens on your tailnet. Connect Tailscale (or your VPN) on the hub's computer and keep it on. The hub retries until the tailnet has an address.

An invitation works once, for 15 minutes. Ask the hub's owner for a new one. After too many wrong codes, wait a minute before trying again.

Do not join. Check the address with the hub's owner and ask for a new invitation.

Phones can join only through the hub machine's Tailscale name: turn on HTTPS certificates for your tailnet and bind the hub to the tailnet. Joining a hub from the mobile app is coming.

A policy caps the mode. The workbench says which policy and what it allows, for example "This repository's policy allows at most Auto here". See Policies.

The repository's policy says agents.sandbox: required. A desktop never sandboxes agents, so agents in that repository can only run on a sandboxed node. See Sandboxing.

The member is set to run on a named subscription account this machine does not have. Add an account with the same name under Settings → Models → Runtimes, or pick another account for the member. See Your subscriptions.

Uncommitted changes of your own hold a merge back. Commit or stash them, then merge again.

On macOS the app shows the download link when an update is out; download and install the new version.

MOJOUP_DISABLE_AUTO_UPDATE=1 in the app's environment turns updates off. The update channel (stable or nightly) is under Settings → General → Updates.