mait.sh1.142.0

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

Project

Changelog

Every release of every product in one feed, newest first. Search it, or filter by product.

Releases

Find a release.

AIDC Launch (aidcx)

Stable6.46.0Edge6.47.1

Documentation

206 releases

November 2026

  1. 6.47.1Edge
    • Uninstall now removes the per-user runtime folder, and start refuses to run before aidcx is installed.
    • MCP files are wired on reused containers, and the launcher says when they are unchanged.
    • Update notes, display settings, container counts and the custom install folder on Windows are reported correctly.
  2. 6.47.0Coming
    • On a Mac, aidcx doctor in the Linux terminal now shows the runtime's CPUs, memory and disk, read from the Linux environment itself, instead of reporting that the figures are unavailable.
    • When no allocation can be read, the skipped row now says why, telling a missing file from a permission problem, and suggests aidcx vmm status on the Mac.
    • aidcx health in the Linux terminal shows the same runtime allocation on a Mac.
    • The MCP registry entry in the agent CLI workspace files is now written as mcp-stub serve; entries with the removed options are repaired and custom serve modes are kept.
  3. 6.46.0Stable
    • Improved sign-in renewal behaviour on the Mac.
    • Improved reliability of shutdown and WSL start on Windows.
    • The MCP section now has a per-tool trust note with a doctor check.
    • Updates no longer downgrade the display binaries, and uninstall cleans up leftover files.
    • The background bridge relay no longer holds onto the calling terminal.
  4. 6.45.2
    • Headed browsers started by the MCP registry service inside the container now get the session's display and GPU settings, so they no longer fail with "Missing X server or $DISPLAY".
    • Fixed background sign-in renewal failing when it refreshes a credential; failed renewals are now logged.
    • On a Mac, aidcx uninstall also removes the identical copy of aidcx that the installer leaves in ~/.local/bin next to a custom install directory. A copy that is a different build is left in place, and the uninstall report says so.
    • aidcx update says that nothing changed, and asks for no restart, when the downloaded launcher is the one already running.
    • On a Mac, aidcx doctor run in the managed Linux environment reads the VM allocation from the real instance, drops the unrelated sysbox note and shows no relay details under the skipped X11 relay row; aidcx uninstall no longer prints Lima's harmless stop line.
  5. 6.45.1
    • aidcx stop no longer reports a failure when one of the container runtime's background services is not installed or is already stopped; it only reports a service that is still running after the stop.
    • On Windows, the .wslconfig lines that aidcx install adds are now recorded in the same manifest file as the other install records, and aidcx uninstall still removes exactly those lines. Lines that aidcx adds follow the line ending the file already uses most.
    • aidcx uninstall now removes the aidcx binary that the installer placed in a custom AIDCX_INSTALL_DIR, and the directory itself when it is left empty. An install into a temporary location is left in place.
    • On a Mac or Windows computer, the hints for commands that only run inside the Linux environment now say "in the Linux terminal" and name the command to run there. On a Mac, a failed command no longer prints the harmless "use of closed network connection" error line from Lima.
    • aidcx doctor gives separate advice for /dev/kvm: a missing device points to firmware and nested-virtualisation settings, a device you may not open points to the kvm group, and a device that exists but cannot be opened points to the virtualisation setting.
  6. 6.45.0
    • On Windows, install again sets a memory limit for the WSL 2 virtual machine ([wsl2] memory, sized from your computer's RAM) and [experimental] autoMemoryReclaim=gradual in .wslconfig, but only when those keys are absent; what it adds is recorded and removed by aidcx uninstall.
    • If you installed aidcx 6.40 or 6.41 on Windows, those versions already wrote the same two keys without recording them. 6.45 leaves them exactly as they are: it does not rewrite or remove them, and aidcx uninstall does not remove them because it never recorded them. They are harmless; the limit applies to the whole WSL 2 virtual machine and only after it next restarts. To change it, run aidcx vmm set --memory <GB> and then aidcx vmm restart --vm, or edit %UserProfile%\.wslconfig yourself; delete the two lines by hand if you want them gone after uninstall.
    • A Ctrl-C typed inside the aidcx distill picker is a cancel: nothing is built and the exit code is 0. A real SIGINT sent to the process exits with 130, after the temporary containers and images are removed.
  7. 6.44.3
    • Start and doctor wording is consistent, and doctor suggests starting a stopped engine.
    • Uninstall now counts only what was actually removed, matching the dry run.
    • On Windows, install applies and confirms the automount setting and restarts WSL reliably.
    • Microphone refusal text now says the decision is not yet made.
  8. 6.44.2
    • Microphone permission is checked before the Mac runtime restarts.
    • Clearer messages from the Docker, doctor and uninstall commands; uninstall counts left-over versions correctly after an incomplete run.
    • The minimum host memory for the managed runtime is lowered to 6 GB.
  9. 6.44.1
    • aidcx start on Windows waits for the Docker engine inside WSL2 to be ready.
    • The distill message for a refusal on a Mac or Windows host points at aidcx, where distill runs.
  10. 6.44.0
    • aidcx distill shows progress per stage, a heartbeat line on plain output, and escapes hidden characters in listed paths.
    • The managed Linux environment follows the host's release channel on update, and a pinned fetch must match exactly.
    • Calmer wording for start, doctor and microphone status.
  11. 6.43.0
    • aidcx distill builds an image from exactly the paths and packages you select, and cleans up after an interruption.
    • A cancelled carry-over selection in aidcx start stops the start cleanly, and start fails with a clear message when there is no devcontainer.
    • On a Mac, the microphone grant is enforced and its status shown by aidcx vmm mic-status; the bridge restarts after an update and a pending restart is shown by doctor.
    • Windows install requires WSL 2.5.4, keeps the distro up while idle and re-runs cleanly.
    • aidcx uninstall removes more of what install placed, including empty cache folders and Mac microphone markers.
  12. 6.42.1
    • Install probes Docker as the provisioned user, and terminal verdicts start with ERROR.
    • Uninstall removes owned caches and names the files it keeps.
  13. 6.42.0
    • First aidcx distill allowlist flow: select what to carry into one new image layer, with a tree picker, a dry run and verification before the tag is written.
    • The folders that belong to your account are re-owned correctly when the container's account differs from the image's; a mesh switch from off to on asks before recreating the container.
    • aidcx uninstall previews and removes Windows host leftovers, and aidcx delete asks for --force when no terminal can answer.
    • Mac microphone attach names the device, fails when access is denied and survives a restart; the Mac runtime starts through the aidcx app.
    • Start is more reliable after an unclean stop and after creating a container.

October 2026

  1. 6.41.0
    • aidcx start on Windows refuses a project on a Windows drive and tells you to use a folder inside the Mait environment; drive automount is disabled there.
    • aidcx update prints a short summary when piped and an honest outcome; a stopped Mac VM is started on demand.
    • Windows logins stay converged between the Linux environment and the host, and are never overwritten by a renewal in progress.
    • aidcx scaffold no longer accepts --drivers; host drivers are always written as declarative options.
    • Editing devcontainer.json is safer, and worktree removal is more reliable.
  2. 6.40.1
    • Maintenance release.
  3. 6.39.1
    • Windows: the Windows profile folder is adopted as home at startup, and .aidc state is kept inside the Linux environment.
    • Deleting a container reclaims its anonymous temporary volume more safely.
    • Install warning rows show their suggestion and strip control characters.
  4. 6.39.0
    • The launcher talks to Docker directly instead of through the docker command, forwards your registry logins to pulls and builds, and explains BuildKit-only builds and skipped pulls.
    • On Linux, a Docker group that is not active in the current session is explained with the steps to fix it; the install ends by verifying Docker access.
    • aidcx cp pulls container files over exec; the old Docker exec shim is retired.
    • aidcx doctor flags a libvirt network that shadows the DNS server.
    • The scaffold picker remembers your telemetry and AI-tool choices.
  5. 6.40.0
    • Maintenance release.
  6. 6.38.1
    • The activity row is cleared on interrupt and update and no longer overlaps child-process output.
  7. 6.38.0
    • Install checks WSL (and macOS 26 or newer) before changing anything instead of updating it, and never exits silently on a crash.
    • aidcx start refuses --branch without a commit and reports an ambiguous target once.
    • Clearer warnings about the real kubeconfig location; the activity row is cleared before a sudo prompt.
  8. 6.37.3
    • The host and guest logins stay in sync on a Mac, using only the file the login actually uses.
  9. 6.37.2
    • Maintenance release.
  10. 6.37.1
    • Fixes GPU hook ordering and reads the Apple GPU name at runtime.
  11. 6.37.0
    • Improved Mac app packaging.
  12. 6.36.3
    • The Mac app is named aidcx.app; inspect and health no longer show false display and GPU warnings on a Mac.
    • Container audio can use the shared sound cookie in host mode.
  13. 6.36.2
    • audio on starts the in-container sound server reliably; container clients get the real cookie.
    • Mac guest DNS is read from the real network layout; a login containing a dot is accepted by the helper.
  14. 6.36.0
    • Containers can read their own telemetry through a dedicated MCP server, and the collector also accepts OTLP/gRPC on port 4317.
    • MCP components are now named after what they are.
    • The Mac guest sound server starts with systemd.
  15. 6.35.6
    • A fresh Mac install can create its runtime and call the CLI.
  16. 6.36.1
    • Maintenance release.
  17. 6.35.5
    • Install skips downloads the Mac guest already has.
  18. 6.35.4
    • More reliable telemetry collector administration and Mac runtime commands; legal exits 2 when it cannot write.
  19. 6.35.3
    • More reliable start of the Mac runtime tools during install.
  20. 6.35.2
    • More reliable Mac and WSL install steps and display access inside containers.
    • Runtime failure text is capped without cutting an identifier.
  21. 6.35.1
    • Keeps the telemetry collector within its memory budget; a frozen collector is replaced within about 90 seconds.
  22. 6.35.0
    • aidcx health shows the container's own view of the telemetry endpoint and aidcx inspect shows mesh and telemetry state.
    • The status says when the bridge supervisor is not installed instead of reporting a collector that is not running.
  23. 6.34.0
    • New telemetry feature: a local OTLP endpoint in each container (--otel on|off) and a host collector managed with aidcx feature otel status|remote|purge|wipe.
    • aidcx bridge enable|disable otelc switch the collector.
  24. 6.33.9
    • After a Microsoft Store update, aidcx update aligns the managed Linux environment to the newly installed package.
    • On a Mac, aidcx doctor run in the managed Linux environment describes the display as Xwayland :1 with the Wayland socket wayland-1, and login shells there set DISPLAY=:1 and WAYLAND_DISPLAY=wayland-1.
    • A Mac account name that contains a dot, such as first.last, is accepted when the native display is prepared.
  25. 6.33.8
    • aidcx update aligns the managed Linux environment to the launcher the update installed, and keeps the downloaded launcher for the next launch when Windows cannot replace the running one.
  26. 6.33.7
    • aidcx start --name resumes a stopped container of the same workspace instead of colliding with it, and a folder that is already a Git repository is not initialised again.
    • A failed sign-in renewal keeps the credential stored inside the managed Linux environment.
    • aidcx list keeps one row for a worktree whose branch was switched and marks the difference.
    • aidcx doctor, aidcx health and aidcx inspect report the Linux environment's findings; inspect lists the containers, images and volumes of a container's own Docker daemon, and USB is reported as unsupported on macOS and Windows.
    • On macOS, virtualization tools installed by other means cannot redirect the managed VM, and aidcx update aligns the Linux environment to the version being installed.
  27. 6.33.6
    • Creating a container with a shared display no longer breaks copying files into it under the secure runtime.
  28. 6.33.5
    • Shells and editor sessions open as your own account instead of root, and the KVM device group appears by name.
    • Starting an existing environment with a different audio mode recreates it so the new mode takes effect.
    • aidcx update installs the latest public build of the channel when your credential does not allow the update.
    • A sign-in stored inside the managed Linux account is found when no host sign-in file exists.
    • Installs on headless Linux and WSL bring up the display bridge in the same run, and plain docker exec opens as your account.
  29. 6.33.4
    • More reliable account ownership when preparing new project environments.
    • Recreate an existing environment when adopting the changed preparation behavior; ordinary reuse does not rebuild it.
  30. 6.33.3
    • Corrected container home-directory ownership and Windows Store channel selection.
    • Improved account consistency between the host and managed Linux runtime.
  31. 6.33.2
    • Containers use the intended managed-runtime login account.
  32. 6.33.1
    • Corrected home-directory and account detection on macOS.
  33. 6.33.0
    • Simplified macOS runtime installation and graphics preparation.
  34. 6.32.3
    • Simplified macOS runtime packaging and storage layout.
    • Changed the macOS and Windows workflow: native operational commands are refused. Prepare the runtime on the host, then run bare aidcx to enter its Linux terminal for diagnostics and project work. Existing scripts that run those operations directly on the native host must move that work into Linux.
    • Improved launcher terminal handling.
  35. 6.32.2
    • The macOS runtime keeps running after the installer's terminal closes.
    • Improved installation progress, retries and update previews on macOS.
  36. 6.32.1
    • Maintenance release.
  37. 6.32.0
    • scaffold --upgrade refreshes pinned versions while preserving project choices; fresh configurations now enable systemd and an inner Docker daemon, with audio, USB and mesh off.
    • Install, update and uninstall previews no longer apply their plans; installation scope flags are Linux-only.
    • Doctor identifies missing required software more clearly, and installation reports platform-specific recovery guidance.
    • Improved interrupted-start cleanup, worktree naming and submodule setup progress.
    • Improved Windows installation and cold-start handling, and macOS runtime and credential recovery.
  38. 6.31.1
    • On Windows, the container user is built with the same user ID as your WSL distribution, which fixes missing-user errors and degraded Kubernetes wiring after start.
    • A slow cold start of the WSL virtual machine is retried within one five-minute budget instead of failing the import, and Docker image data stays on the dedicated WSL Docker disk.
    • aidcx health and start name the real cause when no container user resolves or when Docker credential wiring cannot write your home directory, with a suggested fix.
  39. 6.31.0
    • aidcx start --branch no longer shows a spurious "gitdir pointers unusable" warning after a successful start, and one failing submodule no longer stops the others from being set up.
    • A start now ends with a readiness line such as Workspace ready: 87/112 submodules (22 failed, 3 unknown), the problem folders (up to ten) and one recovery command, aidcx start --branch <branch>. The exit code stays 0 on partial failure.
    • Running aidcx start --branch <branch> again finishes the unfinished submodules under your original --submodules choice and never touches folders with local work. Submodules are set up faster and retried once after a temporary network error. aidcx health counts submodules recursively.
    • Each container gets its own private, read-only credential access for Git, Docker and Kubernetes; a container sees only its own. Docker sign-ins work for every registry you are signed in to, and Kubernetes sign-ins are tied to the context and server chosen at start and refuse a cluster whose certificate cannot be verified. Containers created by an earlier launcher have no credential access until they are recreated (aidcx start --rebuild).
    • --sso now shares only Git, Docker and Kubernetes; AI coding tools travel only through --aidev, which copies their configuration and history into Kubernetes and nested environments. The ssoPolicy and Docker-cleanup start options are gone, and aidcx gc -a with --until applies one cutoff to every class.
  40. 6.30.2
    • aidcx doctor no longer reports a running macOS virtual machine as not running.
    • The installer verifies its download on a Mac or Linux host that has no signature tool.
  41. 6.30.3
    • Maintenance release.
  42. 6.30.1
    • aidcx start --effective is a read-only preview: it no longer probes, offers an install, starts the virtual machine or proposes an upgrade.
    • On a Mac, a credential connection inside the runtime that something else has taken over is detected and re-checked.
  43. 6.30.0
    • On a Mac, the credential bridge is on by default and is always restarted; it keeps working when you start from an SSH session and reattaches by itself after a runtime restart.
    • On a Mac, aidcx start waits for the Docker daemon after an install and re-enters the normal start once the runtime is up.
    • The Mac credential provider is more robust and shows why it is not attached.
  44. 6.29.0
    • On macOS and Windows, aidcx start and aidcx exec stop with a per-platform remedy when the launcher inside the virtual machine or distribution is verifiably different from the host launcher; aidcx also brings the guest launcher in line, or records why it could not.
    • The launcher never downgrades the guest from the channel's newest release and flags host builds that are not published.
  45. 6.28.0
    • On a Mac, one runtime component replaces the four separate runtime packs.
    • A Mac that still reports the old runtime is pointed to aidcx install --user.
  46. 6.27.0
    • aidcx start waits for the guest display to come up at the end of the start instead of warning before it exists.
  47. 6.26.2
    • Maintenance release with updated shared components.
  48. 6.26.1
    • The Git credential helper is wired into the container when the live credential bridge is active.
  49. 6.26.0
    • aidcx gc -a now covers images, stopped containers and volumes, and --until applies one cutoff to every class. The short-lived --legacy-snapshots option is removed.
  50. 6.25.0
    • The Windows installer's Store option defaults to the stable product and warns about an aidcx.exe that would shadow the Store command.
  51. 6.24.0
    • New aidcx gc --legacy-snapshots reclaims space from the old container store, and inspect and health now point it out.
  52. 6.23.0
    • On a Mac, the new aidcx-bridge background agent replaces the DNS-only agent; aidcx bridge status reports its health.
  53. 6.22.1
    • On a Mac, the Docker data disk is mounted before the Docker daemon starts, and a failed mount no longer stops the start.
    • The native display is more robust against stale sessions, and a missing display component is restarted.
    • aidcx uninstall, stop and delete run without a MAIT credential.
  54. 6.22.0
    • New aidcx gc cleans the Docker daemon inside a running container; inspect, health, doctor and the MCP status report the last cleanup.
  55. 6.21.0
    • Maintenance release for the Windows Store update.
  56. 6.20.2
    • The Windows Store update can now be started from aidcx with a proper owner window.
  57. 6.20.1
    • On a Mac, the first start no longer warns that Docker is not yet responding.
  58. 6.20.0
    • Changed (output): aidcx stop and aidcx delete name every container as NAME (ID12) (for example aidc-proj-main (1a2b3c4d5e6f)), the same two values aidcx list shows. Scripts that match container <id> stopped or deleted and reclaimed need updating.
    • aidcx stop and aidcx delete no longer start with every container checked: toggle rows with space, check all with a, clear with n; q cancels with exit code 130. Without a terminal the command lists the candidates and acts on nothing. New --all acts on every candidate without a picker; -f skips only the confirmation.
    • aidcx delete always asks Delete NAME (ID12)? [y/N], and a mistyped --name or --id fails with the available containers listed.
    • aidcx stop shuts a container down from the inside first (optional pre-stop hook, inner containers, the inner Docker daemon, systemd), then docker stop, then docker kill. Exit code 3 means stopped, but only by force. customizations.aidcx.stop in devcontainer.json tunes it.
  59. 6.19.1
    • Maintenance release.
  60. 6.19.0
    • The Windows installer can install the Store package with winget, and only one Store channel is kept installed. Public Store availability is not established by this release source.
    • A Store-installed launcher is updated through the Microsoft Store.
  61. 6.18.0
    • The Windows Store build now covers every product identity in a single binary.
    • Sysbox install progress is reported under the right step.
  62. 6.17.0
    • Install, update and uninstall follow one settled plan, and each error is shown once.
    • On a new Mac, the launcher inside the virtual machine is verified after it is installed.
  63. 6.16.0
    • On Windows 11 the launcher can run as a packaged Microsoft Store app whose updates the Store owns; the installer recognises the Store package. Public Store availability is not established by this release source.
  64. 6.15.7
    • Native Linux display bridges recover after a reboot and after aidcx update.
  65. 6.15.6
    • Maintenance release.
  66. 6.15.5
    • Clearer message when a workspace start is blocked by an account access requirement.
  67. 6.15.4
    • Maintenance release with updated shared components.
  68. 6.15.2
    • Maintenance release.
  69. 6.15.0
    • aidcx install and aidcx uninstall now require a valid sign-in. Sign in before preparing or removing the runtime; these commands do not renew credentials.
    • Invalid execution targets and root-level uninstall attempts report their setup error before checking credentials.
  70. 6.14.4
    • Host setup and removal use aidcx install and aidcx uninstall instead of --install and --uninstall; update existing commands and scripts. The existing scope, repair and force options remain flags.
  71. 6.14.3
    • Refreshed Linux display credentials remain visible to running containers that use the new folder mount.
    • X11 health checks report stale or rejected display access.
    • Existing single-file authority mounts need a coordinated one-time migration; the launcher does not restart them automatically.

September 2026

  1. 6.14.1
    • legal is now only a subcommand; the --legal flag is rejected.
  2. 6.14.0
    • New aidcx legal shows the copyright notice and the third-party components built into aidcx; it works offline.
    • Clearer help about which release versions your credential lets you see.
  3. 6.13.5
    • Maintenance release with updated shared components.
  4. 6.13.4
    • Faster commands on Windows.
    • aidcx now works only with MAIT projects under the secure runtime: --runtime host, other project types and files with the secure runtime turned off are refused with a clear error.
  5. 6.13.3
    • Clearer warnings and doctor messages, with fewer false alarms.
    • Broken lines in devcontainer.json are commented out automatically, with a backup; use --invalid-lines fail to stop instead.
    • aidcx update now fails when updating the managed Linux VM or WSL distribution fails.
    • More reliable USB devices attached while a workspace starts.
    • Sound and container networking now state the services they need.
  6. 6.13.2
    • A shorter sign-in sharing picker.
    • Kubernetes targets on macOS: named workspaces work as expected.
  7. 6.13.1
    • Fixes for sign-in sharing with Kubernetes and for choosing a workspace by name.
  8. 6.13.0
    • Sign-in sharing now covers Kubernetes.
    • Added the nested-workspace launch path; it requires a suitable parent image and does not establish availability in the selected MAIT image.
  9. 6.12.1
    • Sign-in sharing is one setting, --sso, with ai and dev groups.
    • Stop and delete can act on several workspaces at once.
    • start --name sets the workspace's container name.
    • The interactive carry-over picker is back.
  10. 6.12.0
    • Sign-in sharing reaches more AI tools: GitHub Copilot, OpenCode and Grok.
    • Choose what to share when you scaffold a project; start honours the saved choice.
    • Credential reads are recorded for later review.
  11. 6.11.1
    • Maintenance release.
  12. 6.11.0
    • More reliable preparation and repair on Windows and macOS.
    • Container networking can join every eligible network automatically.
  13. 6.10.1
    • Container networking starts without extra administrator prompts.
  14. 6.10.0
    • Added container-network membership and connectivity support; usable traffic still requires a compatible image and runtime.
    • Windows keeps Docker data across updates and repairs.
    • macOS gives Docker a growable data disk.
  15. 6.9.6
    • Repair on Windows can restore the managed Linux environment.
  16. 6.9.3
    • The managed environments on macOS and Windows are named "mait".
  17. 6.9.2
    • Sound settings apply at each start.
    • Better memory detection on Windows.
  19. 6.9.1
    • Safer updates, with a minimum compatible project configuration.
    • Progress while Windows and Docker warm up on a cold start.
    • The installers print the same clear progress as aidcx.
  20. 6.8.0
    • Windows installs aidcx in your programs folder, with the signature checker beside it.
    • Clearer message when a security product locks aidcx on Windows.
    • Friendlier messages.
  21. 6.7.2
    • Doctor checks nested Docker under the secure runtime.
  22. 6.7.1
    • Update notes follow the release channel you use.
    • Sound relay fixes.
  23. 6.7.0
    • USB devices: pass them all, or attach and detach them one at a time.
  24. 6.6.0
    • Sound modes: your speakers and microphone, sound inside the workspace, both, or off.
    • aidcx feature shows the live state of each setting and connects sound devices.
  25. 6.5.1
    • . and .. work in workspace paths and file copies.
  26. 6.5.0
    • Update checks cover the graphics components too.
  27. 6.4.0
    • New aidcx cp copies files and folders into and out of a workspace.
    • The workspace registry handles names and aliases reliably.
  28. 6.3.1
    • Sign-in sharing for six more AI coding tools.
    • More reliable preparation on macOS.
  29. 6.3.0
    • Warns about project mounts that would overlap shared sign-ins.
  30. 6.2.0
    • Sign-in sharing for Git, Docker and Claude Code.
  31. 6.1.14
    • Windows: credential migration no longer hangs.
  32. 6.1.13
    • Git sign-in sharing no longer opens an extra prompt.
  33. 6.1.12
    • Sign-in sharing: workspaces use your Git and Docker sign-ins from the computer.
    • Clearer errors when a container fails to start.
  34. 6.1.10
    • Secure runtime fixes on macOS.
  35. 6.1.9
    • GPU access on Windows.
  36. 6.1.8
    • Secure runtime fixes.
  37. 6.1.7
    • Graphics fixes for applications in the workspace.
    • A note when the requested release channel differs from the release access granted to the account.
  38. 6.1.6
    • Graphics fixes on macOS.
  39. 6.1.5
    • More reliable install and uninstall.
  40. 6.1.4
    • More reliable secure runtime installation.
  41. 6.1.3
    • More stable graphical applications on macOS.
  42. 6.1.2
    • Graphics fixes on macOS.
  43. 6.1.1
    • Graphical application windows on macOS.
  44. 6.1.11
    • Maintenance release.
  45. 6.1.0
    • Graphical applications on macOS through the managed display.
  46. 6.0.2
    • macOS fixes after a restart.
  47. 6.0.1
    • macOS no longer needs a separate Docker command-line install.
  48. 6.0.0
    • New macOS runtime.
    • More reliable Docker connections on every platform.

August 2026

  2. 4.12.1
    • Fixed NVIDIA GPU files being hidden by the container's service manager.
  3. 4.12.0
    • NVIDIA GPU passthrough is preferred when the host has the NVIDIA userspace installed.
  4. 4.11.3
    • Install now shows a row for the bridge-unit step and its live progress display no longer gets garbled by service commands.
  5. 4.11.4
    • Maintenance release.
  6. 4.11.2
    • Install records are more precise across platforms, and a nudge appears when a record is missing.
  7. 4.11.1
    • Repair now also re-runs the Docker install topic.
  8. 4.11.0
    • New aidcx --install --repair forces install steps to run again.
  9. 4.10.2
    • Maintenance release.
  10. 4.10.0
    • New workspace registry with remote addressing and a discover command, plus a better picker when a workspace is missing.
    • Progress displays are consistent across commands, Sysbox rebuilds are detected, and health volume suggestions are consolidated.
  12. 4.9.0
    • The Sysbox ownership check moved from doctor to health, with consistent suggestions.
  14. 4.8.0
    • Install now chooses between system and user scope more consistently and checks readiness up front.
    • Health and inspect no longer leave a permanent line per check, and install topic headers are no longer printed twice.
    • Install shows the real Sysbox version and prints the system-install hint only once.
  16. 4.7.4
    • A Sysbox upgrade that has been applied is no longer shown as still available.
  17. 4.7.3
    • Sysbox update detection now checks the platform of the guest environment rather than the host.
  18. 4.7.2
    • Sysbox versions are now compared correctly, and progress displays in health and inspect no longer run out of room.
  19. 4.7.0
    • aidcx upgrade is removed; update information now appears in health and inspect.
  20. 4.6.2
    • Scaffolding goes back to floating major.minor pins, and the update check is now fully silent.
  21. 4.6.1
    • A newer image patch within your pinned line is now detected, and doctor's requirements check no longer gets stuck.
  22. 4.7.1
    • Maintenance release.
  23. 4.6.0
    • aidcx now detects stale components, including the Mac VM base, and reports binary, requirement and image updates in one place.
    • Scaffolding writes the exact patch version while keeping the major.minor pin.
  24. 4.5.0
    • The image and features are now pinned to a major.minor version.
    • aidcx detects and offers Sysbox updates, and --name and --id replace --instance for selecting a container.
    • Cleaner list columns and no more overlap between pickers and spinners.
  25. 4.5.1
    • Maintenance release.
  26. 4.4.0
    • prune is now a checkbox-driven bulk cleanup, and delete also removes the worktree, replacing --prune.
    • Containers started with a custom instance are no longer mistaken for worktree-backed ones.
  27. 4.3.0
    • The carry-over file list now uses a tree picker.
    • Mismatched submodule pointers and files missed during warm-up or carry-over are now reported.
  28. 4.2.2
    • Closed remaining gaps where long steps showed no progress.
  29. 4.2.1
    • Added progress spinners to list and logs.
  30. 4.2.0
    • Commands that used to run silently now show progress indicators, and health and inspect run their checks in parallel.
  31. 4.1.0
    • Host and guest commands are now separate, and isolation between host and guest is tighter.
    • Nested KVM is enabled on supported Macs, and Fedora (including arm64 and Asahi) is supported for the secure runtime and GPU detection.
    • aidcx --uninstall now removes only what you installed, and respects --dry-run and the install scope.
    • Installation is more reliable and honest on Windows and Mac: it reports clearly when something was not completed and converges on a clean install.
    • Branch warm-up is faster and no longer hangs on a git credential prompt.
  33. 4.0.3
    • Fixed the container user's host user and group IDs not resolving at runtime.
  34. 4.0.2
    • Fixed several Mac problems: dotfile and state mounts inside the VM, a false XQuartz warning, a stale display warning, and a login deadlock during install.
    • The devcontainer lock file is regenerated when the version is upgraded.
  35. 4.0.1
    • Maintenance release.
  36. 4.0.0
    • Mac audio now works in both directions: with --audio on, the microphone and speakers are available in the container, on Apple Silicon through the managed VM.
    • Intel Macs are no longer supported; a Mac now needs Apple Silicon, and aidcx keeps its own VM separate from any other Colima setup you have.
    • Windows setup is more reliable, including WSL2 installation in one pass, a reboot prompt on fresh Windows 11, and a fallback for non-admin users.
    • New --user and --system install scopes and a Docker group picker, plus an embedded MCP server with status, start and stop tools.
    • Mac display forwarding, DNS following the Mac's network, and doctor checks for XQuartz were added.

July 2026

  1. 3.18.2
    • Further fixes.
  2. 3.18.1
    • Bug fixes.
  3. 3.18.0
    • All feature flags now use on and off consistently.
  5. 3.17.0
    • New option to mount AI tool home folders into the container, with protection against mounting your whole home directory.
    • Binary features are now written and accepted as on or off, and the container knows its own instance name.
    • Removed an unneeded requirement from the secure runtime prerequisites.
  7. 3.16.0
    • Access to the host's Docker now goes only through the managed bridge relay.
    • The feature-version check also applies when scaffolding, and optional choices in the scaffold picker sit behind a toggle.
  8. 3.15.3
    • DNS forwarding now loads all of the host's upstream servers, and the reported server count is accurate.
    • aidcx now checks that the requested feature version exists before pinning to it.
  10. 3.15.0
    • The scaffold can now enable libvirt, KVM and Docker.
    • Fixed gaps in the secure-start checks and in a few command-line flags.
  12. 3.14.0
    • The X11 display connection is now always relayed per user and uses the host's detected display, with a more accurate doctor status.
    • Fixed a startup problem when several users share the same host.
  14. 3.13.0
    • Mac GPU support is installed per component set, so each GPU build is set up independently.
  15. 3.12.0
    • Container DNS is now surfaced in the status output and kept working through a local forwarder.
    • Starting a branch now resolves the remote's default branch automatically.
  16. 3.11.0
    • Docker, KVM and libvirt options are simplified: Docker is now one setting that can be off, on or use the host's, and doctor, health and inspect report all three consistently.
    • --debug now includes everything --verbose shows.
    • Pickers only offer instances that fit the command you are running, and upgrade checks look across the whole version line.
  17. 3.10.1
    • Containers can now use the host's GPU, including a software-rendering mode that works on every platform, and aidcx opens the GPU render devices for secure containers.
    • On Windows and Mac, aidcx now runs through its own managed Linux environment, with X11 display forwarding and audio relayed to the container.
    • New aidcx inspect, health and distill commands show what a running container uses, flag size and performance problems, and let you choose what to keep when saving a container.
    • Starting a branch checkout fills in the workspace and submodules automatically, and aidcx exec now supports interactive sessions.
    • Setup is more reliable on Windows (WSL2) and Mac, and downloaded components are now checked for authenticity.
    • First tagged releases (3.10 to 4.12, July to August 2026): one --dockerd setting for Docker inside the workspace, your computer's Docker or neither, reached through the launcher relay.
    • Graphical applications use your desktop's display; GPU support on macOS, and automatic NVIDIA selection on compatible Linux hosts.
    • Shares your AI coding tools' settings with the workspace; every on/off setting uses on and off; Apple silicon is required on macOS, with microphone input.
    • Workspace registry with short names, --name and --id addressing, a tree picker for branch carry-over and a checkbox aidcx prune.
    • One update check for the launcher, its requirements and the workspace image; aidcx install --repair, readiness-first installation, progress indicators and a secure-runtime ownership check in health.