Everyday AIDC Launch tasks

Choose the host behind the example

Your browser suggests a host; choose another at any time. The shared lifecycle stays visible while platform-specific support, shell setup, and commands change.

start resumes a stopped workspace or creates it if needed. Use aidcx exec <command> to run one command without opening a shell, and aidcx code to open the workspace in VS Code. Stopping keeps the workspace and its files; delete removes it.

AIDC Launch creates a separate checkout of that branch and a workspace for it, next to your main one. aidcx list shows every workspace with its branch. Check the branch and its status before you change files:

To copy ignored files, such as a local settings file, into the new checkout, add --carry-over <path>. The copy happens once, when the branch workspace is first created.

When two workspaces want the same port, choose how to separate them:

offset picks a port derived from the branch; ephemeral lets Docker pick a free one and prints it. aidcx list shows the ports each workspace uses.

A named copy has its own container but shares the same files as the branch it runs on. Use it to try different settings on the same code.

Settings are requests that AIDC Launch resolves for your computer. After a start, check the result:

inspect shows each setting and where its value came from. health shows CPU, memory and disk use with suggestions. To preview the settings a start would use without starting anything, run aidcx start --effective.

prune lists stopped workspaces and leftover branch checkouts, with container-only rows and clean, pushed checkouts already ticked. A checkout with uncommitted or unpushed work is left unticked so you do not lose it. Your Git branches themselves are never deleted. To remove one workspace, use aidcx delete; add --keep-volumes to keep its stored data.

If you installed extra tools by hand and want to keep them:

AIDC Launch shows what changed and lets you leave out caches and home-directory files before saving a local image. The image stays local until you share it; review it before you do.

After that, any command can reach the project with --workspace shop, from any directory.