Released October 22, 2026.
This release brings Leed to Claude. The Leed plugin for Claude installs the CLI, signs you in and connects your workspace in one command, and its skills can build, migrate, audit and publish a site for you. The leed CLI moves to public npm and gets a new setup command. It also stops guessing which site or environment you mean. Internal page types give your team a place for content your site must never show.
New features
The Leed plugin for Claude
Leed now has a plugin for Claude. It brings the skills Claude needs to work on a Leed site: building templates, managing settings and assets, publishing, and the new skills below. Add the Leed marketplace in Claude Code and install the plugin, or find “Leed” in Claude’s plugin directory and install it in one click.
/plugin marketplace add leed-ai/ai-plugins
/plugin install leed@leedLearn more: Get Started with the Leed Plugin for Claude, The Leed Plugin for Claude: Skills.
Set up everything with /leed:setup
Run /leed:setup in Claude and it checks and installs everything you need: the prerequisites, the Leed CLI, your sign-in, the connection between Claude and your Leed workspace, and your site. Each step is checked before it acts, so on a machine that is already set up it changes nothing, and you can run it again any time. When the plugin and the CLI fall out of step, Leed tells you at the start of a session what to update, and /leed:setup can turn on auto-update for you.
Learn more: Get Started with the Leed Plugin for Claude.
Build your site with Claude
New to Leed? Ask Claude to build your site. The onboarding skill asks about your business and audience, proposes page types, labels and menus, and confirms them with you before it applies anything. It then sets up your header and footer menus and theme, and creates starter templates that follow Leed best practices.
Add a blog or a documentation site at any time with a recipe. Each recipe sets up the page type, menus, search and starter templates in one step, and running it again creates no duplicates.
/leed:create blog
/leed:create documentationOn Growth plans and above, two more recipes add recommendations and dynamic calls to action to your pages. The recommendations recipe includes an offline preview, so you can style the recommendation cards in a local leed site build --serve before you publish.
Learn more: The Leed Plugin for Claude: Skills.
Migrate your docs, or import a Claude Design
Move your documentation to Leed from Docusaurus, MkDocs, GitBook, Mintlify, ReadMe or VitePress. Claude maps your navigation to Leed menus, converts each page to Leed Markdown, uploads your images and turns your old URLs into redirects, so existing links keep working. Anything it cannot map is listed in a migration report, never silently dropped.
Designed your site in Claude Design? Hand it to Claude Code and Leed turns it into your site’s layouts, partials and theme. Any part of the design it cannot map is listed for you.
Learn more: The Leed Plugin for Claude: Skills.
Claude follows Leed best practices, and checks its work
Claude now works from one set of Leed rules for menus, forms, page lists, links, images and theming, so the sites it builds use Leed’s own components and stay consistent and easy to maintain. Ask Claude to audit your site and you get a list of fixes, each tied to the rule it breaks. The audit only proposes changes and never applies them without your go-ahead.
When Claude publishes changes to templates or styles, it now checks them on your staging site first: it compares the affected pages with your live site, looks for console errors and broken links, and shows you the results. It promotes the changes to your live site only when you say yes.
Learn more: The Leed Plugin for Claude: Skills.
Review Claude’s writing in the Leed editor
After Claude writes your pages, it gives you a link to each one in the Leed editor. Read and edit them there, and leave a comment on anything you want changed. Then ask Claude to review the comments, or run /leed:review. Claude reads each whole comment thread and answers it with a tracked suggestion you accept or reject. It never edits a commented page directly and never resolves a comment for you. Where a comment is a question rather than a change request, Claude says so, so you can answer it.
Learn more: The Leed Plugin for Claude: Skills, Comments and Reactions.
Set up continuous documentation with /leed:docs-ci
On Growth plans and above, the plugin can connect your GitHub or GitLab repository to Leed for continuous documentation. /leed:docs-ci creates a trust between your CI and Leed, with no secret stored in your CI. It also adds the release job to your existing pipeline without replacing anything in it, and tells your agent which commit to stamp on a docs edit. The pages then publish with the code they describe. The first job it writes is a dry run, so you can check which pages it would publish before turning it on.
Learn more: Continuous Documentation.
The Leed CLI on public npm
The Leed CLI is now published to public npm as @leed-ai/cli. It installs with no access token and no registry configuration. The leed command and every subcommand are unchanged.
npm i -g @leed-ai/cliIf you already use the CLI, see the action required above.
Learn more: Installing the Leed CLI.
leed setup
Installing Leed is now one short script followed by leed setup. The installer installs the CLI and hands off to leed setup, which signs you in to the Leed environment the installer came from and sets up your site. It never uses a saved login for a different environment. You can re-run leed setup any time, and a site already set up is kept.
Learn more: Get Started with the Leed CLI.
The CLI remembers your sites
The Leed CLI now keeps every site you have set up in one place, ~/.config/leed/sites.json. Commands work from anywhere inside a site’s folder, or from anywhere at all with --site, and moving or renaming a site’s folder no longer breaks anything: the next command you run in it updates the record. leed site list shows every site you have set up, with its environment and folder.
leed site list
leed site build --site leed.aiLearn more: Leed CLI Config and Files.
No more hidden defaults in the CLI
The CLI no longer guesses which site, company or environment you mean. Inside a site checkout, the checkout decides, as before. Outside one, pass --site, or --company and --env. When a command cannot tell what you meant, it stops and tells you exactly what to add, rather than acting on a site you were not thinking of. Listings such as leed site list and leed auth status still work without a target and show the environment on each row.
Learn more: CLI Authentication.
Build a site before you have an account
You can now build and preview a complete Leed site on your own machine, with no Leed account and no sign-in. A sandbox site builds and previews offline, and every system id in it is a readable placeholder. Commands that need Leed say so and point you to the move. When you are ready, Claude moves the sandbox into Leed: it creates the page types, pages, images, labels, menus and forms it needs and replaces each placeholder with the real id.
leed site init --sandbox my-siteLearn more: Sandbox Sites.
Font Awesome Free by default
New sites now include Font Awesome Free. If you have a Font Awesome Pro license, install your own Pro fonts with one command, and Leed supplies the matching styles. Running it again with a newer download upgrades your fonts. Existing sites keep their Pro fonts and build unchanged.
leed site init --font-awesome
leed site init --font-awesome-pro <path to your Pro web zip>Every icon in Leed’s templates can now be changed from your CSS with a --site-icon-* variable, with no template edit.
Learn more: Fonts and Webfonts.
Internal content, and content search in the editor
Create internal page types for content your team needs but your site must never show. Internal pages are organized like documentation and edited in the same editor, but they are never published: you lock a finished revision instead.
The search box at the top of the editor’s left panel now searches page content as well as menu names. Press Enter to search the current section, Site, Documentation or Internal, by Text or by meaning with Semantic search. Each section searches only its own pages, and you only see pages you are allowed to read.
Learn more: Internal Content, Locking and Revising Internal Pages, Searching Content from the Left Panel.
New sites start clean
New Leed workspaces start with a single page type, Root Pages, and a home page that shows how to get started. Blogs and documentation are added when you want them, with the recipes above. New page types now default to the empty.hbs layout, and a page type can only name a layout that exists in your site, so a page type that names a missing layout is refused with a message saying so.
Learn more: Workspace Provisioning, Configuring a Page Type.
Connect an AI client to one workspace
If you manage several Leed workspaces, you can now connect an AI client to a specific one. Add the workspace id to the end of the MCP address, and the consent screen is locked to that workspace. Each project then stays pointed at the right workspace.
https://app.leed.ai/mcp/<companyId>Learn more: Connecting to the Operator MCP.
Improvements
The CLI leaves your site’s AI and editor files alone
The Leed CLI no longer writes AI skills or VS Code files into your site. Get the skills from the Leed plugin for Claude, and run leed site vscode if you want the VS Code workspace. Skill copies written by older versions of the CLI are removed once. leed mcp add --cms now takes --scope user or --scope project, and registers the address bound to your site’s workspace.
Learn more: leed site init.
Create menus from the CLI
You can now create and delete menus from the Leed CLI, as well as edit them. A new menu starts empty and the command prints its id and first revision, ready for the item commands. Creating a menu whose name is already taken is reported, not duplicated, and a menu a documentation set uses as its left navigation cannot be deleted.
leed settings menu create --name "Docs Nav"
leed settings menu delete <menuId>Learn more: CLI Command Reference, Building and Editing a Menu.
Clear reports when Cloudflare blocks a request
Cloudflare occasionally blocks a legitimate request from the CLI or Claude to Leed as suspicious. The CLI now says so plainly, with a request_blocked error, instead of reporting a permissions problem. Your agent can send Leed the details, including the Cloudflare ray id, so the false positive gets fixed: from the CLI with leed feedback blocked, and from Claude with the report_blocked_request tool. The report never carries the blocked content itself, and your agent never changes your content to get past the filter.
leed feedback blocked --ray <id>Learn more: CLI Troubleshooting and Exit Codes, MCP Troubleshooting, MCP Tools: Analytics and Introspection.