Mage-OS 4.0.0 landed on 30 October 2026 on a Magento Open Source 2.4.9 base, bringing a native AI assistant, WebAuthn passwordless login, built-in product feeds, and a reworked multi-source inventory engine - all free.

Mage-OS, the community-governed, Adobe-independent fork of Magento Open Source, shipped version 4.0.0 on 30 October 2026, built on the same Magento Open Source 2.4.9 base we've covered elsewhere on this blog. It's the most ambitious Mage-OS release to date, and a genuinely good news story to close out a year that's otherwise been dominated by Magento security headlines: a free, community-built platform shipping its own native AI assistant, passwordless authentication, and built-in product feed integrations that used to mean a paid extension.
The headline feature is Mago, an administrative AI assistant that lets you query live store data in natural language and get back real answers: stat cards, charts and tables, not just a chat response describing what you could go and look up yourself. You can also make store changes through the chat interface instead of navigating admin screens manually, with slash commands like /cache flush or /index reindex executing directly. Every irreversible action shows its impact before you confirm it, which is a sensible design choice for a tool that can genuinely change store configuration on request.
The genuinely notable detail is how open the implementation is: Mago supports OpenAI, Anthropic, Gemini, Azure OpenAI, DeepSeek, OpenRouter, Hugging Face, Ollama, LM Studio and any OpenAI-compatible gateway, configured under Stores > Configuration > Mage-OS > AI Configuration. You bring your own API key and your own choice of model provider, including fully local options like Ollama or LM Studio for stores that don't want prompts leaving their own infrastructure at all. Mage-OS is upfront that API keys are encrypted at rest and that prompts and responses aren't stored, and token usage is tracked under Reports > AI Token Usage so you can actually see what you're spending. Mago ships off by default, so it's an opt-in addition rather than something switched on without a merchant's choice.
It's a useful point of contrast with Adobe's own agentic-commerce push this year: the Commerce MCP Server and Commerce Developer Agent are Adobe Commerce-specific, Adobe-curated tools. Mago is doing something adjacent (AI-assisted store management) in the open-source line, for free, with your choice of model provider rather than a single vendor relationship.
A new module-seo adds JSON-LD structured data for products, organisation details and breadcrumbs across 16 product-type templates, plus Open Graph and Twitter card generation and proper multistore hreflang support, superseding the older module-meta-robots-tag and module-hreflang modules entirely (more on that below, since it's the one step you can't skip during upgrade). A companion module-aeo module serves /llms.txt, /llms-full.txt and /llms.jsonl endpoints with controls for 14 named AI crawlers, defaulting to allowing CCBot and Bytespider. A theme-agnostic FAQ manager rounds this cluster out, with its own FAQPage schema matching whatever content you actually publish.
Together, this is Mage-OS building the AI-discoverability groundwork that a lot of merchants have been bolting on through third-party modules. Worth checking whether anything you're currently paying for just became redundant.
A new module-passkey-auth brings WebAuthn/FIDO2 passwordless login to both Luma and Hyvä storefronts, with full REST and GraphQL support and self-service passkey management for customers. It doubles as an admin two-factor authentication provider. It's off by default and requires HTTPS, which is a sensible default for a feature that's genuinely new to the platform rather than a long-established pattern merchants are already used to configuring.
A new module-shopping-feed adds native integrations for Google Shopping, Google Local Inventory, Google Promotions, Meta, Pinterest, TikTok and Microsoft Merchant Center, with FTP/SFTP delivery and source-level local inventory feeds that plug into the MSI overhaul below. Feeds produce nothing until you actually define one, so there's no surprise behaviour on upgrade, but if you're currently paying for a feed-management extension purely to cover these channels, it's worth a direct comparison.
The MSI changes are the most technically significant part of this release. Reservations now happen at the source level rather than globally, with proper oversell detection, invariant guards and reconciliation, each independently configurable. A new Stock Visualizer gives shoppers a storefront-facing view of availability per source and variant. Under the hood, reindexing now runs in parallel per stock dimension, with one async message per stock and chunked cleanup of compensated reservations, which should meaningfully help reindex performance on larger multi-warehouse catalogues.
This is also where the upgrade has real teeth. The place-order lock is now taken at the source level during order submission rather than globally, and shipments resolve their allocated source directly instead of falling back to a default. If you have any custom order-placement or shipment-source-selection code, test it specifically against this release before going live. This is the one area of 4.0.0 where "drop-in upgrade" genuinely needs a caveat.
An Extension Directory lets you browse roughly 1,100 open-source modules directly from the admin, showing installed/update badges sourced from your own composer.lock. It never installs anything on its own; it's a discovery and audit tool. ScopeHint2 shows you which configuration scope a given admin field's value is actually overriding, which is a small thing that saves a genuinely annoying class of "why isn't this setting taking effect" debugging session. Under the hood, setup:di:compile runs faster with a smaller compiled output, full-page cache invalidation is fixed for multi-frontend setups, and there's native WebP/AVIF image upload and processing.
From an existing Mage-OS 3.6.x install, the migration is a drop-in upgrade with no PHP version changes required. The one step you genuinely cannot skip: remove mage-os/module-meta-robots-tag and mage-os/module-hreflang from your root composer.json before upgrading, since the new module-seo declares a Composer conflict with both. module-seo does ship a data-migration patch and import command that carries your existing settings across with an admin notification, so you won't lose your current SEO configuration, but you do need to remove the old modules first rather than let Composer fail on the conflict. After upgrading, recompile (the compiled DI format changed) and make sure your queue consumers are running, since AEO document generation and SEO rebuilds depend on them. Fill in your Organization details under Marketing > SEO before relying on the new structured data and /llms.txt output. Mage-OS 3.6.0 itself reaches end of life with this release, so if you're still there, this isn't an optional upgrade to defer indefinitely.
Most of the headline features (passkey login, AEO documents, AI crawler rules, Stock Visualizer, source-level reservations, and Mago itself) ship off by default, so an upgrade won't change your store's behaviour until you deliberately turn each one on.
2026 has not been a quiet year for Magento's security story (we've covered that run of advisories in detail elsewhere on this blog), but Mage-OS 4.0.0 is a reminder that the open-source side of this ecosystem is still building, not just patching. A genuinely novel AI assistant, real passwordless authentication, and feed integrations that used to cost money, shipped for free by a community project, alongside the kind of active events calendar we've written about separately in Mage Camp, Meet Magento Prague, and a thriving open-source community. It's exactly the kind of release that's easy to miss if your Magento news diet is mostly CVE bulletins. Worth not missing this one.
If you're considering a move to Mage-OS, from either Magento Open Source or Adobe Commerce, Deploy can help assess what the migration actually involves for your specific store and extension stack.
Source: Mage-OS's official 4.0.0 release announcement, 30 October 2026.
Last updated 30 October 2026.