Changelog

November 2026

1. 8 Nov
   AIDC Launch (aidcx)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. 8 Nov
   AIDC3.18.0Edge

   • Ansible-core 2.22 and later now run on a Python 3.13 runtime by default.
3. 8 Nov
   MCP AIOM0.6.0Edge

   • Two read-only tools replace the content-listing model: aiom_load returns the framework as one paged document for the workspace, and aiom_env reports the workspace state with actions and a checklist.
   • Removed without aliases: aiom_list_content, aiom_read_content, aiom_skill, aiom_check_version, the skill:// and aiom:// resources and the list, show, prompt and info commands. New commands: load and env.
   • Stricter checks on worktree and outside-root paths; serves AIOM 0.23.0.
4. 8 Nov
   MCP Docs2026.1108.2Edge

   • The version shown by mcp-docs version now reads like 2026.1108.2+mait.g1a2b3c4, so the build is easy to identify.
   • Heading markup is no longer visible in the documentation text returned by the tools.
   • The documentation set now includes the AIDCX MCP tools, telemetry tools and container mesh pages.
5. 8 Nov
   MCP Docs2026.1108.1Coming

   • Version numbers now carry the release date as YEAR.MONTHDAY.COUNTER (this release is 2026.1108.1). mcp-docs version also shows the build id, for example 2026.1108.1+mait.g1a2b3c4.
   • The documentation set is the same as in 2026.11.1.
6. 8 Nov
   MCP Docs2026.11.1Coming

   • Refreshed the whole user documentation set: clearer first-run steps, shorter troubleshooting pages, a new book for the VaaS command-line tool, and the MCP Kubectl interactive tools.
   • Removed pages for internal tools and retired product notes, so the set only covers what users run.
7. 8 Nov
   MCP Kubectl0.11.0Stable

   • New interactive tools: port forwarding and debug containers.
   • Apply can prune resources it no longer declares, and delete accepts selection options.
   • Config read subcommands and clearer confirmation requirements.
8. 8 Nov
   MCP Registry0.10.1Edge

   • A backend that is not an MCP server and keeps exiting is no longer restarted without limit.
9. 8 Nov
   MCP Stub0.8.1Edge

   • The stub finds the registry in every socket folder it may run from.
10. 7 Nov
    AIDC Launch (aidcx)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.
11. 7 Nov
    AIDC Launch (aidcx)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.
12. 7 Nov
    MCP Console0.15.0Stable

    • Access no longer needs a separate token to manage.
13. 7 Nov
    MCP Playwright2.4.2Stable

    • Maintenance release.
14. 7 Nov
    MCP Registry0.10.0Stable

    • Breaking: the separate multiplexer token is gone. MCP_MULTIPLEXER_TOKEN is no longer set for backends and a multiplexer_token entry property is ignored; remove it from registry files and backend environments.
    • Environment variable expansion now matches the rest of the platform.
15. 7 Nov
    MCP Stub0.8.0Coming

    • mcp-stub serve takes exactly one of three forms: bare (connects only to the main registry and never starts one), --registry-json <file> (attaches to or starts the main registry from that file) or --server <endpoint>.
    • Removes the registry key and registry binary arguments; unknown arguments are rejected. Bare serve with no registry fails with a clear error. Use MCP_STUB_REGISTRY_BINARY to name the registry executable.
16. 7 Nov
    MAIT image1.12.3

    • Maintenance release.
17. 6 Nov
    AIDC Launch (aidcx)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.
18. 6 Nov
    AIDC Launch (aidcx)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.
19. 6 Nov
    AIDC Launch (aidcx)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.
20. 6 Nov
    MAIT image1.12.2

    • Improved X11 and registry start-up inside the container.
21. 6 Nov
    MAIT image1.12.0

    • The image now ships a shared MCP registry that starts with the container.
    • The registry service restarts cleanly without stale state.
    • Environment files for aidcx are now owned by root, so they require aidc-init 3.15.0 or newer.
22. 6 Nov
    MCP Console0.14.0

    • Persistent terminals are partitioned per client, restored under their original owner after a restart, and reattached when the owner uses them again; access from other clients is refused.
    • Terminal events are delivered only to the client that owns the terminal.
    • Access secrets are no longer exposed to child processes or the shared terminal service.
    • Sending input and starting terminals now retry on failure and report full errors.
23. 6 Nov
    MCP AIOM0.5.22Stable

    • The load protocol is now available to agents as a runbook resource.
24. 6 Nov
    MCP Playwright2.4.1

    • The browser tool is now found reliably when the server starts.
25. 6 Nov
    MCP Playwright2.4.0

    • WebGPU and WebGL now stay available in software mode when no hardware acceleration is present.
    • Graphics setup is more reliable: Vulkan is chosen by the live device, graphics overrides set at browser start are honored, and a rendering issue on virtualized GPUs is avoided.
26. 6 Nov
    MCP Registry0.9.2

    • Nested default values in environment settings are now supported.
27. 6 Nov
    MCP Registry0.9.1

    • Removes a misleading legacy backends warning.
28. 6 Nov
    MCP Registry0.9.0

    • Each connected client now gets its own instance, state directories and tool overlay, and notifications are routed to the right client.
    • Agents' existing MCP servers can be proposed for migration into the workspace registry, and first-seen clients are guided through onboarding.
    • Server entries can be enabled or disabled, a workspace marker can override a lower-precedence entry, and registry sources are watched and reloaded automatically.
    • Security is tightened: access is limited to your own user, local data is kept private, and secrets are no longer sent over plain HTTP to remote hosts.
    • OAuth tokens move to a new location under the user's MAIT folder.
29. 6 Nov
    MCP Stub0.7.1Stable

    • Maintenance release.
30. 6 Nov
    MCP Stub0.7.0

    • The stub now forwards the agent's identity and the registry's instructions to the agent, and attaches to an existing registry before starting a new one.
    • Only your own registry is trusted, and GPU settings still pass through to it.
    • The old registry-json option is still accepted but is ignored with a clear deprecation warning pointing to the new configuration file.