Released October 9, 2026.
This release made menus and page review practical for AI agents and the leed CLI. Menus can now be changed one item at a time instead of being resent whole, and an agent can read the comments and suggestions on a page and answer them with tracked suggestions. Documentation and API page types can also be created around a menu you already have.
New features
Edit menus one item at a time
Changing one label in a menu used to mean sending the entire menu back, and anything the caller failed to include was deleted. For large documentation menus, edited most often by AI agents, that was slow and easy to get wrong. Menus are now edited through small operations that each address one item by its id: change an item’s fields, add an item under a parent at a position, remove an item, move an item to a new parent and position, or reorder one parent’s children.
The same operations are available from the leed CLI under leed settings menu, and to AI agents as MCP tools such as add_menu_item, move_menu_item, remove_menu_item and set_menu_item_fields.
| Command | What it does |
|---|---|
leed settings menu list | List menus |
leed settings menu get | Show a menu, with its item ids and revision |
leed settings menu set | Change one item’s fields |
leed settings menu add | Add an item, or a whole subtree from a file |
leed settings menu remove | Remove an item |
leed settings menu move | Move an item to a new parent and position |
leed settings menu reorder | Reorder one parent’s children |
leed settings menu set-menu | Change the menu’s own name, description or expanded setting |
Every change requires the menu revision you last read, passed as --base-revision. If someone else changed the menu in the meantime, the change is refused instead of overwriting theirs. When you remove an item that has children, you choose whether they move up into its place (--children promote) or are removed with it (--children cascade). Each change is checked against the rules for documentation menus before it is saved, so an edit cannot leave a docs page out of its set’s menu.
leed settings menu get <menuId>
leed settings menu set <menuId> <menuItemId> --name "Getting started" --base-revision <revision>The Menu Editor in the CMS now saves each change the same way.
Learn more: Building and Editing a Menu, MCP Tools: Site Structure, CLI Command Reference.
Let an AI agent answer comments on a page
An AI agent can now read the review state of a page in one call: every open comment, with its full conversation, and every pending suggestion, grouped by the block of the page they sit on. Each block comes with its current content and everything the agent needs to write an answer, so it can respond to a comment by proposing a tracked suggestion for you to accept or reject. The agent cannot resolve a comment or a suggestion; that stays with you.
Agents use the get_page_review_state tool over MCP, and the same information is available from the CLI:
leed page review <pageId> --json
leed page review <pageId> --status all --jsonBy default only open comments are returned, and emoji reactions are left out.
Two related changes protect your review work. Replacing the whole body of a never-published page is now refused while the page has unresolved comments, so a reviewer’s comments cannot be lost to an overwrite. And when a block already carries someone’s pending suggestion, an agent can now add its own proposal before or after that block, while still being blocked from replacing or deleting it.
Learn more: Comments and Reactions, MCP Tools: Pages and Content, Authoring Pages Over MCP.
Improvements
Create a docs or API page type around an existing menu
When you create a documentation or API page type, you can now name an existing menu as its left navigation instead of having a new one created for it. The menu must belong to your company, must not already be the navigation of another set, and must pass the rules for documentation menus.
leed site create-page-type was removed, because leed settings pagetype create already did the same job with every page type field. The new route also fixes a problem where creating a page type with the old command left a change in a protected file, so leed site validate refused the checkout after an otherwise successful import. When you import an OpenAPI spec, an explicit --page-type-path now takes priority over any local page type entry.
leed settings pagetype create --type api --name "Payments API" --slug payments-apiLearn more: Creating a Documentation Set, Configuring a Page Type, Importing an OpenAPI Spec.