Blog · ReadMe

A New ReadMe, Built to Work with AI

We're rolling out a new ReadMe, redesigned for writers looking to work more effectively with AI to create documentation that helps developers build with agents.

Justina NguyenMay 7, 2026

Migrating Enterprise Documentation to ReadMe

ReadMe Solutions Architect TeamMay 21, 2026

Product

Reviews and Notifications for Enterprise Branching

Davin HazardMay 14, 2026

Product

Introducing GitHub AI Writer

Ryan VisekMay 7, 2026

changelogMay 15, 2026

Reviews and Notifications for Branching

This release introduces review and notification capabilities for branching, enabling teams to check changes before they go live and stay informed at every step.

Read the release notes

Improvements

Writers can request reviews from the Review tab; teammates receive in-app notifications and automatic linting feedback.
Reviewers can approve changes to enable merging.
Teams are alerted when branches are ready for review, approved, or merged.
Customizable in-app and email notifications with a Weekly Review Digest email.
Centralized Reviews Dashboard showing all branches awaiting review across projects.
Group Admins can mandate zero lint errors, teammate approval, or both before merging (Enterprise).
Restrict merge permissions to Admins Only or Admins and Editors, configurable per project or group-wide (Enterprise).
Vector search improves MCP endpoint results; execute-request supports form data; fetch-guide resolves inline content.
Korean language support added with 386 localized UI strings.

Bugs Eaten by Owlbert

Fixed numerous $ref resolution bugs across allOf, oneOf, and anyOf, including deep self-references, sibling metadata preservation, and dropped properties during polymorphic merging.
Fixed oneOf array examples resetting when the last item was removed, and stopped anyOf from rendering duplicate descriptions.
Fixed YAML uploads incorrectly quoting unquoted ISO date strings.
Fixed HAR generation on multipart/form-data requests and on URL-encoded form submissions through the metrics proxy.
Fixed JSON-format fields being rendered inline instead of stacked when nested, and request example descriptions not being shown.

Customer StoryRisk Management

View all customer stories

"Our goal was a best-in-class developer experience, and ReadMe was the clear winner. Out-of-the-box features with real customer impact, collaborative editing across product teams, and bi-directional sync from the UI meant no other solution checked all the boxes the way ReadMe did."

Socure partnered with ReadMe to drive higher API engagement, lower support costs, and get developers to production faster.

Read Socure's story

Older Posts

A New ReadMe, Built to Work with AI

Migrating Enterprise Documentation to ReadMe

Reviews and Notifications for Enterprise Branching

Introducing GitHub AI Writer

Reviews and Notifications for Branching

Improvements

Bugs Eaten by Owlbert

Socure

Older Posts

What is API Documentation (And How to Write it Well)

The ReadMe CLI Tool

Introducing MDX-ish

Give AI Agents Direct Access to Your API with ReadMe's MCP Server

ReadMe vs. GitBook: Which is the Best API Documentation Tool in 2026?

ReadMe vs Mintlify: How Teams Choose an API Documentation Platform in 2026

Improve Documentation Quality at Scale with ReadMe's Docs Audit

Find & Fix API Documentation Errors with ReadMe's AI Linter

Team Up with AI to Build Docs

Use ReadMe’s AI Tools to Write Great Documentation

Interactive API Documentation: How to Use Custom Components in ReadMe

Review & Approve API Documentation Changes with Branch Reviews

Ship Docs Like Features with Branching

Where Docs-as-Code Goes Next

From IDE to AI: How ReadMe bridges APIs to LLMs with MCP

AI Meets API Docs: The Why Behind /llms.txt