Mintlify is opening Autopilot in beta for teams that publish documentation on its platform. The agent works in the background, reading connected GitHub repositories and nearby tools such as Slack, support tickets, project trackers, and feature flags. When code merges, the same support question keeps coming in, or someone flags a mismatch in Slack, it drafts the documentation update and opens a pull request. A teammate still reviews and merges. Nothing publishes until that happens. The launch follows a lag Mintlify measured in its 2026 State of Knowledge Report: 24% of teams get product changes into their docs the same day, and 22% wait a month or longer. Mintlify already offered automations that run a prompt you write when a trigger you configure fires. Autopilot removes that per-workflow setup. Connect sources, turn it on, and it decides what needs an update, with a default pass when code changes and a once-daily quality check. It also checks which automations are already active and avoids repeating that work. Autopilot requires a Pro or Enterprise plan and a Mintlify project on GitHub. It does not support GitLab or other git providers. Pro plans connect GitHub and Slack. Enterprise plans can add a wider set of tools. Each pull request it opens or updates costs 250 credits, and runs that find nothing to change cost nothing. It assigns the pull request to the teammate it identifies as the owner of the changed code, requests their review, and emails them. Merged and closed pull requests are the signal it uses for tone, voice, and how quickly the team usually updates docs. A later release is planned to learn from edits reviewers make before merging and to add a dashboard of what the agent is doing.