Product updates
A full rundown of our latest releases, improvements and fixes in GitBook
One-click MCP connectors and a redesigned Developer tools screen
Connect your site’s MCP server to an AI client in one click. The redesigned Developer tools screen puts MCP first.
Its tabs are linkable and persist after refresh. MCP also has a direct link in the organization sidebar.
A more capable Content API
The Content API gives you more control when creating and linking pages. Set a page’s slug when you create it, and use temporary refs to link pages before they exist.
The creation response now returns a page’s full content and metadata which supports round-trip workflows.
The new
insert_filesaction adds images through the API. Use a URL or inline base64 content.The API also accepts
.mdand.mdxslugs, relaxes page title requirements, and adds a compatibility flag. The flag protects existing workflows from future changes.
Improvements
Cancel or reactivate your subscription from the billing page. Cancellations take effect after your longest-running billing item ends.
Give a button a select action in the editor. Choose an available slug or enter your own value.
Integration blocks work inside Hint blocks. Add live integration content to a callout.
The Broken URLs report groups every URL variant into one row. This includes query strings, fragments, trailing slashes, and share links. Embed views no longer appear.
Git Sync configuration shows connected repository details. Confirm the repository before you save.
Search indexing is faster and more reliable for very large spaces. This includes pages that previously exhausted the indexer’s memory.
Published sites load less JavaScript up front. The syntax highlighter is split out, and Mermaid diagrams load lazily.
GitHub exports check file sizes before export. Files over GitHub’s 100 MiB limit point to Git LFS.
Bulk email invites are limited to 10 at a time. The dialog guides larger imports and clarifies SSO restrictions.
Crawlers can’t access your site’s ask endpoint. Your crawl budget focuses on your pages.
Visitor tokens revalidate without a redirect. Readers stay on the same page on authenticated sites.
Your docs can now collect feedback from readers and AI agents
When page feedback is enabled, GitBook Assistant can submit it on a reader’s behalf. If a reader seems frustrated or reports a page problem, the Assistant can offer to log their feedback. This keeps feedback from getting lost when the conversation ends.
AI agents browsing your site can submit agent feedback. Published-site MCP servers include a sendFeedback tool for reporting unclear, outdated, or missing content. Agent feedback identifies issues the agent finds while working through your docs.
Both types of feedback appear on in your site’s analytics under page feedback.
This feature is rolling out slowly across GitBook organizations. If you don't see it yet, it isn't enabled for your organization.
Ask questions through your site’s MCP server
Published-site MCP servers (with AI enabled) now also include an askQuestion tool that AI agents can use to ask questions about your documentation and get grounded answers back. It complements the ?ask= query parameter that markdown routes have supported for a while, and supports the same goal property — so agents can tell GitBook what they're ultimately trying to accomplish and get answers tailored to that goal.
Custom instructions for GitBook Assistant
Site admins can now give the AI Assistant custom instructions from Customization → AI Assistant. You can set the Assistant’s tone of voice, and add product-specific knowledge and terminology so that it consistently matches your wider style.
This means you can refine the tone and knowledge of the Assistant — but these instructions will never override the Assistant’s scope boundaries or guardrails.
Improvements
When you use a Slack channel for support, GitBook Assistant now replies directly to the customer with its answer, rather than showing its thinking along the way.
You can now queue messages to send to the Assistant while it’s still answering. Queued messages appear at the bottom of the screen — where you can clear them if you change your mind — and are sent automatically once the Assistant finishes its current reply.
You can now attach any type of file to GitBook Agent — Markdown, Word documents and more — so you can hand it reference material in whatever format you have.
Fixes
Fixed a bug that meant disabled or removed organization members could still be requested as reviewers on a change request.
Fixed an issue that meant you couldn’t comment on the title of an expandable block, only the text inside it.
Change requests with conflicts now explain why the Changes tab is unavailable instead of silently returning to the Overview tab.
Meet the GitBook CLI
The new GitBook CLI (@gitbook/cli) brings your GitBook content and organizations to your terminal.
It wraps the GitBook API as a set of commands, so you can list organizations, inspect spaces and pages, ask questions against your docs, and build and publish integrations — all without leaving the shell.
And it’s built for agentic workflows as much as human ones. Machine-readable --json output and a predictable command structure make it easy for AI coding agents like Claude Code, Codex, and Cursor to run commands, parse the results, and chain them together as part of a larger task.
Install it globally with npm install @gitbook/cli -g, then run gitbook login to get started — or head to the CLI docs for the full guide.
A more powerful page cover system
We’ve added two new options that make page covers a much richer design tool for your docs site.
First, you can now set a page cover to display as a background image behind your content — with control over the color of the text displayed on top. That means your header can act more like a background for the top of your page.
We’ve also added the option to enable a radial mask on your page cover, creating a seamless transition from the header into your content.
Combined with the existing positioning and cover height controls, these options add up to a powerful system for enriching your pages.
Improvements
If you set a tint color that is very light (or very dark in dark mode), we’ll now use it as your site’s background — giving you a nice off-white background instead of the default light gray.
You can now choose the size of buttons and inputs on your docs site. The default (large) stays the same, but you can make them smaller — especially useful if you want to fit more recommended questions on a single row.
When readers navigate between sections on your published site, the table of contents now shows a handy back button so they can jump straight back to the section they were browsing.
Prompt blocks now support an expanded mode, giving your prompts more room on the page.
GitBook Agent will now bias more toward action, and will always be explicit if it’s waiting for user input.
Fixes
Fixed an issue that meant you wouldn’t see any progress when requesting a review from GitBook Agent. You’ll now see its work in the Agent window while it reviews.
Fixed an issue that meant the GitBook Agent button didn’t appear when viewing a change request from the change request list.
Fixed a crash on the change request screen that could happen when a contributor account was deleted, a linked Jira issue couldn’t be loaded, or a page diff failed to render.
Fixed an issue that meant a space’s History list wouldn’t show page or computed content changes.
Viewing an unchanged page in a split diff no longer renders the same content twice — the right-hand column now shows “This page did not change” instead.
Fixed an issue in the change request overview that showed same-page heading links as broken.
Fixed an issue with diff view that meant changes to a nested page didn’t show the page as being edited within a change request.
Fixed an issue where Agent would intend to link to a page but wouldn’t include the URL because it was from a docs site that isn’t publicly visible. Now the Agent explains that it’s not accessible.
File imports with no importable Markdown, HTML or docx files now fail with a clear error message.
Meet the sites-first GitBook
We’ve redesigned the GitBook app around what you actually ship: your docs sites.
You now start at your organization Home, and each site’s content, structure, settings, and tools live together in one sidebar. Content in a site lives in sections — what you knew as spaces, now part of their site — organized into groups when your docs grow. And the new All content screen gives you one place to find everything in your organization, including content that isn’t part of a site yet.
If your organization hasn’t made the switch yet, enable the new experience in the app. Your content, sites, and settings come with you exactly as they are.
Read about what’s changed, or jump into the quickstart to learn more.
Introducing style guides
You can now create a style guide for your docs: a dedicated space for your team’s writing rules that GitBook Agent enforces whenever it writes, edits, or reviews content.
Start from the Starter, Google, or Microsoft template, import a guide you already have, or share one style guide across your sites. When content drifts from your rules, the Agent flags the exact rule it breaks and suggests a ready-to-paste fix. You can also request a full style guide review right from a change request.
Style guides are rolling out gradually in early access. Learn more in the style guide docs.
GitBook Agent: broader context and hidden-page editing
GitBook Agent can now read other spaces and your site’s structure while it works, so its suggestions stay consistent with the rest of your docs. It can also create and edit hidden pages directly, without you needing to unhide them first.
New connections for HubSpot, Front and more
You can now connect Freshdesk, Front, HubSpot, and Zoho Desk as context sources, so GitBook can ingest your completed support tickets alongside your existing docs, and suggest improvements based on customer conversations.
Improvements
Change requests now show reviewers directly in the sidebar and surface linked Jira issue status — so you can track review progress without leaving the page.
You can now create a link with Cmd+K even when no text is selected, making it faster to add a url on the fly
You can now use a carousel layout for card tables, helping you present grouped content in a more compact view.
Page cover backgrounds now support masks, giving you the option to customize how your cover images are cropped and shaped.
You can now open your site directly from the left nav, giving you a faster way to jump straight to the live page.
We’ve optimized Git Sync to handle larger commits without timing out, so bigger changes sync reliably.
You can now skip the onboarding walkthrough, letting you jump directly into your new docs if you’re keen to get moving.
Fixes
Fixed an issue that meant copying a page could drop its sub-pages’ content.
Fixed an issue that showed the wrong diff when updating a change request.
Fixed an issue that meant Git Sync would skip imports when a project directory started with a leading slash.
Fixed an issue that meant relative links and Git-style markdown links didn’t resolve correctly through the content API.
Fixed an issue that could crash the editor when turning content into a link.
Fixed an issue that caused the link palette to hang on sites with many spaces.
Fixed an issue that could leave the GitBook Agent stuck or cause it to lose messages.
Fixed an issue that could leave some users missing site permissions after an update.
Fixed an issue where search results over-favored the current space.
Fixed an issue that allowed deleting a space that was still in use as a styleguide.
Fixed a security issue that could allow server-side request forgery (SSRF) through the OpenAPI spec importer.
Fixed an issue that could prevent the GitBook Agent from correctly checking site access permissions.
Private agent conversations
Agent conversations in change requests can now be marked private, so work-in-progress discussions stay visible only to the people who need to see them.
Team management in site members
You can now manage teams and apply team-level role overrides directly from the site members screen, so access control for a specific site doesn’t require switching to org-level settings.
Git LFS support for Git Sync
Git Sync now supports Git Large File Storage (LFS), so repositories that use LFS for binary assets or large files can sync with GitBook without manual workarounds.
Improvements
You can now select several paragraphs and convert them all into a list at once from the “Turn into…” palette — so restructuring a section into bullets no longer means formatting each line individually.
We’ve streamlined the Git Sync provider connection step, reducing the number of screens you move through when connecting a new provider — so setup is quicker and easier to follow.
When a Git Sync fails, the sync step is now shown in the UI so you can see exactly where the failure occurred.
Pending editor changes are now always saved when you navigate away, so no edits are silently lost when leaving a page.
The GitBook Agent floating panel is now hidden on overlay and modal screens, so it no longer obscures content when you’re in a dialog.
The Ask AI page action is now hidden when page actions are disabled, so the UI stays consistent with your page configuration.
GitBook emails have been updated with refreshed branding.
AI answers no longer wrap internal page links in inline code formatting, so links render correctly and are clickable.
Fixes
Fixed an issue that meant the AI agent panel on the change request screen could get stuck in a loading state.
Fixed a bug that meant the
/changesAPI endpoints were computing diffs against the wrong base revision, causing some changes to appear missing or duplicated.Fixed an issue that meant AI-generated record titles were being incorrectly stripped of formatting, producing malformed output.
Fixed an issue that meant the floating diff navigator showed an incorrect count of changed blocks.
Fixed a bug that meant computed content was not being dereferenced properly, causing stale content to appear in some views.
Fixed an issue that meant OAuth redirect URI matching was too strict, rejecting valid sub-path redirects from verified clients.
Fixed a bug that meant spaces without an active installation were sometimes shown with a success status.
Fixed an issue that meant
.gitwas not being appended correctly to repository URLs during Git Sync operations.Fixed a bug that meant the Ask AI queries CSV export failed to download.
Fixed an issue that meant GitBook agents could not loop correctly across multi-step workflows.
Fixed a bug that meant anchor content references were not resolving correctly in some page configurations.
Fixed an issue that meant the OAuth consent screen displayed a loading skeleton instead of the consent form in some flows.
Faster change request reviews with improved diff navigation
Reviewing a change request with many edits is faster with the new floating diff navigator. You can now skip directly to the next or previous changed section without scrolling through unchanged content, so nothing gets missed in a long review. The change request overview now also supports split-diff view, showing the before and after of each edit side by side.
Toggle it on to compare original and revised text at a glance — useful when reviewing prose-heavy changes where inline highlights alone aren’t enough.
AI-generated change request titles and descriptions
You can now let GitBook name and describe your change request for you. When you open a new CR, the docs agent reads your changes and proposes a title and a short description — so you spend less time on housekeeping and more time on the content itself. You can edit either field before submitting.
Improvements
Admins can now send invitations at both org and site levels from a single dialog, eliminating the need to repeat the invite workflow for each scope.
The OAuth consent screen has been refined so permissions are clearer and easier to confirm when granting access.
Change requests now open directly on the Changes tab by default, putting you in review mode immediately instead of the editor.
The copy URL button always appears next to the page title, so you can grab a link anytime without hovering or opening a menu.
The sidesheet now stays open after you duplicate a page, preserving your context and workflow without losing your place.
Member management and invitations are now handled from the site context, so you can manage access to a specific site without switching to org-level settings.
Findings linked to a site now automatically mark as done when all their associated change requests have been merged, keeping your findings list accurate without manual cleanup.
Agent review status is now visible in the CR reviewers list, so you can see at a glance whether the agent has completed its review.
Fixes
Fixed a bug that meant the agent silently skipped reordered blocks instead of applying them, so content reordering now takes effect correctly.
Fixed a bug that meant an agent was silently removed from a change request when it was explicitly added as a reviewer — agents requested as reviewers now stay assigned.
Fixed a bug that meant inserting a page failed silently when the target location was a computed page.
Fixed a visual bug in the table of contents where a computed group tag was rendered incorrectly.
Fixed an issue that meant toggling draft mode on a single variant section left the UI out of sync with the actual state.
Update change request content via the API
Use the GitBook API to update page content in a change request. You can send content as Markdown or in GitBook document format, including internal page links. Once submitted, your team can review and merge the changes directly in GitBook — making it easy to automate documentation updates from CI/CD pipelines, scripts, or other external tools.
Right now the API supports update_page, with more operations coming soon. Check out our API reference to get started.
GitBook Agent can ask multiple-choice questions in change requests
When GitBook Agent needs a decision while working in a change request, it can now ask you a question with clickable options. You can pick an option or type your own reply.
Improvements
You can now click the page pill in the GitBook Agent panel to remove the current page from its context — so you can ask the Agent things unrelated to the page you’re viewing.
Fixes
Improved table diffs so newly added columns are highlighted clearly and aligned correctly in split view.
Checkboxes inside menus no longer close the menu when toggled, so multi-select is functional.
Opening a change request from the change requests overview no longer crashes with a “Something went wrong” error.
Multiple AI chats per change request
You can now have multiple conversations with GitBook Agent inside a single change request. Create new chats, switch between them from the title dropdown (grouped by recency), and rename or delete them. Each chat keeps its own history and gets an auto-generated title — so you can keep separate threads for different tasks within the same change request.
Mermaid diagrams: fullscreen view and improved controls
Mermaid diagrams can now be opened in a fullscreen view, making large diagrams easier to read and explore with zoom and pan. We’ve also redesigned the diagram controls into a cleaner, more compact toolbar.
OpenAPI: one operation per page
When inserting an OpenAPI spec, you can now split it so each API operation gets its own dedicated page. This gives readers a cleaner, more focused view of each endpoint.
Improvements
You can now paste or drag & drop images and files directly into the GitBook Agent’s input — so you can share screenshots, diagrams, or reference files.
We’ve added on-page search for tables and cards. Large tables and card blocks on your published site now automatically include a search bar, so your readers can filter records to find what they need faster.
You can now export the user questions listed in AI insights to CSV — useful for sharing data with your team or analyzing question patterns outside of GitBook.
You can now reorder page actions — including “Ask assistant” — with drag-and-drop in site customization, instead of relying on a fixed order.
The Assistant now has a tool to open a page directly for your docs visitors during a conversation.
The Agent now shows a live indicator of what it’s currently working on (thinking, searching, reading, editing…), so it’s always clear when it’s active.
The Git Sync entry point is now always visible for space admins, so you can find and set up Git Sync without searching through settings.
When linking a Git-Synced space into a Git-Synced site, you’ll now see a warning across all linking flows to help you catch sync conflicts before they happen.
Fixes
Opening a change request that includes reusable content changes no longer shows a “Something went wrong” error page.
For sites with customized page actions, the PDF download option now stays consistent after a plan upgrade or downgrade.
The AI Agent could get permanently stuck after hitting an internal error — it now recovers and accepts new messages.
When editing a link in a table, the current link is now shown and editable instead of starting empty.
Long link titles in tables now wrap instead of overflowing.
Pages containing legacy full-width blocks now display as wide in the editor, matching how they already appear on the published site.
Inline emoji, icon, and link shortcut insertion no longer duplicates text.
Prevented deleted pages from being viewable outside active diff views.
Prevented moved/renamed pages from appearing as duplicate deleted entries in diff views.
Files attached to the Agent are no longer uploaded until you send the message, and the input is locked while sending.
GitBook Agent can now work with variables
The Agent can now list, create, and update space and page variables, and insert variable references directly into your content — making it easier to maintain consistency across your docs without manual editing.
Improved matching in full-text search
Search results are now more forgiving of typos and partial matches. So if you’re close to what you’re looking for, GitBook will find it — even if you don’t get the spelling exactly right.
Multiple custom merge rules
You can now define multiple custom expression rules in a space’s merge settings, each with its own message that appears when it blocks a merge. So if your team has several conditions that need to be met before content can go live, you can enforce them all in one place.
Improvements
Recent search queries and questions are now saved locally and shown in the Search window and Assistant start screen, so you can easily return to them.
If you’re testing our new and improved interface, you can now toggle the draft property on any section of your site. This means you can work on new content alongside your published docs without it going live until you’re ready — no need to keep it hidden in a separate space or hold it back in a change request.
Fixes
Fixed an issue where the image toolbar showed both “Caption” and “Remove caption” at the same time when an image already had a caption.
Typing “list” in the insert palette now surfaces the more commonly-used ordered and unordered lists before the task list.
Setting a different tag to display in the table of contents now correctly replaces the previous one.
Fixed an issue that meant auto-generated content — such as translations and API references — could show outdated content after a Git sync resync.
Fixed a crash that could occur when viewing the diff of a change request that included a page deleted from the main branch.
Improved Git Sync export and content indexing performance.
Reusable content diffs in change requests
Changes to reusable content now open in a dedicated modal inside the change request diff view. So if you’re reviewing a change request that touches reusable content, you can see exactly what changed before you merge.
Improvements
Stepper blocks can now be inserted inside tabs from the editor.
Library-level changes — files and reusable content — now appear in the diff view within change requests, so you can see the full picture of what’s changed at a glance.
Webhook and Slack “docs updated” alerts now include the user(s) who authored the revision via a new
updatedByfield.You can now remove an applied highlight or text color in one click with the new “No color” option in color pickers.
Version history now shows 25 items, up from 10 — so you have more history to browse when you need it.
We’ve improved the Developer screen in Settings with examples and a “Coming soon” preview for the MCP server.
We’ve reworked the Customization navigation and variant override controls, making it easier to browse settings and manage overrides across variants. We’ve also reorganized MCP settings — ingested MCPs are now under Connections, with a dedicated MCP settings page.
Tags are back in page options.
You can now right-click the “Open” button on a file block to copy the file’s link address — consistent with behavior in PDF exports and published content.
We’ve added URL validation across org logos, site favicons, website imports, Git imports, site context-connections, and integration dev-mode tunnels. Requests to internal, private, and cloud-metadata hosts are now blocked.
Fixes
Fixed an issue that meant pages with a tabs block would scroll sideways.
Fixed an issue that meant redirects with a
+in the source path (e.g./c-c++) were rejected when added manually or imported via CSV.Fixed an issue that meant the
@mention menu would glitch and become impossible to select from during collaborative editing.Customization previews now use current light/dark styling instead of outdated dark mode colors.
Fixed an issue that meant the focus ring was clipped on the “Link title” input.
Fixed an issue that meant links to API reference and computed content pages would break after a GitHub sync.
Fixed an issue that meant the text formatting toolbar didn’t appear correctly when editing inside annotation bodies and popovers.
Fixed an issue that meant using the formatting toolbar while editing inside a dialog (e.g. the table editor) would close the dialog.
Fixed an issue that meant Font Awesome icons were being clipped in the editor.
Fixed an issue that meant comment links in email notifications weren't working correctly.
Fixed an issue that meant identical changes across different change requests or revisions were flagged as merge conflicts.
Fixed an issue that meant pasting from Google Docs would fail to insert images correctly.
Improved GitBook Agent inside the editor
You can now invoke GitBook Agent directly from the editor using a new floating panel — no need to switch to the sidebar. Spot something that needs updating? The Agent handles it inline, right where you’re working.
We’ve also combined the Ask AI and Agent experiences into one. When you select text, the Agent is available right from the format toolbar. And on every change request, the Agent now automatically is added as a reviewer — checking your docs against your existing content with no manual setup needed.
Free users can now try the Agent too, with a soft weekly limit that resets automatically.
Filter update blocks by tag on your published site
If you’re using update blocks with tags to build a changelog, your site visitors can now filter updates by tag. This makes it easy for readers to find the type of update they're looking for — whether that’s new releases, improvements, or fixes.
Improvements
Expandable blocks now support anchor links, so you can link directly to a specific expandable section on your page.
We’ve improved the ‘Target link’ experience in table and card blocks with a new edit dialog and a visit action, making it easier to set and follow links.
Column layout changes now appear in the diff view within change requests, so you can see structural changes at a glance.
Fixes
Fixed an issue where the version history showed a Load more button even when there were no older revisions to load.
Fixed an issue where a space was not refreshed after a Git Sync import.
Fixed a layout shift where page content would jump horizontally when the outline panel appeared or disappeared.
Fixed an issue where requesting an Agent review on a change request wouldn’t notify all assigned users.
Fixed the translate selection menu in the Agent palette.
Fixed an issue where clicking links and mentions inside a change request description didn't work.
Integration blocks inside reusable content
You can now embed integration blocks directly inside reusable content. Content powered by integrations — like embedded diagrams, videos, or third-party widgets — can now be reused across spaces just like any other reusable block.
Improvements
You can now filter AI insights questions by channel type, so you can understand where readers are getting stuck across different sources. This is available for teams with the Ultimate plan.
You can now set a GitHub repository URL as one of your site’s social accounts, appearing in your site’s header and footer alongside other social links.
We’ve improved the speed of merging and updating change requests, especially for larger organizations.
Diff blocks in change requests now have a tinted background and left border, making it easier to scan added, removed, and modified content at a glance.
You’ll notice improved AI translation accuracy — translations should now be more faithful to the original phrasing.
Changes to page options are now shown in the diff view within change requests.
The Mermaid diagram block now uses a clearer, updated icon.
Fixes
Fixed an issue where larger change requests could fail when merging.
Fixed an issue where the URL input showed the preview URL instead of the public URL for your site.
Fixed a bug where removing the last child block inside a parent block would delete the parent block entirely.
Fixed an issue where computed content was not resolving synchronously, which could cause stale or missing content on published pages.
Fixed an issue where headings inside steppers and other custom blocks were downgraded by one level after a Git Sync roundtrip — a Heading 2 now stays a Heading 2.
Fixed sites list cards keyboard navigation.
Diff-style highlighting in code blocks
You can now mark lines in code blocks as added or removed using inline markers. Added lines render with a green highlight and removed lines render with a red highlight on your published page — and the markers themselves are hidden from readers, so your code stays clean.