diff --git a/content/en/docs/releasenotes/studio-pro/11/11.16.md b/content/en/docs/releasenotes/studio-pro/11/11.16.md
new file mode 100644
index 00000000000..730fb54b438
--- /dev/null
+++ b/content/en/docs/releasenotes/studio-pro/11/11.16.md
@@ -0,0 +1,127 @@
+---
+title: "11.16"
+url: /releasenotes/studio-pro/11.16/
+description: "The release notes for Mendix Studio Pro 11.16 (including all patches) with details on new features, bug fixes, and known issues."
+weight: 84
+# KI: "Maia Chat pane issue": MID-317
+# KI: "BYO LLM": SPAM-435
+# KI: "Mx.exe commands": SOLP-4224
+# KI: "GUIDs are not restored": SOLP-4209
+# KI: "Breaking client certificate auth": REST-751
+---
+
+{{% alert color="info" %}}For highlights of this release, see the [Mendix Release 11.16](https://www.mendix.com/blog/mendix-release-11-16/) blog post.{{% /alert %}}
+
+## 11.16.0 {#11160}
+
+**Release date: October ___, 2026**
+
+{{% button color="info" href="https://marketplace.mendix.com/link/studiopro/11.16.0" text="Go to Marketplace" title="Download version 11.16.0 from the Marketplace" %}}
+
+### New Features
+
+#### Maia New Features
+
+* The **Changes** pane now shows changes made by Maia. You can see which elements and properties changed inside documents. Additionally, starting a commit now triggers the keep all action for documents generated by Maia.
+* Maia can now create Import Mapping and Export Mapping documents using JSON Structures as a source, and auto-map the mapping to new entities. Changing existing Import Mappings and Export Mappings is not supported yet.
+* Maia now supports creating and editing Java action documents and Java action source code files.
+* You can now attach more file types (CSV, JSON, XML, YAML, HTML, and Excel files) to your Maia chat messages. Attached files are made available to Maia for the rest of the session.
+* Maia can now delete documents in your app. Maia asks for your permission before deleting, and a deletion cannot be undone.
+* Maia now supports Plan Mode, which creates an implementation plan based on your prompt. You can review and refine the plan with Maia before implementation begins.
+* Studio Pro now includes Playwright, and Maia uses it to check the running app in its Plan-Do-Check-Act (PDCA) cycle.
+* We added a new API for interacting with the Maia agent chat (`studioPro.ai.chat`) to prefill the Maia chat window with input text and either let the user review it before sending it or automatically send it.
+
+#### Other New Features
+
+* We added a new user authentication API (`studioPro.ui.userAuthentication`) to check the signed-in state (`isSignedIn`), retrieve the user's profile information (`getUserProfile`), and subscribe to `signedIn`/`signedOut` events.
+* The **History** pane now shows a loading indicator next to the search box while background search results are still being loaded.
+* We added a pre-check to the commit process. Studio Pro now checks the integrity of your app to avoid committing a corrupted app with missing mx unit files.
+* You can now open historical versions of domain models directly from the comparison pane. For more information, see [Comparison Pane](/refguide/comparison-pane/).
+* You can now open historical versions of microflows, nanoflows, and workflows directly from the comparison pane. For more information, see [Comparison Pane](/refguide/comparison-pane/).
+* We added a **Tool Call Permissions** settings page where you can view and manage all tool permissions, including MCP tools and web fetch permissions. You can configure permissions to always allow or allow only in the current session.
+* Design mode now reacts to the following changes to an app: document exclusions, inclusions, deletions, and additions.
+* We introduced an overview that lists all modules in your app. From there, you can update Marketplace modules by providing an MPK file. In future updates, this overview will connect to the Marketplace directly to show and run available updates. To open the overview, go to **App** > **Tools** > **Module Overview** in the top bar.
+* We added a **Setup** folder to modules, allowing publishers to reference documents there and highlight them for consumers.
+* We improved the JavaScript action editor with project-aware language support. The editor now understands other JavaScript files in your app, provides type information for the Mendix Client API, and offers richer coding assistance, including automatic imports and IntelliSense for installed npm packages.
+* We added the option to manage workflow groups at runtime. In the **Workflow** tab of **App Settings**, you can now set **Group definition** to **Runtime** to create and manage workflow groups dynamically in your app instead of defining them in Studio Pro. In this mode, groups are no longer synchronized from the model on deployment. XPath constraints that use group tokens should use the **Name** attribute instead, and a quick fix is available to convert them.
+
+### Improvements
+
+* The Text Area widget no longer uses inline styling for the [Grow Automatically](/refguide/text-area/#grow-automatically) feature. This requires an upgrade of the Atlas Core module to version 3.21.1 or 4.5.1, depending on which version your app uses. (Ticket 266993)
+* We upgraded the JDBC driver for Microsoft SQL Server to version 13.6.1. If you connect to SQL Server using integrated security in a module such as [Database Connector](https://marketplace.mendix.com/link/component/2888), you may need to update the JDBC driver in `userlib` as well.
+* We added a confirmation dialog box before publishing, so you can review and confirm the action.
+* We added a **Kafka** tab to the runtime settings in Studio Pro. You can now configure Kafka settings for Change Data Capture event publishing.
+* We now show the ID attribute for each exposed entity in Change Data Capture documents, including its exposed name.
+* We added tooltips to the Change Data Capture document that explain disabled items, pending changes, and modification states.
+* We improved the Change Data Capture document by showing attributes and associations in the same order as the domain model. Deleted items are shown at the bottom.
+* We improved Change Data Capture event publishing performance by sending events in batches and updating the Kafka Producer configuration.
+* We added support for custom Kafka SASL properties in the runtime configuration for Change Data Capture event publishing.
+* Maia now combines multiple thinking blocks to reduce vertical clutter.
+* We improved the editor for published REST services in Studio Pro. It now uses a tree view that shows the resources and their operations. It also uses fewer pop-up windows. There is a toggle to revert to the old behavior under [New Features](/refguide/preferences-dialog/#new-features).
+* We changed the runtime to exit with exit code 7 instead of 0 when a cluster node fails to update its heartbeat on time. This allows service managers, such as Windows service recovery, to treat the shutdown as a failure and restart the runtime. The heartbeat check is also no longer affected by system clock changes.
+* Studio Pro now warns you when exporting a module that contains files with disallowed paths, since importing such a package is not possible. For more information, see [Import and Export Apps, Modules, Widgets, and Documents](/refguide/import-and-export/).
+* Maia now recovers from its own formatting mistakes when it calls a tool, instead of spending an extra attempt to correct them. Creating a single document is faster as a result.
+* We made the modernized App Explorer the default for all users. If you find an issue, you can fall back to the legacy App Explorer by disabling the modernized App Explorer flag in **Preferences** > **New Features** tab.
+* The modernized Find Results pane now shows an overflow button next to the result set tab bar. Clicking it opens a menu listing all result sets, with the active one marked. Selecting an item from the menu switches to that result set and scrolls it into view.
+* We changed the default names of newly created workflow events so that they identify themselves as events. Start events are now named `startEvent`, end events `endEvent`, timers `timerEvent`, and notifications `notificationEvent`. Event sub-process start events now use `startEvent` as well, instead of a name derived from their event type. Existing workflows are not affected.
+
+### Fixes
+
+* We fixed an issue where files bigger than 5 MB could not be downloaded when encryption was enabled for S3. (Ticket 279197)
+* We fixed an issue where clearing the selection with a JavaScript action did not always work for data widgets with **Keep selection** enabled, such as the Data Grid 2 widget. The previously selected rows would become selected again. (Ticket 280575)
+* We fixed an issue where an optional microflow, nanoflow, or page parameter that was explicitly configured as "(none)" would still receive a default value at runtime instead of being left empty. (Ticket 284412)
+* We fixed an issue where the `analyze-mpr` command of `mx.exe` crashed on projects containing modules with more than 10,000 documents inside. (Ticket 284495)
+* We fixed an issue where metadata was missed during a commit with a large number of model changes. (Tickets 285459, 285998, 286434, 286937, and 287069)
+* We fixed an issue where retrieving objects in offline apps could fail with a SQLite "no such column" error when an XPath constraint traversed an association to a referenced entity with specializations. (Ticket 286965)
+* We fixed an issue where Strict Mode would not work correctly with certain Client APIs and nanoflow actions in offline apps. (Tickets 287100, 282233)
+* We fixed an issue with sorting and filtering on microflow, nanoflow, or association data sources. A client error dialog would appear if users sorted or filtered by an attribute or association they could not access due to access rule constraints. (Ticket 287118)
+* We fixed an issue where a row extracted with **Extract to new grid** could not be selected in the page editor and had no **Insert row above/below** options in the context menu. Inserting a row in the extracted grid placed it at the wrong position or caused an error. (Ticket 287120)
+* We fixed an issue where a Custom Chart in a pop-up window would flood the console with type errors when users hovered over data points. (Ticket 287153)
+* We fixed an issue where signing out of native and offline-first web apps could show a database error when other database operations were still running. (Ticket 288359)
+* We fixed an issue where offline synchronization operation IDs changed between builds, which could cause synchronization errors after updating a native app. (Ticket 288359)
+* We fixed an issue where missing file content on the server caused a microflow's **Sync to device** action to fail in offline apps instead of skipping the affected objects and synchronizing the remaining objects. (Ticket 288772)
+* We fixed an issue where Prometheus failed to scrape the `/prometheus` endpoint on the admin port, because the response had no `Content-Type` header and Prometheus could not parse the `jvm_info` metric. (Ticket 289111)
+* We fixed an issue where layout grids in snippets were missing some of their classes, which caused incorrect styling. (Ticket 289135)
+* We fixed an issue where deploying an app could fail while exporting a nanoflow. This happened when a Call JavaScript action with **Use return value** turned off still had an old output variable name stored, and the nanoflow also contained a variable with that same name. (Ticket 289203)
+* We fixed an issue where widgets with an open page action that opens a page with a URL configured would not render in the React client. (Ticket 289874)
+* We fixed an issue where using an extension created from an older version of Studio Pro caused permissions to be missing in the Extensions Overview tab.
+* We fixed an issue that resulted in an index.lock error when performing a rebase.
+* We fixed an issue where branch name validation was slow when entering a name in the **Create Branch Line** dialog box.
+* We fixed an issue where renaming a document could make Studio Pro unresponsive for 30 seconds and then fail with a timeout error while the Changes pane was open.
+* We fixed an issue where the **Fetch** menu item was enabled for apps that are not under version control.
+* We fixed an issue where undoing an entity rename did not revert the automatically updated references to that entity, its attributes, and its associations in microflows, pages, and access rules. This left consistency errors pointing at names that no longer existed until the references were corrected manually.
+* We fixed an issue where consistency errors would not show up after changing security settings.
+* We fixed an issue where the runtime could start Change Data Capture snapshot processing when no CDC document was configured or when the Kafka Producer could not be created.
+* We fixed an issue where entity access rules would contain invalid module role references after copying or moving an entity to another module, preventing users from selecting and updating roles in the access rule editor.
+* In the logic editors, the expression wizard no longer selects a disabled expression type (such as 'Constant' for while loops) when it opens.
+* In the logic editors, we now check microflow or nanoflow return values for errors if the return type is set to Nothing. This prevents errors during deployment.
+* We fixed an issue in the logic editors where a selected flow, or a flow that was being changed, could be hidden behind other flows and elements. Such flows are now rendered on top.
+* We fixed the order of the buttons in the **Connect Debugger** dialog box. The **OK** button is now on the left, as in other dialog boxes.
+* In the logic editors, we fixed an issue where dragging a toolbar item did not work the first time after dragging a different one.
+* We fixed an issue where users who are not signed in to the Mendix Platform could not configure and use a custom LLM provider to chat with Maia.
+* We fixed an issue in the **JSON structure** editor where the **Custom name** field did not resize together with its column.
+* We fixed an issue where Maia page generation removed all but one translation from a page title when it read or edited a page in an app with multiple languages. Page titles now keep all their translations.
+* We fixed an issue where the custom error handler of a decision was skipped when its expression or rule failed after another decision had already been executed in the same microflow. Instead, a "No connecting flow found" error was thrown and handled by the error handler of a calling microflow.
+* We fixed a known issue where storage GUIDs were not retained during module update from an MPK file.
+* We fixed an issue where running `mx module-import`, `mx update-widgets`, or `mx rename-design-properties` on an app using MPR format version 2 converted it to version 1.
+* We fixed an issue where Maia MCP server tool selection was lost after signing out of the Mendix Platform and signing back in.
+* We improved the Studio Pro MCP Server connection handling. If you have an MCP client (such as Claude Code) connected to Studio Pro, disconnect and reconnect it after updating.
+* We fixed an issue where running different Find Results-related operations could incorrectly reuse an unrelated Find Results tag.
+* We fixed an issue in the modernized Find Results pane where an older result tag could show information from a more recent search. Each tag now keeps the search it was created with, including when switching back to it or refreshing the results.
+* We fixed an issue where comparing two lists with `=` in a client-evaluated expression (for example, in a nanoflow) used a membership check instead of true equality. Lists with duplicate elements, or the same elements in a different order, could incorrectly be considered equal. For example, `[1, 2] = [2, 1]` previously evaluated to `true`; it now evaluates to `false`, matching microflow behavior.
+* We fixed an issue where an excluded JavaScript action could not be opened in the JavaScript action editor.
+* We fixed an issue where nanoflows with the same name in different modules could call the wrong nanoflow at runtime in apps that use the React client.
+* We fixed an issue where user task captions, event sub-process captions, and user task outcome values could be longer than the 200 characters that are stored at runtime, which made the app fail when it was deployed. Captions of all workflow activities, event sub-processes, and boundary events, as well as user task outcome values, are now limited to 200 characters in their properties dialogs, and a consistency error is reported when they are too long.
+* Studio Pro now shows a consistency error when a **Complete user task** microflow action refers to a user task outcome that no longer exists (for example, because the outcome was renamed or deleted). Previously this went undetected until the microflow raised a runtime exception.
+* We fixed an issue where dynamic classes were not applied to data views and layout grids in snippets in the React client.
+
+### Known Issues
+
+* The Maia Chat pane may appear and remain functional even when Maia is disabled in **Edit** > **Preferences**.
+ * Workaround: Manually close the panel when it appears.
+* When using BYO LLM, switching back to the Mendix Platform provider and saving your configuration causes reasoning and caching to stop functioning.
+ * Workaround: Click **New Chat** to restore reasoning and caching. Note that **New Chat** is only available when the chat is not empty.
+* The `mx.exe module-import replace` and `mx.exe module-import update` commands will not rescue storage GUIDs after a module update, which will result in data loss.
+* When you use the new module update flow (when you right-click a module and choose **Update from file..**), the StorageGuids and StableGuids for native mobile are not restored. This will lead to data loss when the app is started. The usual import module flow (**App** > **Import module or Download from Marketplace**) is not affected by this issue.
+* REST, ODATA, Web Services, and all other features that use client certificate authentication fail because the client certificate is not sent. If you use client certificate authentication for these integrations, do not upgrade until a fixed version is released.
+
diff --git a/layouts/partials/landingpage/latest-releases.html b/layouts/partials/landingpage/latest-releases.html
index 265fc583002..d3f7d7db676 100644
--- a/layouts/partials/landingpage/latest-releases.html
+++ b/layouts/partials/landingpage/latest-releases.html
@@ -5,8 +5,8 @@ Latest Releases
All Release Notes
- Studio Pro 11.15.0
- September 30, 2026
+ Studio Pro 11.16.0
+ October, 2026
Projects