Point it at your docs
Open your docs folder of local .md files - product docs, PRDs, release notes, runbooks. No CMS import, no proprietary format, no copy-paste out of a chat window.
From draft to shipped docs - with you in the loop
The agent lives inside the editor, working on your real documentation files. Writing with AI feels like editing a doc and approving changes, not babysitting a chat window.
Direct the agent
Ask Claude Code or Codex to draft a section, tighten wording, reconcile a spec, or update docs to match a change. It works on the real files, right next to your draft.
Review every diff
Each edit lands as an inline diff. Accept the accurate changes, reject the rest - nothing ships until you approve it, and every change is tracked in version history.
AI leverage, editorial control
The shift in doc work isn't writing from scratch - it's directing an agent and reviewing what it produces. FlashType is built for that loop: every change is visible, reviewable, and reversible before it reaches your published docs.
Review, don't trust
AI drafts are fast but not always right. FlashType surfaces every agent edit as a diff so you - the person accountable for the docs - approve or reject each change instead of pasting in unreviewed output.
A real audit trail
Version history powered by Lix tracks every change automatically. See what the agent changed, when, and why - roll back any edit. No untracked rewrites, no silent drift in your specs.
Your files, your format
Docs stay as portable .md in your repo or docs folder. No lock-in, no per-seat fees - FlashType is free and open source, and works alongside the tools your team already uses.
Built for the people who own the docs - technical writers keeping instructions accurate and consistent, and product managers drafting PRDs, specs, and release notes without losing editorial control or a version trail.
More control than copy-pasting into a chatbot
Chatbots and doc-tool AI generate text, but they don't show you a reviewable diff against your real files. FlashType puts the agent where your docs live - and nothing lands until you approve it.
| Capability | FlashType | Chatbot copy-paste | Notion / Docs AI |
|---|---|---|---|
| Works on real local .md files | — | — | |
| Agent reads & edits your actual docs | — | Some | |
| Review each change as an inline diff | — | — | |
| Accept or reject edits one by one | — | — | |
| Automatic version history & audit trail | — | Some | |
| Repo / docs-folder friendly | — | — | |
| No structure lost in copy-paste | — | ||
| Free & open source | — | — |
FAQ
What's the best AI tool for technical documentation?
For docs you have to keep accurate, the key isn't just generation - it's review. FlashType runs Claude Code and Codex directly on your local .md files and shows every change as an inline diff, so technical writers approve or reject each edit instead of pasting in unreviewed AI output.
How can product managers use AI for PRDs and specs without losing control?
Direct an agent to draft or update a spec, then review its edits diff by diff before anything lands. FlashType keeps the work in real .md files with automatic version history (via Lix), so there's always an audit trail and no silent spec drift.
Can I review AI-generated edits to my docs before they're saved?
Yes - that's the core of FlashType. Agent edits appear as inline diffs in your document. Accept the good changes, reject the rest. Nothing is written to your files until you approve it.
Does it work with our existing docs and repo?
FlashType edits plain .md files in any folder, including your docs directory or a Git repo - no migration or proprietary format. It's free, open source under the MIT license, and runs on macOS.
Free & open source
Built in the open. Issues, pull requests and stars welcome.
macOS · MIT license