mait.sh1.69.2

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

Docs / Launcher and command-line tools

AIDC Launch workspace settings

Choose what the workspace can use from your computer, how sign-in sharing works, and where your own defaults live.

Settings you save with the project apply to everyone who opens it; flags on start apply once.

A setting is a request. `aidcx inspect` shows what the workspace actually got.

Advanced
Command reference

Where settings come from

  1. The project definition. aidcx scaffold saves your choices in the project's devcontainer configuration, so everyone who opens the project gets them.
  2. A flag on one start. The same options passed to aidcx start apply to that start only.
  3. Your own defaults. Personal settings go in ~/.mait/aidcx.yaml, or in environment variables that start with AIDCX_.

A flag wins over an environment variable, which wins over your defaults file.

What the workspace can use

Pass these to aidcx scaffold to save them, or to aidcx start for one start.

OptionDefaultWhat it asks for
--runtimesecuresecure isolates the workspace more strongly; host uses the plain runtime
--dockerdoffon runs Docker inside the workspace, host uses your computer's Docker, off neither
--x11onGraphical applications shown on your desktop
--gpuautoGPU access; auto uses one when available, off disables it, software draws without a GPU
--audiohosthost uses your speakers and microphone, on gives the workspace its own sound, bridge lets you connect your devices later, off disables sound
--usboffon passes every USB device, dynamic lets you attach devices one at a time
--kvmoffHardware virtualization, for running virtual machines inside the workspace
--aidevonYour AI coding tools' settings and saved sign-in, shared with the workspace
--ssoonSign-in sharing; see below
--distroautoThe Ubuntu version of the workspace image
Option
--runtime
Default
secure
What it asks for
secure isolates the workspace more strongly; host uses the plain runtime
Option
--dockerd
Default
off
What it asks for
on runs Docker inside the workspace, host uses your computer's Docker, off neither
Option
--x11
Default
on
What it asks for
Graphical applications shown on your desktop
Option
--gpu
Default
auto
What it asks for
GPU access; auto uses one when available, off disables it, software draws without a GPU
Option
--audio
Default
host
What it asks for
host uses your speakers and microphone, on gives the workspace its own sound, bridge lets you connect your devices later, off disables sound
Option
--usb
Default
off
What it asks for
on passes every USB device, dynamic lets you attach devices one at a time
Option
--kvm
Default
off
What it asks for
Hardware virtualization, for running virtual machines inside the workspace
Option
--aidev
Default
on
What it asks for
Your AI coding tools' settings and saved sign-in, shared with the workspace
Option
--sso
Default
on
What it asks for
Sign-in sharing; see below
Option
--distro
Default
auto
What it asks for
The Ubuntu version of the workspace image

Running Docker inside the workspace also turns on the secure runtime. aidcx inspect shows what each request resolved to.

Sign-in sharing

Sign-in sharing lets the workspace use the accounts you are already signed in to on your computer. It is on by default and uses each account with its existing permissions.

ValueShares
onEvery supported provider
devGit, Docker and Kubernetes
aiYour AI coding agents
git,dockerOnly the providers you list
offNothing
Value
on
Shares
Every supported provider
Value
dev
Shares
Git, Docker and Kubernetes
Value
ai
Shares
Your AI coding agents
Value
git,docker
Shares
Only the providers you list
Value
off
Shares
Nothing

Sign in to each service on your computer first. After starting, check one real read, such as git ls-remote origin in the workspace. To clear what an earlier start shared, turn sharing off and recreate the workspace.

Your AI tools in the workspace

With --aidev on, the workspace finds the settings folders of supported AI coding tools on your computer, such as Claude Code, Cursor, Gemini and Antigravity, Codex and GitHub Copilot CLI, and makes them available inside. An agent you already signed in to on your computer can then work in the workspace without a second sign-in.

Tools installed on your computer are shared; turn --aidev off when a project needs a separate agent identity.

Attach devices and sound while running

With --usb dynamic or --audio bridge, attach devices to a running workspace:

sh
$ aidcx feature usb attach --device 1d6b:0002
$ aidcx feature audio devices
$ aidcx feature audio attach --both --sink 1

aidcx feature <name> status shows what a listed feature requested and its current state.

Platform notes

  • macOS. AIDC Launch runs workspaces in a virtual machine it manages for you. Graphical applications appear through its own display. Preparation needs a Mac with at least 8 GB of memory.
  • Windows. Workspaces run in a WSL2 distribution that AIDC Launch manages. Preparing it needs an interactive desktop session.
  • Linux. Workspaces run directly on your computer's container engine.

What you getA project definition that asks for exactly the access your work needs, and nothing more.