Mintlify Desktop

the "write offline, sync when you reconnect" plus "agent works alongside you on the page" combination is the part I'd want to pressure test. if I'm offline editing a page locally and the agent (or a teammate) also touched that same section before I reconnect, what happens on sync - do I get a merge view to resolve it, or is it last-write-wins and I just lose whichever version didn't make it? offline-first is great until two edits collide, and that's usually where these tools go quiet.

Having the docs saved locally and being able to work offline is really useful. Especially when the internet decides to disappear

Incredible!We can't live without Mintlify, and this is such a great addition to their product suite.

Hey Product Hunt, Justin here, Engineering Manager at Mintlify 👋We've spent the last few years making documentation easier to create, maintain, and collaborate on. One thing kept becoming obvious as we used Mintlify ourselves: docs had outgrown the browser tab.So we built Mintlify Desktop: an agent-native home for your docs and internal knowledge.What does "agent-native" mean here?Every page is structured Markdown in files you own. Agents can read, search, and update your knowledge as easily as your team can, and there's an agent built right into the app, working next to the page you have open. No copying context into another tool to get help.Why a desktop app?A normal day might involve updating an internal runbook, launching new customer-facing docs, drafting messaging on an upcoming launch, and a pull request changing something else entirely.In the browser, all of that info gets buried between Slack, Linear, Gmail, and fifteen other tabs (or more if it's my browser ). Mintlify Desktop gives all of your documentation a home of its own.What's different from the web editor?You can keep pages open in tabs, and run different projects or Mintlify organizations side by side.Close the app and everything is still there when you come back.Your files also live locally, so you can keep working offline and sync once you reconnect.Is this only for public docs?No. A lot of what teams write never ships publicly: runbooks, onboarding guides, internal processes, notes from the last incident. That knowledge usually ends up scattered across wikis and shared drives, where it's easy for it to go stale.Desktop puts internal knowledge and public docs in the same app, so the pages your team uses to do the work sit right next to the pages your customers read.Is collaboration different?No. Someone can be editing visually in Desktop while someone else works directly in Markdown or from the web.It's the same collaborative workflow, built for people who spend a lot of their day in docs.Why now?Docs are becoming core infrastructure for engineering, product, support, and agents. That's just as true for the internal knowledge your team relies on as it is for your public docs.The web editor made Mintlify accessible to everyone on a team. Desktop is for the people who live in it.We're launching in beta today on Mac, Windows, and Linux. It's still early, and we'd love to hear what you think about its performance, interface, sign-in, or what would make this useful for you.Read more about it on our blog: https://www.mintlify.com/blog/mintlify-desktop