Skip to content
The Docs Report
Tuesday, November 17, 2026NewsletterRSS

ReadMe's Slack AI Writer Drafts Docs Changes When You Mention It

ReadMe's Oct. 23 changelog adds a beta Slack AI Writer that turns a thread mention into a docs branch, plus Teams alerts and invite expiry.

2 min read

ReadMeSlackAI

Isometric 3D illustration of glossy hot pink speech bubbles on a tiled floor

ReadMe now drafts documentation changes from Slack: mention @ReadMe in a thread where a team is discussing a change, and the AI Writer puts the update on a new branch for review before anything goes live, ReadMe said in its Oct. 23 changelog. The feature is in beta. Admins connect a workspace from Settings > Integrations > Slack, on Pro plans and above.

Admins choose where the writer works

ReadMe said the Slack page lets admins pick which projects the AI Writer operates in and whether it can merge or delete branches. Enterprise groups manage the same settings from Integrations in the Enterprise dashboard. GitHub and Slack now each have their own page under Settings > Integrations, where each person can also connect their own Slack account for personal notifications.

Merging a branch now deletes it by default

ReadMe changed the editor so that merging a branch deletes it unless the merger opts out. The merge dialog remembers the choice. Deleted branches can be restored for up to 7 days. Every list item, including nested ones, also gets its own block menu handle for dragging, copying or deleting a single item.

Other changes in the release

ReadMe said an agent calling an API through MCP now files feedback on its own when a failure contradicts the API reference. Invites for teammates and end users can be set to expire after 30, 60 or 90 days, or never, with 30 days as the default. Admins approving a teammate access request can pick the Viewer, Editor or Admin role. Translated pages keep the anchors from their source headings. A link such as #prerequisites works in every language.

The Theme Editor gains an Angled table of contents style next to Line and Dots. Changelog posts can use Reusable Content and custom components, which also render in the changelog list and RSS feed.

Key takeaways

  • Mentioning @ReadMe in a Slack thread creates a docs branch for review (beta, Pro plans and above).
  • Admins control which projects the writer touches and whether it can merge or delete branches.
  • Merged branches are now deleted by default and can be restored for 7 days.
  • Invites can expire after 30, 60 or 90 days.

The take

We think the useful part is that the draft lands on a branch. Doc changes often start as a chat message. A tool that turns the thread into a reviewable branch removes the copy-and-paste step where the change usually dies.

The merge permission deserves a decision. A writer that can only open branches is a suggestion engine. A writer that can merge is a publisher. We’d start with branches only. A person reading the diff is the check that catches a confident but wrong paragraph.

The delete-on-merge default needs a check too. A 7-day restore window is short for a team that merges often and audits rarely. Tell the team the window exists before the first branch disappears.