Website · User guide · Privacy and local data · Limitations · For agents
Markover is a macOS app for reviewing Markdown as a document tree and returning block-level feedback to an agent. Instead of quoting fragments back into chat, feedback stays attached to the blocks it concerns, and the agent retrieves the whole review in a single structured handoff.
Markover is in early preview. It is free and MIT-licensed, requires no account, and keeps ordinary review data in your macOS account.
- 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.
Ask your agent to open a Markdown document in Markover (the command it needs is below), review the document, then tell the agent "Check Markover." To review a document without an agent, choose File → Open Markdown… in the app. The user guide covers the full workflow and keyboard controls.
- 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.
- Data formats from unreleased prototype builds may change without migration support. 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.
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 public npm package named markover is unrelated to this project. Use the
exact GitHub release-package URL above.
The command downloads the Apple Silicon app on first use. Native Intel releases
are deferred; see issue #80.
The launcher verifies the download's checksum, bundle identity, version,
architecture, minimum macOS version, ad-hoc signature, and code seal before
caching it. Later commands reuse that validated version. The launcher returns
a review ID, a status, and a markover:// URL that macOS can open, 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'
Some chat apps, including T3 Code and the Codex app, do not currently open custom-scheme links from Markdown. Then stop. See the dedicated agent workflow for retrieval, reopening, and interpretation guidance.
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.
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.
- Contributing
- Roadmap
- Security policy
- Code of conduct
- Discussions for early ideas, usage questions, and general support
- Report a problem with the smallest sanitized reproduction
