Release 32

Released June 12, 2026.

This release opened Leed up to AI tools. You could connect an assistant such as Claude to your workspace through the new Operator MCP, the in-product assistant learned to manage more of your settings, and your published site could describe itself to AI agents. Alongside that came duplicate detection for uploads, custom code-highlighting languages, read-only API reference pages and a set of fixes to short links, redirects, embeds and settings.

New features

Connect your AI tools to Leed

The Operator MCP let you connect an AI tool you already use, such as Claude, to your own Leed workspace. Through it an assistant could search and read your content, draft pages, and query your forms and page analytics. You sign in through the browser to connect, and every request runs with your own permissions in your own workspace, so an assistant can do no more than you can. At launch it covered reading and drafting only: publishing, deleting, billing and user management were left out.

Learn more: Connecting to the Operator MCP, What the Operator MCP Can and Cannot Do.

The in-product assistant and the Operator MCP gained tools to show what your role allows you to do, including any extra access you hold on particular pages, page types or labels. They could also view and edit labels, view users and edit their profile details (but not their roles), list and create autolinks, and edit individual journey stages. Actions that cannot easily be undone, such as deleting a form, removing an autolink or publishing changes, were limited to the in-product assistant, where they wait for your approval before running. Release 39 also made publishing changes available over MCP, behind a confirmation step.

Learn more: MCP Tools: Analytics and Introspection, MCP Tools: Site Structure, How Leed’s AI Is Guarded.

Short links could now be listed, viewed and created through the API and the AI assistant. The assistant could create a UTM-tagged short link once you approved it, and look up the ones you already have. Short links stay permanent: once created, a link cannot be changed or deleted, so a link you have shared keeps pointing where it did. UTM values are tidied when a link is created, by trimming them, lowercasing them and replacing spaces with hyphens. A custom (vanity) code has to use only lowercase letters, numbers and hyphens, and is refused rather than altered when it does not.

Learn more: Short Links and Attribution.

Let AI agents read your published site

Your published site could now offer its public content to AI agents through two emerging standards, WebMCP and A2A. A visitor using an AI-enabled browser could search your blog and pages and get structured answers instead of scraped text, and external agents could discover what your site offers. Access is read-only, covers published content other than documentation and API pages, and is switched on per site.

Learn more: Site AI Agent.

Find duplicate images before you upload them

From this release, uploading an image checks your existing images for the same file and for pictures that look nearly the same, and shows you any matches. You can reuse an existing image instead of creating a copy, or upload anyway. When you upload from the page editor, picking a match drops that image straight into your page. Videos and other files are checked for an identical copy, so the same video is not uploaded twice. Images already in your library were included in the check.

Learn more: Uploading Images.

Add your own code-highlighting languages

This release let you add syntax highlighting for a language Leed does not ship with. Put a highlight.js language file in your content repository, and the language appears in the code block language picker in the page editor. The file runs isolated from the CMS, and a file that fails to load or takes too long falls back to plain text without disrupting the editor.

Learn more: Code Blocks.

Read-only API pages and lockable page types

Pages in an API page type are generated from an OpenAPI spec, so they became read-only in the CMS: they can’t be edited, revised or deleted there, though they can still be scheduled and published. Separately, an Administrator could now lock any page type so no new pages can be added to it. Together these let you import an API reference or a versioned documentation set, then lock it so it stays in step with its source.

Learn more: API Reference Pages, Configuring a Page Type.

Inline SVG diagrams with svgDiagram

This release added the svgDiagram shortcode, which inlines a hand-built SVG diagram into a template as easily as an image. Because the SVG is inlined and wrapped in a themed container, it follows light and dark mode and stays crisp at any size, which an SVG loaded as an image does not.

{{ svgDiagram "svg/charts/adoption" class="max-w-3xl mx-auto" }}

SVG files live in src/_includes/svg/ and can be organized in subfolders.

Template-built pages in search, analytics and asset tracking

Pages your site builds from templates rather than from the CMS editor, such as list, archive and category pages, became part of site search and AI search, appeared in page analytics, and had the assets they use tracked the same way as pages written in the CMS.

Learn more: Page Analytics in the Editor.

Form submissions record the visitor’s timezone

Form submissions began capturing the visitor’s browser timezone, so lead records and form notification emails show times in each lead’s own local time instead of a company default. A returning lead who submits from a new timezone has it updated. The change reaches your site when it is next deployed.

Learn more: Form Submissions.

Plan changes update your entitlements automatically

From this release, a change to your paid plan updates your workspace’s plan tier and MCP access automatically, instead of needing a manual change. A canceled subscription keeps its plan until the paid period ends, a failed payment does not downgrade you on its own, and the workspace moves to Free only when the subscription expires.

Learn more: Changing Plans and Downgrades.

Fixes

  • A published page could become unreachable through its short link. Short links now resolve reliably, and a missing page address is logged as the real cause instead of being reported as an invalid code. See Short Links and Attribution.
  • Renaming a page’s URL back to one it used before could leave a redirect pointing the page at itself. That redirect is now removed when the page is published. See Aliases and Redirects.

Page types and documentation menus

  • Changing a page type’s Allow recommendations setting now applies to every existing page of that type on the next publish. Before, it only reached pages that were individually published again afterward. See Recommendations.
  • Changing page type settings that do not affect the published site, such as editor formatting options or required fields, no longer marks the page type as needing to be published. See Publish Reminders and the Must-Publish Model.
  • Each documentation or API set now owns its left navigation menu and no longer inherits one from company-wide settings. The company-wide Left Menu option was removed. See Left Navigation Menu.

Settings and embeds

  • Saving company settings, even just the site description, could silently reset your plan and your DKIM email-authentication records to their defaults. Saving now changes only the fields you edited. See General Site Settings.
  • Iframes added in the editor now save cleanly, without stray placeholder text, and render on the published site with their title, sandbox, loading and fullscreen options. See Inserting Media and Embeds and Embeds and Icons.
ESC