mait.sh1.69.2

Private beta: features and content may change. No warranty; use at your own risk.

Set up your workspace and run your agent.

A workspace is a container on your computer where you and your chosen coding agent work with a project’s files and tools.

This guide goes from nothing installed to a first small task by your agent, then to named workspaces side by side, in eight steps. Each step says what it does, what to check before the next one, and where the docs cover it.

Linux · BetamacOS · AlphaWindows · Alpha

MAIT is a private beta by invitation, for exploratory use, without warranty or support.

Join the waitlist See the steps

Before you begin

What you need on each platform.

Everything is beta: Linux is Beta, macOS and Windows are Alpha. Check your computer, your account and your agent’s sign-in before running any command.

Linux

Beta

A Linux computer for which the launcher and runtime downloads are provided.
Administrator rights for the installation only: the system part of the preparation needs an account that can elevate, or someone who can run that part for you. Daily use does not.
Network access for the downloads. Preparation installs the container runtime and the secure runtime where the host supports it.

macOS

Alpha

A Mac with Apple silicon.
At least 8 GB of memory: the launcher sizes its own virtual machine from the Mac’s memory.
A decision about clipboard sharing with that machine, made before the first real start.

Windows

Alpha

Windows with WSL2 enabled, and PowerShell for the installer.
At least 8 GB of memory: the launcher sizes its own WSL distribution from the computer’s memory.
An interactive desktop session for the preparation step, locally or over remote desktop.

An activated account

All platforms

A MAIT beta invitation, activated on this computer by signing in. Starting a workspace needs it; preparation and diagnosis run without it.
A small project you are allowed to use, in a folder you can write to.

Your agent’s own sign-in

All platforms

An account with your agent’s provider. You sign in to the agent’s model account separately from MAIT.
The agent’s permission choices, reviewed when it first starts.

Set up

Eight steps, from installer to a first task.

Your platform is selected for you; change it with the toggle. The steps play on their own: point at them to pause, or pick one in the terminal or with the dots.

Commands are the same on every platform after the installer. The terminal output is illustrative.

Install the launcher1/8

Install and verify →

Step 2 of 8

Prepare your computer

Your computer needs a container runtime before it can run a workspace. Preview the preparation plan first: it lists what will change and at which scope, and checks every precondition before changing anything. Then run it, and read the doctor report.

Run it as your normal user, never with sudo in front: it asks for elevation only for the steps that need it.

What you get The run ends with one summary of changed, unchanged, skipped, warning and failed steps and a zero exit status. Doctor can then reach the container runtime.

Step 7 of 8

Add and run your agent

Inside the workspace, the tool installer adds your chosen coding agent, separately from one installed on your computer. List the supported integrations first: a tool’s name there can differ from its command. Then start the agent, complete its own provider sign-in and review its permission choices.

What you get The agent starts in the workspace shell. For a first task, ask it to summarize one project document without changing any file, and compare its summary with the document yourself.

Step 8 of 8

Run named workspaces side by side

Type exit to leave the agent and the shell; the workspace keeps running until you stop it. Back in the project folder, a name starts another container of the same project, so several can run side by side and you stop or start each one by its name. Containers on the same branch share the project’s files; a branch gives one its own checkout.

What you get The list shows each name with its status, and stopping one leaves the others running.

Step 1 of 8

Install the launcher

One command downloads and installs the workspace launcher, aidcx, and adds it to your shell path. Open a new terminal if the command is not found yet.

What you get The version command runs, so the launcher is installed; the next steps prepare the runtime and your account.

Step 1 of 8

Install the launcher

One command downloads and installs the workspace launcher, aidcx, and adds it to your shell path. Open a new terminal if the command is not found yet.

What you get The version command runs, so the launcher is installed; the next steps prepare the runtime and your account.

Step 2 of 8

Prepare your computer

Run it as your normal user, never with sudo in front: it asks for elevation only for the steps that need it.

What you get The run ends with one summary of changed, unchanged, skipped, warning and failed steps and a zero exit status. Doctor can then reach the container runtime.

Step 7 of 8

Add and run your agent

What you get The agent starts in the workspace shell. For a first task, ask it to summarize one project document without changing any file, and compare its summary with the document yourself.

Step 8 of 8

Run named workspaces side by side

What you get The list shows each name with its status, and stopping one leaves the others running.

Troubleshooting

Fix a setup step and carry on.

Run the doctor report first and read the section that failed before changing anything. Fix the step that failed rather than repeating every step. These are the most common setup problems.

The launcher command is not found after installing?

Your current terminal has not picked up the path change the installer made. Open a new terminal and check that the command runs. If the command is still missing, read what the installer reported about where it installed.

aidcx versionRead the docs →

The doctor report shows Docker unavailable?

No container runtime is reachable: it is not installed, its service is stopped, or on a Mac the managed virtual machine is not running. Preview the preparation plan, run it, then read the doctor report again.

aidcx --install --dry-runRead the docs →

The preparation says the install plan is blocked?

A precondition is not met on this computer, so nothing was changed. Common ones: an account without administrator rights, or a Mac or Windows host under the managed runtime’s memory requirement. Read the listing printed above the summary, resolve the condition it names, and run the preparation again.

Read the docs →

Starting a workspace says no credentials were found?

Starting a workspace needs an activated MAIT account on this computer. Sign in with the instructions the launcher prints, then start again. Never share the one-time code.

aidcx loginRead the docs →

Your agent’s command is not found in the workspace?

The agent needs to be installed inside the workspace, or the shell needs to load the new path. Install it inside the workspace, load the tool environment, then check that the shell finds it. If the agent already runs in the workspace shell, skip the install.

aidc install claude@latestRead the docs →

All troubleshooting topics