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

Showing the latest 60 of 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.
Load more releases