Website · User guide · Privacy and local data · Limitations · For agents

Markover is an Early macOS preview for reviewing Markdown as a document tree and returning block-level feedback to an agent.

Features

• Navigable, collapsible blocks for YAML frontmatter, headings, paragraphs, lists, tasks, code, tables, block quotes, and thematic breaks.
• Markdown feedback and labeled screenshot attachments on individual blocks.
• A document browser with inbox and project views.
• Autosave and automatic restart recovery.
• Exact source-edit proposals shown as word-level diffs without changing the original review target.
• One-shot agent handoff containing the exact source, checksum, document tree, annotations, attachments, and review context.

Before you try the early preview

• Markover supports macOS 14 Sonoma or newer on Apple Silicon Macs. Native Intel releases are deferred to issue #80.
• The launcher requires Node.js 22.13.0 or newer.
• Downloads are hardened and ad-hoc signed, but not Apple-verified or notarized. macOS is expected to block the first launch.
• Ordinary review work stays in your macOS account. Markover has no telemetry, analytics, cloud sync, or automatic review upload.
• Unreleased prototype formats may change directly. Released review schemas are converted automatically with an original backup; unknown future versions remain untouched until a compatible Markover release opens them. Back up important review data before changing versions.

Read Privacy, storage, and recovery for local-data and cleanup consequences, and Markdown support and preview limitations before relying on extension-specific rendering. Ask usage questions in GitHub Discussions.

For agents: open a review without installing

Open a document with:

npx --yes \
  --package=https://github.com/lastobelus/markover/releases/latest/download/markover-cli.tgz \
  markover open ./DOCUMENT.md \
  --summary "Explain why this document exists and what feedback would help."

The command downloads the Apple Silicon app on first use. Native Intel releases are deferred to the Broad announcement roadmap in issue #80. Release launchers produced from the hardened preflight verify its checksum, bundle identity, version, architecture, Sonoma floor, ad-hoc signature, and code seal before moving it into the cache. Later commands reuse that validated version. The launcher returns a review ID, status, and OS-openable custom URL, then exits without waiting for the review:

{"reviewId":"mko_8f3a2c","status":"editing","reviewUrl":"markover://review/mko_8f3a2c"}

If you are an agent, retain the returned reviewId, present a best-effort [Open in Markover](markover://review/mko_8f3a2c) (mko_8f3a2c) link, and also put the reliable Terminal fallback on its own line:

open 'markover://review/mko_8f3a2c'

Custom-scheme Markdown links depend on the thread-host; T3 Code and the Codex app do not currently dispatch them. Then stop. See the dedicated agent workflow for retrieval, reopening, and interpretation guidance.

Opening Markover on macOS

Markover downloads are not Apple-verified. They use hardened ad-hoc signing to make code changes detectable, but they do not have an authenticated Developer ID publisher and are not notarized. Gatekeeper is therefore expected to block the first launch.

After a blocked launch, open System Settings → Privacy & Security, find the message about Markover under Security, choose Open Anyway, and confirm Open. If you downloaded the app manually, you can instead Control-click Markover.app in Finder and choose Open, then Open again. Apply an override only to a Markover archive whose SHA-256 checksum you obtained from the same GitHub Release. Do not recursively remove quarantine attributes.

See GitHub Releases for each release's checksums, provenance, trust status, and rollback information.

See the user guide for the complete review workflow and keyboard controls, read Privacy, storage, and recovery for Markover's storage, network, and macOS-account boundary.

Contributing

Contributor and implementation documentation is kept separately from the user guide. Start with the developer documentation for checkout setup, architecture, security mechanics, tests, packaging, and release operations.

Community

• Contributing
• Roadmap
• Security policy
• Code of conduct
• Discussions for early ideas, usage questions, and general support
• Report a problem with the smallest sanitized reproduction of a defect