An open-source markdown reader for macOS

A markdown reader
with a memory.

Redline renders the markdown on your disk the way you want it rendered. And because it quietly keeps every version it has ever shown you, it can also answer the question an AI rewrite leaves behind — which four paragraphs moved? — word by word, without touching git.

Get it Try it in the browser Beta

Your file is only ever read. Nothing is written next to it, and nothing in it leaves the machine.

An animation of Redline marking a document: a modified paragraph, a modified list, an added line and a removed paragraph, with the change counter and the ruler filling in.
ingest-pipeline.md ~/Projects/atlas/docs

Ingest pipeline

changed

Atlas takes in about 40 60 million events a day from the mobile clients and the edge workers. This document is the design of the path an event takes between arriving and being queryable. accept and queryable, and the back pressure that keeps it there.

Goals

changed
  • Never drop a well-formed event. A backlog is recoverable; a gap is not.
  • Bound the tail. p99 from accept to queryable under 90 60 seconds.
added
  • Keep the operational surface small enough for one on-call engineer.
removed

An earlier draft promised exactly-once delivery from the edge to the warehouse.

Stages

An event passes through four stages. Each one is idempotent and keyed on the event id, so a replay of any prefix is safe.

A reader first.

GitHub-style rendering, syntax highlighting, tables, task lists and > [!NOTE] alerts. Light and dark follow your system theme, or whichever you pin. Open a file and it stays open — your place in it is kept across reloads, across quits, and across the document being rewritten under you.

Rendered or raw, one key apart

r swaps the prose for the markdown that made it: highlighted, line-numbered, and marked line by line rather than block by block.

Your place survives the swap, because the thing being kept is the line of the file you were on and not the pixel you had scrolled to — which is a different part of the document once the same text is set as prose.

A demonstration: the same passage shown as rendered prose and as highlighted markdown source, with the changed line struck through above the line that replaced it.

back-pressure.md

Back pressure

changed

When the queue holds more than 90 60 seconds of work, the accept endpoint answers 429 with a Retry-After.

Shedding at the edge is cheaper than shedding at the warehouse, and a client that is told to wait will.

Light or dark, diagrams included

mermaid fences render in the page; plantuml fences render to inline SVG locally, never over the network. Both follow the theme, and both are redrawn when you change it rather than left in the colours of the theme you left.

A demonstration: a document with a flowchart in it, redrawn as the theme is switched between light and dark.

stages.md

Stages

An event passes through three stages. Each one is idempotent and keyed on the event id, so a replay of any prefix is safe.

Two sidebars, one down each side

The files you have open and every version of this one on the left (⌘B); the document's own headings on the right (⌥⌘B), with the one you are reading under marked as you scroll.

Live reload that keeps your scroll

An editor on one side, Redline on the other, in step. Nothing on the bar says so, because that is the normal state; a red dot appears only if the watch drops.

Links to the file next door work

./api.md, ../adr/0004.md, resolved against the directory your document came out of. Hover one and its destination appears written the way its author would recognise it.

Tabs and no chrome

Several files in one window, one watcher each, each named over its directory so two README.mds are told apart. The window has no OS title bar.

Review mode: the diff is in the prose, not beside it.

No two-column wall to read twice. A changed paragraph gets a thin bar in the left margin, and inside it only the words that actually moved are struck through and tinted — everything else keeps its normal colour, so the document still reads as a document.

Word by word, in place

The word diff runs over rendered HTML rather than markdown source, so marking up an edit never cuts through an emphasis run, a link destination or a fence.

Check a change off as you read it

Click the word in the margin that names it, or press c, and the mark goes — it stops being counted, and n / p walk past it. A heavily edited file is worked down to nothing left.

Every change on the scrollbar

The same three colours down the right edge, at the scale of the whole file. The margin speaks for the screen you are on; the ruler says whereabouts — edited throughout, or three paragraphs near the end.

A demonstration of walking a file's changes: each press of n scrolls to the next marked block and lights its mark on the ruler, and each press of c puts one away and drops the count on the bar.
ingest-pipeline.md +1 ~2 −1

Ingest pipeline

changed ✓ checked

Atlas takes in about 40 60 million events a day from the mobile clients and the edge workers.

This document is the design of the path an event takes between accept and queryable, and the back pressure that keeps it there. Nothing here is specific to a warehouse vendor.

Goals

changed ✓ checked

Bound the tail: p99 from accept to queryable under 90 60 seconds, measured at the warehouse rather than at the queue.

Never drop a well-formed event. A backlog is recoverable; a gap is not, because nothing downstream can tell a gap from a quiet hour.

added ✓ checked

Keep the operational surface small enough for one on-call engineer to hold in their head at three in the morning.

Non-goals

removed ✓ checked

An earlier draft promised exactly-once delivery from the edge all the way to the warehouse.

At-least-once with an idempotent write is the same thing from the reader's side and a tenth of the machinery.

change 1 of 4
+1 ~2 −1 on the bar is what is still outstanding, not what the edit was. Work the file down and it reaches nothing left.

You choose what since means

Since you last read it, since HEAD, or since any version in the list. m moves the read mark; d puts the marks away for a clean read and forgets nothing while they are gone.

Every version is in a list, and a tracked file arrives with its git history already in it — up to 50 commits, read with --follow so a rename does not end the trail. A row is named by its commit subject, or by the clock time it was saved.

  • Snapshots the file itself — no commits, nothing written beside it
  • Two windows on one file share a watcher and a history
  • A checked-off change survives the document moving around it

A demonstration of choosing a baseline: picking an older version from the history list widens what counts as changed, and the count on the bar grows with it.

ingest-pipeline.md +1 ~1 −0

Compare against

Goals

changed

Bound the tail: p99 from accept to queryable under 90 60 seconds.

changed

Never drop a well-formed event. A backlog is recoverable; a gap is not, because nothing downstream can tell one from a quiet hour.

added

Keep the operational surface small enough for one on-call engineer.

removed

An earlier draft promised exactly-once delivery to the warehouse.

Get it.

One app, and nothing else to install — or nothing at all, in a browser.

With Homebrew

Upgrades come with brew upgrade.

The cask fetches the same signed and notarized .dmg as the button beside it.

Or download it

macOS 11+ · Apple silicon and Intel in one app

Download Redline 0.9.0

Drag it to Applications. Signed and notarized, so it opens on the first double-click — no Gatekeeper detour.

Or open it in a browser Beta

Nothing to install · one file at a time, no git

Open the web app

The same reader and the same history, kept in your browser. It reads the file you give it and never writes to it.