Mintlify Autopilot

So sick!

curious how it handles code that merges but is still behind a flag. docs showing up before the feature does confuses people just as much as stale ones. does it wait for the rollout or open the PR anyway and let the reviewer decide?

As a former customer (I'm now a Mintlify employee ◡̈), this is exactly what I was hoping Mintlify would offer for me. Using it internally has been amazing.

Learning from the PRs a team closes is an interesting detail. Deciding what shouldn't go into the docs is part of learning the team's voice too.

Patrick and Ethan, our knowledge engineer, are doing live webinar next week on Autopilot.It's October 27 at 10am PT.You can RSVP here: https://luma.com/mintlify-0xnx

Hey Product Hunt, Patrick here, Software Engineer at Mintlify 👋Your team ships faster than your docs can keep up. In our 2026 State of Knowledge Report, only 24% of teams got product changes into their docs the same day, and 22% waited a month or longer.And the gap is growing. Agents write more of your code every month, and Claude Code and Cursor merge changes faster than any writer can track them.That gap used to be an annoyance. Today it’s a liability. Your customers read those pages. Increasingly, so do the agents working for them. A stale page means an agent confidently doing the wrong thing.So we built Autopilot.What is it? An always-on agent that keeps your docs in sync with what your team ships. It reads your repos and the context around them: Slack, your project tracker, support tickets, feature flags. When something changes, it drafts the update and opens a PR.A merge changes an API, and it drafts the page. The same support question keeps coming in, and it writes the answer. Someone flags a mismatch in Slack, and it picks up the thread.Does it publish on its own? No. Every change is a PR. It tags the right reviewers and emails them. Nothing ships until your team merges.How is this different from automations? Automations made you the planner. You set up each workflow and maintained its prompt. Autopilot flips that. Connect your sources, click Enable, and it decides what needs to change.How does it learn? Every PR you merge or close is a signal. Autopilot has memory, so it picks up your tone, your voice, and whether your team updates docs every release or the moment something changes. No toggles. No custom prompts. If you want to steer it, just talk to it.Why now? Agents already write a growing share of the code. Docs were the last part of the loop still waiting on a person to notice something changed. Autopilot is the part that notices.Autopilot is in beta today on Pro and Enterprise. Next, it learns from the edits reviewers make before merging, and a dashboard will show everything it’s doing for your docs. Want to see it live? I’m walking through Autopilot and answering questions in a webinar on Tue Oct 27. Register here: https://luma.com/mintlify-0xnx Tell us where it falls short. That’s how it gets better.