Released September 16, 2026.
This release introduced Leed’s new contact-based pricing and a refreshed look, and reworked how documentation sets are built and read. Docs URLs now follow your sidebar folders, readers on paid plans get AI-powered search, and edits from AI tools appear live in the editor next to your own. It also added GitHub sign-in, a machine-readable mode for every leed CLI command, and a way to publish content from your own CI when you ship a code release.
New features
Sign in with GitHub
You could now sign in to Leed with your GitHub account, alongside the existing options. GitHub sign-in is for existing Leed accounts only and never creates a new one. It matches your Leed account against any email address that is verified on your GitHub account, not just your primary one, and unverified addresses are never used. When the automatic match cannot decide, you can connect GitHub from your profile settings instead. Each GitHub account links to exactly one Leed login.
Learn more: Signing in, Sessions, connected accounts and API tokens.
New plans, metered on contacts
Leed moved to four plans: Free, Starter, Growth and Enterprise. Free includes unlimited users, unlimited pages and a custom domain, and captures up to 250 leads at no cost. The paid plans unlock lead nurturing, marketing email, the full per-reader funnel and advanced analytics. Plans are metered on contacts rather than traffic, and capturing a contact is never blocked: contacts above your plan’s limit are kept, but locked until you upgrade. Your plan and live usage meters are shown in Settings.
The release also gave Leed its new look: a refreshed logo and a pink brand color across the app, sign-in and emails.
Learn more: Plans and tiers, Usage and limits.
Live collaboration with AI tools
Collaborative editing moved to a sync service that the server controls. Edits made by the Operator MCP, or any other server-side tool, now appear instantly in every open editor with a live shared cursor. Simultaneous edits from people and tools merge safely instead of overwriting each other, and remote edits no longer make images and videos flicker or reload in the editor.
Learn more: Autosave, collaboration and locking.
Documentation URLs follow your sidebar folders
Documentation pages now publish at URLs that mirror the folder structure of your sidebar menu, such as /docs/configuration/linux/. Moving a page to another folder, or renaming a folder, updates the affected URLs and adds redirects from the old ones, so existing links keep working. Existing docs pages kept their current URLs until they were next moved or renamed.
Learn more: Folders set your URLs, Aliases and redirects.
Documentation menus ready to go, and new pages from the menu
Creating a documentation or API page type now creates its navigation menu automatically, so a new documentation set starts with a sidebar. In that menu, and in any folder in it, adding a page now offers to create a new page as well as link an existing one. Creating one opens the new-page flow with the documentation set’s page type already filled in, and places the page where you chose in the menu.
Learn more: Creating a documentation set, Building and editing a menu.
AI-powered search for documentation sites
Documentation sites on Starter and above now use AI-powered search. Readers get relevant results even when their wording does not match the page, can narrow results to one part of the docs, and see where each result sits in the docs. Sites also load faster, because the prebuilt search index is no longer downloaded.
Learn more: Live documentation search.
Dynamic CTAs update live
Dynamic CTAs now change on your live site the moment you save them, with no republish needed. Page recommendations also load without the site shipping a pre-rendered fragment for every page.
Learn more: Dynamic CTAs, Recommendations.
Clearer drag and drop in the menu editor
The menu editor now shows exactly where a dragged item will land, highlights a folder when you are dropping into it, and lets you drag items back out of a folder to the top level.
Learn more: Building and editing a menu.
Filter the documentation sidebar
Documentation sidebars now have a filter box that narrows the navigation as you type, so readers can jump straight to a page without scrolling the whole menu. Matches inside collapsed sections are shown without expanding anything, and clearing the box restores the menu as it was.
Machine-readable output from the CLI
Every leed CLI command now accepts --json, which returns one structured, schema-validated JSON document instead of formatted terminal output, so AI agents and scripts can drive the CLI reliably. The new leed schema --json command describes the full command set, including the exact response shape of each command.
leed site list --json
leed schema --jsonRelease 39 turned leed schema --json into a compact index and added leed schema <command> for one command’s full description.
Learn more: Machine-readable output.
Drag files into Leed, and crop images before upload
You can now drag images and files from your desktop anywhere into Leed to add them to your asset library. Images can be cropped before they upload, and dropping an image onto a spot in the page editor both adds it to the library and places it there.
Learn more: Global drag and drop.
Your own theme, code theme and font names
In Settings, the color theme, code theme and font fields now offer a custom option where you type a name, either per page type or as the company-wide default. That lets you select custom styles defined in your site repository directly from the CMS. The matching CSS has to exist in your site repository. Available on Starter and above.
Learn more: Themes, fonts and code themes.
Publish content from your CI by source commit
Pages can now carry a source commit id: the commit in your own repository that the content was written against. A new API endpoint schedules every page that carries any of a list of commit ids to publish together, so a content release can be triggered from your own pipeline when you cut a code release. A dry run shows exactly what would be scheduled without changing anything, and is available on every plan; scheduling for real requires the Growth plan.
Your pipeline authenticates with an OIDC trust, which you register, view and revoke in the CMS, instead of a stored Leed secret. Release 37 added leed settings oidctrust for managing these trusts from the CLI.
Learn more: Scheduling and automatic publishing, Front matter reference.
Fixes
Publishing
- Deleting a page generated by your site build, rather than managed in the CMS, could stall publishing for every site. Publishing now skips a page it cannot resolve and carries on with the rest.
Editing and settings
- Invisible leftover highlight marks from an earlier content migration could make text appear highlighted on published pages. Those highlights are now visible in the editor, so you can review or remove them.
- Settings changes now save reliably as you type. Before, some edits were saved only when you clicked away from the field.
- Renaming a menu and then toggling its Expanded option no longer discards the new name.
CLI
- When
leed auth reset,leed auth rotateorleed site validate --resetrefuses to run unattended, the message now says whether there was no terminal orCIwas set totrue. Before, a developer at a real terminal withCIexported was told there was no terminal.
Improvements
Faster site builds
Site builds are substantially faster, particularly on large sites.