Imark is a native Markdown reader for macOS. Double-click a .md file and it opens rendered; comment on a phrase and the note goes into the file itself.

Install: download Imark-0.6.2.dmg, drag Imark to Applications, open it. Installed copies update themselves; brew upgrade imark works too.

What's new

• The copy button is back in Quick Look. Press Space on a .md file and every code block has its copy button again — the preview is where most snippets get copied from, and it used to hide it. The labels now read Copy / Copied / Failed, like the rest of the interface. Contributed by @aislam23 in #25, Imark's first outside pull request — thank you.
• Homebrew no longer warns on install. The cask dropped a parameter Homebrew had deprecated. Reported by @petreq in #23.

Nothing else changed since 0.6.1.

Imark is a native Markdown reader for macOS. Double-click a .md file and it opens rendered; comment on a phrase and the note goes into the file itself.

Install: download Imark-0.6.1.dmg, drag Imark to Applications, open it. Installed copies update themselves; brew upgrade imark works too.

What's new

• A small cup at the end of the toolbar, and Help › Buy Me a Coffee…. Imark is free and stays free; if it saves you time, that is where to buy me a coffee. It steps aside during a review, where only the approve and send-back buttons remain. Nothing else changed since 0.6.0.

Imark is a native Markdown reader for macOS. Install it with brew install --cask migsilva89/imark/imark, or download the disk image below.

What’s new

You can now turn off Show controls for adding comments in Settings when you only want to read. This removes the moving +, block highlights, the Comment selection action, and the Comment on Document toolbar button. Comments already in the file remain visible.

See the Comments guide for details.

A maintenance release. Nothing in the app itself changed — if you are already on 0.5.0, updating gains you nothing you can see, and skipping it costs you nothing either.

What changed is how the release is published. From this version on, each release carries the disk image twice under two names: the plain one, which the website and Homebrew link, and an -update one that only the updater inside the app fetches. They are the same file, byte for byte.

The reason is counting. GitHub reports downloads per file and nothing else, so with a single image there was no way to tell somebody installing Imark for the first time from a copy updating itself — both were one number. Two names, two counters, and no analytics, no server, and nothing that phones home to do it.

Update without leaving Imark

Imark can now download, verify, install, and reopen new versions. Automatic checks remain optional, and nothing is installed until you click Install and Relaunch.

The move from 0.4.0 still opens the download page because that version predates the updater. After installing 0.5.0, later releases can be installed inside Imark.

Comment on the exact item

• Beside a list, the margin button now offers the item under the pointer instead of the whole list.
• Inside a table, point at a cell to comment on that cell.
• A note's dot sits beside the words it quotes, including the correct line of a long paragraph.
• A whole item or cell gets a soft wash instead of an underline.

Notes still stay after the block in the Markdown file, so they never split a list or table.

Open documents from the terminal

The app now includes the imark command. Install it from the Imark menu, or get it automatically when you install with Homebrew. imark notes.md opens the document in the copy of Imark that is already running.

Fixed

The About window no longer shows the meaningless build number (1) after the version.

Imark is a native Markdown reader for macOS: double-click a .md, read it rendered, preview it in Finder with the space bar, and comment on a phrase so the note is written into the file itself.

Download, drag Imark to Applications, open it. macOS 14 or later, 5.8 MB, signed and notarised.

Editing, when you ask for it

The toolbar has a new switch: an eye and a pencil. The eye is the app you already know — nothing on screen offers to change the file. The pencil replaces the page with the document as text, in a plain editor: line numbers, Markdown in colour, a bar in the gutter beside every line that differs from the file on disk, and the system's own find bar. ⌘S writes it, and ⌘E turns the switch.

Reading is still the state it opens in, and still what the app is for. What changed is that fixing a wrong line no longer means leaving.

It will not cost you somebody else's work

While there is anything unsaved, Imark stops following the file — live reload is the reason this app exists and also the one thing that could erase what you typed. The close button carries the edited dot, Revert puts the file back, and closing the window, quitting, or opening another document all ask first.

A save cannot land on top of an edit made elsewhere: it goes through the same check every comment does, and if the file moved since Imark read it, the save is refused and says so. ⌘Z afterwards puts the document back.

Open in… while you edit

The moment a change is bigger than a line, the file goes somewhere built for it — Cursor, VS Code, Zed, Sublime, and Claude and ChatGPT are all in that menu, and it now stays in the toolbar while editing. Imark runs nothing on your machine and asks nothing of your accounts.

Also

• Download in the update notice now opens imarkmd.com instead of a page of release assets.
• Cut and Paste arrived in the Edit menu, and ⌘Z / ⇧⌘Z undo and redo your typing while editing.
• The caret lights the right line in files saved by a Windows editor.

Reported by u/Medical_Time1567 on Reddit, who asked for exactly this. Ideas and bugs: github.com/migsilva89/imark/issues.

The front matter card can be put away

A document that opens with YAML metadata always showed it as a card at the top. Plenty of files carry that for tooling rather than for the person reading, so View › Show Front Matter now hides it, and Imark remembers your choice for the next document.

Equations that run over two lines render

$$ … $$ split across lines came out as raw text while the same equation on one line was fine. The math is now read while the Markdown is read, so the LaTeX reaches KaTeX exactly as written.

An example of the comment format stays an example

A note shown inside a code block — the way this README teaches the format — was counted as a real note, and a review handed it to the agent as if somebody had written it. Both readers now know what a code fence is.

The agent files come with the update

The skill and commands were written once, at setup, and never moved again: anybody who set Imark up months ago was still running those instructions. The first launch of a new version now brings them up to date. A file you edited yourself is left alone, and Imark says so.

The plugin script runs through a linked path

Asking for a review through a path that went through a symlink did nothing at all — no window, no error — and told the agent the review was over. It runs now.

Thanks to u/100is99plus1 on Reddit for the first two.

Imark 0.2.3

If a review ever left your agent waiting for nothing, this is the release that fixes it.

The agent was told, and nobody heard

Pressing Request Changes closed the window and said the review was done, but the agent on the other end kept waiting. It could sit there for four hours.

Every review leaves a small file where Imark and the agent agree on what is being reviewed. A round you walked away from left its file behind, and Imark answered that one instead of the review in front of you. It only happened the second time you reviewed the same document, which is why it took until now to show up.

Imark answers the open review now, and an agent that is interrupted cleans up after itself.

Closing the window asks

Closing a review without pressing anything left the same silent wait. Now the window asks first, and offers Approve, Send Back, or going back to reading.

Request Changes is now Send Back

Request Changes is what GitHub calls it when you review code. This is a document going back to whoever wrote it, with your notes on it. Nothing about how it works has changed.

Updating

The app checks for updates on its own. Or download the image below and drag it across.

Undo could write one document over another. Please update.

Comment on a file, open a different one in the same window, then press ⌘Z: the first file's contents were written over the second, in full and without warning. The undo remembered the text but not which document it belonged to, so it handed it to whatever was on screen.

A second case: comment, edit the same file in another editor, let Imark reload it, then undo. That erased the outside edit. Undo was the only write in the app that did not first check whether the file had changed underneath it.

Undo now puts the text back in the document it was taken from, and refuses when that document has moved on since — with a message rather than silence.

Found by t_var_s on Discord. If you have been commenting across several files in one window, this is worth updating for today.

Updating is drag-and-drop, or brew upgrade --cask imark.

Two fixes to the notes an agent reads back out of your document.

Formatted text is no longer reported as missing. A comment on a phrase in bold, italic, code or a link came back marked as an orphan — as though the words had been edited away — because the note stores the text as you see it while the check searched the raw Markdown. Both sides are now compared the same way. An orphan tells the agent to stop and ask, so this cost a round trip on every formatted line.

The app had the same symptom in one place, for a different reason: a note written under a list item is now anchored to that list instead of being reported as lost.

Notes you have already dealt with stay out of the way. Reading the notes back hands over the ones still asking for something. A note that was acted on remains in the document as the record of what was asked, faded in the margin, and --all produces the whole history. Nothing is ever deleted.

Everything else is unchanged from 0.2.0. Updating is drag-and-drop, or brew upgrade --cask imark if you installed it that way.

Reviews happen on the file itself

When an agent opens a document for review, your notes are now written into the document — as the same <!-- imark --> comments the app has always used — and travel with it. Send the file to anyone and the notes go along. The hidden copy under .imark/reviews/ is gone, and so is a subtle race that could end a review with a stale decision.

When the agent acts on a note it marks it resolved= instead of deleting it: the note stays as the record of what was asked, shown faded in the margin.

The app now notices new versions

Once a day Imark asks GitHub for the latest release number and tells you — once per release — when there is something newer. A version number travels; your documents never do. Turn it off in Settings, or check on demand with Imark → Check for Updates…

Updating is still drag-and-drop: download, drop it over the old one.

If you are on 0.1.0: this is the one update your copy will not tell you about — 0.1.0 predates the check. Grab this DMG once, and from here on the app lets you know.

First release. Native Markdown reader for macOS: double-click a .md file and it opens rendered, reloads while you edit, and previews in the Finder with the space bar. Comment on a phrase and the note goes into the file itself, as an HTML comment — invisible in every other renderer, and it travels with the document.

Requires macOS 14 or later. Signed and notarised, so it opens without a Gatekeeper warning.