Moodle 5.2: React, AI with Gemini and Bedrock in 2026

Moodle 5.2 arrived on 20 April 2026 and is not an incremental update: it brings React to the core, native AI integration with Google Gemini and Amazon Bedrock, a multi-marker workflow for assignments, and a complete overhaul of activity pages. For those operating EAD at scale, this is the most important version since the leap to Moodle 4.0 — and the first in years that touches foundations, not just the surface.

TL;DR

• Released on 20/04/2026, general support until 19/04/2027 and security support until 04/10/2027.
• React enters the core via build integration, import maps and external bundles, paving the way for a modern UI.
• Native AI gains Gemini (Google) and Amazon Bedrock (with access to Claude, Titan and Llama) providers.
• Multi-marker workflow for assignments (phase 1), real-time Q&A and forum locking due to inactivity.
• Composer install, OpenTelemetry, asynchronous course reset and Moodle Design System NPM package.

What changed in Moodle 5.2 in one sentence

From 5.2 onwards, Moodle is no longer a platform exclusively based on AMD/RequireJS on the front-end and embraces React in parallel to the current stack, while standardising the consumption of generative AI via pluggable providers. In practical terms, any institution that was already planning to modernise its installation now has an inflection point: you can start investing in a new UI without forking and you can put AI to pedagogical use without relying on third-party plugins.

The lifecycle also helps with the decision. Moodle 5.0, released on 14/04/2025, has been in a security-only window since 20/04/2026. Moodle 5.1, released on 06/10/2025, remains the stable version until 05/10/2026. And Moodle 4.5 LTS, released on 07/10/2024, receives extended security support until 04/10/2027 — so those on LTS have time to plan the migration calmly, without short-window pressure.

React in the core: the architectural turnaround no one expected so soon

This is, by far, the change that will most impact the ecosystem over the next two years. Moodle 5.2 introduces the foundational infrastructure for React in the core, with four pieces:

• Build integration in Moodle's asset pipeline, without relying on an external toolchain per plugin.
• Auto-initialisation and template helpers — you mark a component in Mustache and React mounts it automatically.
• Import maps to resolve dependencies without a heavy bundler per call.
• External bundles, i.e., official support for bundles compiled outside the core.

It's worth understanding what 5.2 does not deliver: the current UI remains largely in AMD/RequireJS. React serves, at this point, as a foundation — some dashboard components and the Report Builder already use it, and the roadmap points to gradual migration in future versions.

The practical effect for plugin developers is significant: for the first time, there is an official and supported path to deliver rich interfaces (complex drag-and-drop, interactive dashboards, specific editors) without reinventing the lifecycle in AMD. Combined with the Moodle Design System published as an NPM package, it is finally possible to share tokens, colours and components between custom theme, plugin and external front-end (like a White-Label app) without copying SCSS by hand.

What this means for your installation

In practice, three immediate effects:

1. Old plugins continue to work — there is no breaking change in AMD/RequireJS.
2. Custom themes need auditing — if you have overridden Mustache of components that now use React, you will need to adapt.
3. Your front-end team can start learning React without waiting for another release cycle.

Native AI with Gemini and Amazon Bedrock

Moodle 5.1 had already brought the AI provider framework with OpenAI and Azure OpenAI. Moodle 5.2 completes the offering with Google Gemini and Amazon Bedrock as official providers — and the second is the most interesting for Brazilian companies with data sovereignty requirements.

The Bedrock provider keeps data within the configured AWS region (you choose, for example, sa-east-1 in São Paulo) and gives access to multiple foundation models:

• Claude (Anthropic) — good for long reasoning, writing and revision.
• Amazon Titan — a cheap, general-purpose option from AWS itself.
• Llama (Meta) — open weights, low latency.
• Other models available in the Bedrock catalogue.

Gemini, on the other hand, is compatible with all current core AI actions — text generation, summarisation, answer explanation and image generation. It is the simplest option for those already using Google Workspace at the institution and wanting a shorter adoption curve.

How to leverage AI in Moodle 5.2 without falling into a trap

Two points of attention that rarely appear in releases:

• Moodle exposes AI actions by context (course, activity, role), so you can release AI only to teachers in certain categories, without institutional chaos.
• The AI usage report (introduced in 5.1, refined in 5.2) shows who used it, when and in which action — essential material for institutional policy and for defending pedagogical use in audits.

After configuring AI, it's worth connecting the experience to the custom Moodle app — that's where the student gains the most from contextual suggestions and automatic corrections.

Course and activity pages redesigned

The visual overhaul in 5.2 is less flashy than it seems, but solves real pain. Activity pages have gained a standardised structure: completion indicators above the fold, dates in direct format (no more "opens on" in tiny grey letters), main actions anchored at the top, and a visible status section without scrolling.

Another underestimated change: restricted content now has a dedicated page showing availability conditions in a readable format. Previously, the student only saw "this item is not available" and was lost. Now, they read exactly what they need to fulfil (minimum grade in X, complete activity Y, be in group Z) and engagement improves.

In subsections, anchor links replace dedicated pages, and the design is cleaner, with headers and dividers instead of stacked boxes. For long courses, this significantly reduces navigation time.

Page comparison: before and after

Element	Moodle 5.1	Moodle 5.2
Completion indicator	Footer, small icon	Top, coloured badge
Dates (open/close)	Inline, grey	Dedicated block
Access restriction	Generic message	Page with conditions
Subsection	Own page	Anchor + headers
Primary actions	Scattered	Fixed top

Assessment: multi-marker workflow has arrived

The most anticipated pedagogical new feature in Moodle 5.2 is phase 1 of the marking workflow for assignments with multiple markers. You configure how many markers assess each submission, choose the final grade calculation method (simple average, trimmed average, highest, lowest) and Moodle manages the flow, keeping individual grades auditable.

In phase 1, the feature covers the basic scenario: two or more markers independently assign a grade and the system consolidates. Subsequent phases (planned in the roadmap) bring moderation, third-party review in case of divergence, and customisable workflow — common features in European universities and professional certifications.

For internal competitions and courses with qualifying grades (dissertation, monograph, expert opinion in legal courses), this solves in core what previously required a paid plugin or external spreadsheet. And it's an important shift to reduce disputes in high-stakes assessments, because each marker has their own record and the final grade has a clear trail.

Question bank revamped

Those who operate quizzes at scale will feel the immediate impact. The question bank has gained five functional changes:

1. Expandable/collapsible categories — no longer need to scroll through 200 categories to find yours.
2. Drag-and-drop to move questions and entire categories between parents.
3. In-place editing of the category name, without opening a separate form.
4. Question count visible in the list (previously you had to click to find out).
5. Movement between banks — finally you can migrate questions between courses without export/import.

In the Report Builder, the gains are wildcards in filters, read/write metrics per report (useful for DBAs to find expensive queries) and clear feedback on schedule status. Those who did weekly reports via SQL can now migrate to Report Builder without losing flexibility.

Composer, OpenTelemetry and the infrastructure side

Three changes that seem niche but change the administrator's life:

• Installation via Composer officially supported. You define moodle/moodle in composer.json, plugins become versioned dependencies, and the deployment becomes reproducible. It's the end of manually edited mod/ folders in production.
• Built-in OpenTelemetry — Moodle now exports traces in the OTel standard, connecting your installation to any modern observability stack (Grafana Tempo, Honeycomb, Datadog, AWS X-Ray) without an extra agent. In critical environments, this is the difference between finding and not finding a bottleneck.
• Asynchronous course reset — an operation that used to block the HTTP request now becomes a job, without timeout on heavy courses.

For large installations, these three points combined drastically reduce operational costs. Composer closes the CI/CD cycle, OTel replaces noisy logs, and the asynchronous reset frees up the maintenance window.

Mobile, forum and app customisation

On the student side, Moodle 5.2 arrives with a Q&A forum showing answers in real time (without refresh), automatic locking of inactive discussions, and new customisation options for the official app. But if what you want is a truly differentiated brand experience, it's still worth evaluating the path of Moodle Mobile App vs custom app — the official one covers the basics, the custom one delivers segmented notifications, a splash with the institution's visual identity, and its own enrolment flow.

When to upgrade to Moodle 5.2 (and when to wait)

There is no "upgrade now" without context. As of 28/05/2026, I would recommend as follows:

• Upgrade now if you are on 5.0 — general support ended on 20/04/2026 and you are in a security-only window. Migrating to 5.2 gives you a full year of support.
• Wait 1-2 minor releases if you are on 5.1 — 5.1 still has general support until 05/10/2026. Take the opportunity to wait for 5.2.1 or 5.2.2, which usually stabilise new APIs (React) and AI providers.
• Plan calmly if you are on 4.5 LTS — you have guaranteed security until 04/10/2027. Use the time to audit plugins, test React in staging, and train your team on AI.

Two points that block more migrations than one might think: custom theme plugins with Mustache overrides of components now using React, and payment integrations or SSO that depend on hooks changed between versions. Do an inventory before upgrading.

Next steps for your installation

If your institution operates EAD in production, the practical path is:

1. Set up a staging environment with Moodle 5.2 using a copy of the database and current plugins.
2. Run the obsolescence report (admin/tool/checkout) and validate each plugin in the Plugins Directory.
3. Configure at least one AI provider (Bedrock if you need data sovereignty, Gemini for a short curve).
4. Validate the custom theme focusing on dashboard and Report Builder components.
5. Migrate the asset build to the official pipeline (npm + core tools).

And above all, do not treat 5.2 as a cosmetic upgrade. The combination of React + AI + Composer + OTel repositions Moodle as a modern platform — and those who invest time now will arrive in 2027 with ready infrastructure, while competitors are still discussing whether or not to upgrade.

At Agathas Web, we have been operating critical Moodle environments for legal and educational institutions for over 10 years. If you need a migration assessment, plugin audit, or AI deployment with Bedrock within your AWS region, this is the type of project where we can reduce risk and window time. It's worth talking before touching production.