Skip to main content
Start Plannotator from your coding agent when you want feedback returned to that agent. Run the plannotator command directly for terminal workflows and automation.

​
Start from your coding agent

Choose your agent for its exact setup and commands: Most command-based agents also provide /plannotator-annotate for a file or URL and /plannotator-last for the latest assistant message. See Agents to choose an agent, editor, or note app.

​
Run it directly

Local files opened for annotation must be 2 MiB or smaller. Eligible text files selected from a folder receive per-file version history just like supported files opened directly. Run command-specific help before scripting a workflow:

​
Common options

plannotator review accepts --git or --gitbutler to force the provider. Pull request review uses a local checkout by default. Use --no-local when you only want the provider diff. plannotator annotate accepts:
  • --markdown to convert HTML input to Markdown instead of rendering it as HTML
  • --no-jina to fetch a URL without Jina Reader
  • --gate to add an approval action
  • --json to emit a structured decision
  • --hook to emit hook-native block or pass JSON
  • --require-approval to make annotations and dismissal exit 1 in a strict --gate --json workflow
  • --result-file <path> to atomically publish the structured result without overwriting an existing file
--require-approval and --result-file work only with direct annotate --gate --json calls. plannotator annotate-last accepts --stdin, --gate, --json, and --hook. Running plannotator with no arguments is reserved for hook input. It expects JSON on standard input and is not the interactive entry point. Last verified against Plannotator OSS v0.25.0 on July 27, 2026. Maintained by the Plannotator project.
Last modified on August 9, 2026