mait.sh1.132.1

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

AIDC Launch (aidcx)

Runs each project in its own secure container on your own computer, with explicit choices for shared files, devices and accounts.

Start here: what it does, why use it, and how it fits.

Beta
OverviewInstallWorkflowsOperateCustomizeInsideAll components
What it does

A safe, separate workspace for each project, one command away.

When an AI coding agent works on your computer, it shares your files, your tools and your signed-in accounts. AIDC Launch gives each project its own secure project workspace. You start it with one command and step inside, and the agent works there. The project can access files, devices and accounts you choose to share; review those grants before starting.

Picture a developer who wants an agent to upgrade a library across a large project. Without a boundary, a bad step could change files anywhere. With AIDC Launch, the project opens in its own container, the agent makes the change, and the developer reviews the result. Stopping the container preserves its state; it does not undo changes made through shared resources. The container uses your Git, Docker and cluster sign-ins without copying their stored account secrets into it.

AIDC Launch runs on Linux, on Macs with Apple Silicon and on Windows. Installation prepares the managed runtime when its platform prerequisites and account access are available. Projects run in Linux environments, while device support and host integration vary by platform. AIDC Launch does not choose an agent for you and does not sign you in to the agent's own account.

aidcxmait<version>the launcher
Platforms
  • Linuxnative
  • macOSsupported
  • Windowssupported
Linux on common desktop and server distributions, macOS on Apple Silicon only, and Windows with its built-in Linux support. Projects run in Linux environments; host prerequisites, devices and integration features vary by platform
YouLauncherSealedprojectcontainerYour agent1start aproject2opens3works insideYouLauncherSealed project containerYour agent1start aproject2opens3works inside
  1. Step 1: You start a project Launcher.
  2. Step 2: Launcher opens Sealed project container.
  3. Step 3: Sealed project container works inside Your agent.
Why use it

What you gain over running an agent on your own machine.

An agent that works directly on your computer can reach everything you can. Setting up a container by hand takes care for every project. AIDC Launch keeps the setup with the project and handles the machine-specific details for you.

Security

Check the runtime before project work

Verify the runtime and review shared files, devices and accounts before starting

Typical alternative
Choosing a runtime separately for each project
Here
The supported Docker project flow checks the required secure runtime
Usability

Guided machine preparation

Follow the reported remedy, then verify readiness before opening a project

Typical alternative
Preparing each runtime prerequisite by hand
Here
Installation reports the steps performed and any remaining prerequisites
Usability

Your sign-ins stay with you

Use approved account permissions without manually placing credential files in the project

Typical alternative
Pasting tokens or copying credential files into the container
Here
The container uses your existing Git, Docker and cluster sign-ins live, and you choose which ones to share
Reliability

One workspace per task

Distinct branches separate project edits; containers on the same branch still share files

Typical alternative
Two tasks editing one checkout
Here
A task on its own branch gets its own copy of the project and its own container
Experience

Windows open on your Mac

Graphical tools work with no display setup

Typical alternative
Setting up a display by hand
Here
On a Mac with Apple Silicon, a graphical program started in the container appears as a normal window
Operability

A clear picture of every container

You repair the stage that broke and nothing else

Typical alternative
Guessing which container belongs to what
Here
AIDC Launch lists your containers with their branch, state and resources, and when a start fails it says which stage failed
Out of the box

One installer per platform, then sign in.

Follow the current installation route for your platform. Windows installation uses the configured Store route. After that you sign in with your MAIT access, let AIDC Launch prepare the secure runtime, and keep everything current with its update command.

Installing, signing in and starting a project need access to the MAIT services. Checking the version and reading the legal notices work offline, and the health report still shows what it can find on your computer when the services are out of reach. The project must use a MAIT image or the MAIT devcontainer feature, and AIDC Launch can write a ready configuration for a project that has none. Opening the project in VS Code additionally needs VS Code and its Dev Containers extension.

Where it fits

Where it sits in the MAIT toolkit.

Installed byThe public installer for your platform, described in Install
RunsThe MAIT image from mait-image, or a project that uses its devcontainer feature
Prepares inside the containerThe account and startup it needs, so it can use your sign-ins without copying their stored account secrets, described in Trust and sign-ins
HostsThe agent you choose, which you start from a shell inside the container
Learn more

Where to read on.