Skip to main content
Use plannotator annotate to open a Markdown, MDX, text, or HTML file, a web page, or a folder of supported documents.

​
Open a document

When you run the command directly, Plannotator starts a temporary local server, opens the annotation UI, and waits for your response. Send Feedback prints formatted feedback to stdout. Agent skills and commands return the same feedback to the active agent session. Add --gate when the document needs an explicit approval decision:

​
Open a folder

Pass a folder to open the file browser:
The browser lists supported .md, .mdx, .txt, .html, and .htm files. Select a file to annotate it, then move to another file without starting a new Plannotator session. Common generated and dependency directories, including node_modules, dist, and build, are skipped. See Annotate a Folder for file-browser shortcuts, folder feedback, and large-folder limits.

​
Open a web page

Plannotator converts web pages to Markdown before annotation. Jina Reader is used by default for public pages. URLs on localhost or private networks use a direct fetch because Jina cannot reach them. Use direct fetch for any URL with --no-jina:
Direct fetch converts the returned HTML with Turndown. URLs ending in .md or .mdx are read as text when the response is Markdown.
Plannotator imports a web page into its annotation UI. It does not attach notes directly to elements on the live website. The upcoming Plannotator desktop app will support that direct workflow. Until then, use App Notes in the Chrome Web Store, a free local-first extension with public source. The latest GitHub release provides separate Chrome and Firefox packages with checksums.

​
Edit Markdown

The Markdown editor supports two outcomes:
  • For a plan, agent message, URL conversion, or other non-writable source, Plannotator sends your changes to the agent as a unified diff.
  • For an eligible local Markdown, MDX, or text file, save with Cmd/Ctrl+S to replace the file atomically. Plannotator confines the write to the opened source file, checks whether it changed on disk, and asks you to resolve a conflict when needed.
Saved file changes are included with submitted feedback as context so the agent knows they are already applied. Unsaved edits are not written to disk. Local HTML has its own rendered workflow. See Annotate HTML. To change the message returned by supported agent wrappers, see Customize Feedback. Last verified against Plannotator OSS v0.23.1 on July 18, 2026. Maintained by the Plannotator project.
Last modified on July 19, 2026