Released June 15, 2026.
This release gave AI tools a reliable way to write in Leed. The in-app assistant and connected MCP clients could now build a set of cross-linked pages from Leed Markdown and propose edits for you to review, without overwriting anyone’s work. It also made protected forms clearer in the CMS.
New features
Author and cross-link pages with AI
The AI assistant and connected MCP clients could now create CMS pages and documentation from Leed Markdown, working in a few steps:
- Reserve the pages. An AI tool could create an empty draft and get its page id back right away. Reserving every page in a set first meant each page could link to the others before any of them had content.
- Fill the bodies. A body could be set in full from Leed Markdown while the page was still empty, with internal links written as
pageid:links, optionally to a heading. - Edit safely afterwards. Once a page had content, an AI tool read it back as Leed Markdown with an anchor on every block, then inserted, replaced or deleted blocks by anchor. These edits landed as tracked suggestions attributed to the person who connected the tool, for you to accept or reject in the editor. If a block had changed since the tool read the page, the whole set of edits was rejected so the tool could re-read and try again, so an AI edit never overwrote a change someone had just made.
Content was also checked against the page type’s formatting options. If the markdown used a feature the page type turns off, such as tables or alerts, the write was rejected with a message naming the features that were not allowed. Pages created this way were drafts. Publishing stayed in the CMS.
Release 35 made direct edits the default for AI tools connected over MCP, with tracked suggestions available on request, and allowed replacing the whole body of a page that has never been published. Release 39 renamed several of the MCP tools.
Learn more: Authoring Pages over MCP, What Each Page Type Lets You Format, Suggesting Mode and Tracked Changes.
Fixes
Protected forms can’t be deleted, and now say so
Some forms belong to a Leed service rather than to you, and cannot be deleted. Before this release, the Delete Form button on a protected form could still be clicked, and the delete failed with a confusing permissions error. The button was now disabled on protected forms, with the explanation “Protected — this form cannot be removed.” beneath it. Other forms were unaffected.
Learn more: Building a Form.