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 30 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.
Load more releases