Skip to content

Releases: Ishan-Nim/plume

Plume v1.2.0

Choose a tag to compare

@github-actions github-actions released this 08 Oct 12:07

Plume is a feather-light Markdown viewer. Double-click a .md file and it opens straight into a clean reading view: no workspace to import, no project to set up, no editor chrome.

1.2.0 adds live preview, and a button for opening a folder of notes.

Live preview. Click a paragraph and it becomes the Markdown it was
written as, right where it sits — the stars around bold, the brackets
around a link — while the rest of the page stays rendered, so nothing moves
under you. Click somewhere else and it is a paragraph again. A list, a table
or a code block opens whole, as the one thing it is; diagrams, maths blocks
and images stay rendered, so a stray click cannot replace a diagram with its
source. Arrow keys carry on into the next block, and clicking past the end of
the document starts a new paragraph there. Editing a block replaces that
block's own lines and passes the rest of the file through exactly as it was.
It is on by default — Reading settings → Live preview turns it off — and
Ctrl+E still shows the whole file as plain text when that is what you want.

Open folder sits beside Open file on the welcome screen, and in
⋯ → Open folder… once a document is open. Pick a folder of notes and the
sidebar roots itself there and stays there; opening a note inside it reveals
the file in the tree rather than re-rooting on the note's own folder. Plume
remembers the folder, so it is waiting the next time you open the app.
Close folder lets it go.

Typing one way no longer loses the other. Live preview and the whole-file
editor write into the same text, so Ctrl+E in the middle of a sentence
keeps it, the reading view shows your unsaved edits rather than the last
saved version, and Esc goes back to reading without throwing anything away.
Re-reading the file from disk (F5) now asks first instead of discarding
unsaved work.

1.2.0 prepares for the repository moving to its own organisation. The updater accepted release downloads from one repository path, baked in at build time. Plume is moving to github.com/Plume-MD, and after that move GitHub answers an older copy of Plume with URLs under the new name — which that copy would have refused, stopping its own updates for good. This release accepts both, so the move costs nobody an update. If you are on 1.1.0 or earlier, take this one before the move.

1.1.0 adds Git sync, and four colour palettes.

Git sync keeps a folder of notes in a Git repository: pull what changed elsewhere, commit what changed here, push. It is in ⋯ → Git sync…, and it is part of having a Plume Vault account. Plume never asks for a token and never stores one — it drives the Git already on your machine, so your credentials stay in your credential helper or SSH agent, and conflicts, submodules, LFS and signing behave exactly as they do in your terminal.

Starless, Greenwood, Commit and Lapis sit beside Plume's own under Reading settings → Palette. A palette recolours whichever of light or dark is in force rather than replacing that choice.

1.0.3 added four colour palettes. Starless, Greenwood, Commit and Lapis sit beside Plume's own under Reading settings → Palette. A palette recolours whichever of light or dark is in force rather than replacing that choice, so Auto still follows the system inside every one of them. The same five are on the website and the web app, in the footer. They are derived from four MIT-licensed Obsidian community themes, credited in the README.

1.0.2 fixed the updater, which could not install an update. "Install and restart" started the install and a second download at the same time, and the second one deleted the installer the first had just handed to Windows. Nothing was installed, Plume reopened on the old version, and offered the same update again — a loop with no way out of it.

If you are on 1.0.0 or 1.0.1, updating from inside Plume will not work, because the broken updater is the one you are running. Download 1.0.2 below or from plume-md.com/download and run it over the top — your files and settings are untouched. Updating from inside Plume works again from 1.0.2 onward.

1.0.1 fixed folder sync on a large notebook. Syncing stopped partway through and reported a number of failures with no reason. The vault asks a caller to slow down after six hundred requests a minute, and a thousand documents sent as fast as the network allows tripped that a few hundred in — everything after it failed. Sync now paces itself and waits when asked, plans against the 100 MB quota before it starts, and says why when a document is left out. The list of skipped files is also bounded, so pointing it at a folder full of things it will never send no longer costs memory on every rescan.

What it does

Opens the file you clicked

Plume registers itself for .md, .markdown, .mdown, .mkd, .mkdn, .mdwn, .mdtxt and .mdtext. A second file opens in a new window of the already-running app, so there is no cold start. Make it the default for .md once and every note opens in a calm, distraction-free window.

Reads Obsidian notes properly

[[wiki links]], ![[embeds]] and section transclusion, callouts including the foldable > [!warning]- kind, ==highlights==, #tags, %%comments%%, block ids and front-matter Properties — rendered the way Obsidian renders them, and resolved across the whole vault. For a note that really is inside an Obsidian vault, ⋯ → Open in Obsidian hands it over.

Everything GitHub-flavoured works too: tables, task lists, footnotes, definition lists, emoji shortcodes, syntax highlighting, KaTeX maths and Mermaid diagrams.

Edits where you click

Click a paragraph and it becomes the Markdown it was written as, right where it sits; move away and it is a paragraph again. For the whole file as plain text, press the pencil or Ctrl+E. Ctrl+S saves. Esc goes back to reading.

Both write into the same text, so moving between them loses nothing. The rules Plume keeps:

  • Nothing is written until you ask. Typing changes nothing on disk.
  • An unsaved change is never thrown away silently. A dot marks it, and leaving asks first.
  • A file changed elsewhere cannot overwrite your unsaved work. Plume tells you, and you choose.
  • Tab indents, Shift+Tab outdents, Enter continues a list.

Ctrl+Shift+E hands the file to VS Code, Cursor or your system editor.

Keeps a folder in sync, if you want

Create a free account and you get a 100 MB vault. There is no card, no trial and no paid tier.

Choose one folder and Plume keeps everything in it — notes, images and sub-folders — in your vault by itself while you are signed in. It watches the folder while Plume is open and checks again every few minutes, so edits made in any editor go up on their own. Your folder stays exactly where it is; nothing is moved or renamed.

  • Only documents and images are ever uploaded. Markdown, text, CSV, JSON, YAML, and PNG, JPEG, GIF, WebP and AVIF. Programs, installers and archives are refused by an allow-list and stay on your computer.
  • Folders are kept. Projects/Plume.md arrives as Projects/Plume.md, not as Plume.md.
  • Nothing is flattened. Each upload carries the revision this machine last saw. If the vault copy changed on another computer meanwhile, Plume refuses the write and asks which copy to keep.
  • Read it anywhere at plume-md.com, straight in a browser.
  • Pausing or stopping sync deletes nothing.

Everything else Plume does works with no account at all. The vault is entirely opt-in.

Gives an assistant a memory

Plume Vault ships an MCP server. Create an API token, point Claude Code, Codex or any MCP client at it, and it can keep project decisions, notes and running logs somewhere that is still there next week — and that you can open in Plume on any of your machines. Eight tools: list, read, write, append, search and delete documents, plus the vault graph and storage status.

The notes are plain Markdown. Nothing is proprietary, and a token can be revoked in one click.

The rest

  • A sidebar with the folder tree (or your whole vault) and an outline of headings.
  • A graph of how your documents link to each other.
  • Live reload when the file changes on disk — same scroll position, same spot on the page.
  • Find in page with next, previous and a match count. Back and forward between linked notes.
  • Light, dark and system themes, plus text size, reading width and font settings.
  • Print and export to PDF, on white paper, with a real PDF outline built from your headings.
  • Updates that ask first: Plume tells you when a new version is out and installs it when you say so.
  • Nine languages on the website, following your browser.

Safe by default

Documents are sanitised, scripts never run, and links never launch programs. A note cannot make Plume pull files off other computers on your network. Plume saves Markdown and text and nothing else, so a flaw in the renderer cannot overwrite a shell profile or a script on your PATH.

Everything that touches the network happens in Plume's main process, so the window that renders your documents never has network access and keeps its full sandbox. Your vault password is hashed with scrypt; the account token is encrypted at rest with your system keychain.

Every release publishes SHA256SUMS.txt, and an automatic update is checked against it before it is allowed to run. A download that does not match is deleted rather than executed.

Worth saying plainly: Plume is not code-signed. Those checksums come from the same release as the download itself, so they protect you against a corrupted or swapped download — not against someone who controls the release. Signing is the fix, and it is next.

Downloads

System File
Windows 10 / 11, 64-bit Plume-Setup-1.2.0.exe
macOS, Apple silicon `Plume-1.2.0-mac-a...
Read more

Plume v1.1.1

Choose a tag to compare

@github-actions github-actions released this 08 Oct 07:43

Plume is a feather-light Markdown viewer. Double-click a .md file and it opens straight into a clean reading view: no workspace to import, no project to set up, no editor chrome.

1.1.1 prepares for the repository moving to its own organisation. The updater accepted release downloads from one repository path, baked in at build time. Plume is moving to github.com/Plume-MD, and after that move GitHub answers an older copy of Plume with URLs under the new name — which that copy would have refused, stopping its own updates for good. This release accepts both, so the move costs nobody an update. If you are on 1.1.0 or earlier, take this one before the move.

1.1.0 adds Git sync, and four colour palettes.

Git sync keeps a folder of notes in a Git repository: pull what changed elsewhere, commit what changed here, push. It is in ⋯ → Git sync…, and it is part of having a Plume Vault account. Plume never asks for a token and never stores one — it drives the Git already on your machine, so your credentials stay in your credential helper or SSH agent, and conflicts, submodules, LFS and signing behave exactly as they do in your terminal.

Starless, Greenwood, Commit and Lapis sit beside Plume's own under Reading settings → Palette. A palette recolours whichever of light or dark is in force rather than replacing that choice.

1.0.3 added four colour palettes. Starless, Greenwood, Commit and Lapis sit beside Plume's own under Reading settings → Palette. A palette recolours whichever of light or dark is in force rather than replacing that choice, so Auto still follows the system inside every one of them. The same five are on the website and the web app, in the footer. They are derived from four MIT-licensed Obsidian community themes, credited in the README.

1.0.2 fixed the updater, which could not install an update. "Install and restart" started the install and a second download at the same time, and the second one deleted the installer the first had just handed to Windows. Nothing was installed, Plume reopened on the old version, and offered the same update again — a loop with no way out of it.

If you are on 1.0.0 or 1.0.1, updating from inside Plume will not work, because the broken updater is the one you are running. Download 1.0.2 below or from plume-md.com/download and run it over the top — your files and settings are untouched. Updating from inside Plume works again from 1.0.2 onward.

1.0.1 fixed folder sync on a large notebook. Syncing stopped partway through and reported a number of failures with no reason. The vault asks a caller to slow down after six hundred requests a minute, and a thousand documents sent as fast as the network allows tripped that a few hundred in — everything after it failed. Sync now paces itself and waits when asked, plans against the 100 MB quota before it starts, and says why when a document is left out. The list of skipped files is also bounded, so pointing it at a folder full of things it will never send no longer costs memory on every rescan.

What it does

Opens the file you clicked

Plume registers itself for .md, .markdown, .mdown, .mkd, .mkdn, .mdwn, .mdtxt and .mdtext. A second file opens in a new window of the already-running app, so there is no cold start. Make it the default for .md once and every note opens in a calm, distraction-free window.

Reads Obsidian notes properly

[[wiki links]], ![[embeds]] and section transclusion, callouts including the foldable > [!warning]- kind, ==highlights==, #tags, %%comments%%, block ids and front-matter Properties — rendered the way Obsidian renders them, and resolved across the whole vault. For a note that really is inside an Obsidian vault, ⋯ → Open in Obsidian hands it over.

Everything GitHub-flavoured works too: tables, task lists, footnotes, definition lists, emoji shortcodes, syntax highlighting, KaTeX maths and Mermaid diagrams.

Edits when you ask it to

Press the pencil, or Ctrl+E, and the document becomes editable — the raw Markdown, in a plain editor, with no hidden formatting model. Ctrl+S saves. Esc goes back to reading.

Plume is a reader first, so editing is a mode you turn on rather than the state you are always in. The rules it keeps:

  • Nothing is written until you ask. Typing changes nothing on disk.
  • An unsaved change is never thrown away silently. A dot marks it, and leaving asks first.
  • A file changed elsewhere cannot overwrite your unsaved work. Plume tells you, and you choose.
  • Tab indents, Shift+Tab outdents, Enter continues a list.

Ctrl+Shift+E hands the file to VS Code, Cursor or your system editor.

Keeps a folder in sync, if you want

Create a free account and you get a 100 MB vault. There is no card, no trial and no paid tier.

Choose one folder and Plume keeps everything in it — notes, images and sub-folders — in your vault by itself while you are signed in. It watches the folder while Plume is open and checks again every few minutes, so edits made in any editor go up on their own. Your folder stays exactly where it is; nothing is moved or renamed.

  • Only documents and images are ever uploaded. Markdown, text, CSV, JSON, YAML, and PNG, JPEG, GIF, WebP and AVIF. Programs, installers and archives are refused by an allow-list and stay on your computer.
  • Folders are kept. Projects/Plume.md arrives as Projects/Plume.md, not as Plume.md.
  • Nothing is flattened. Each upload carries the revision this machine last saw. If the vault copy changed on another computer meanwhile, Plume refuses the write and asks which copy to keep.
  • Read it anywhere at plume-md.com, straight in a browser.
  • Pausing or stopping sync deletes nothing.

Everything else Plume does works with no account at all. The vault is entirely opt-in.

Gives an assistant a memory

Plume Vault ships an MCP server. Create an API token, point Claude Code, Codex or any MCP client at it, and it can keep project decisions, notes and running logs somewhere that is still there next week — and that you can open in Plume on any of your machines. Eight tools: list, read, write, append, search and delete documents, plus the vault graph and storage status.

The notes are plain Markdown. Nothing is proprietary, and a token can be revoked in one click.

The rest

  • A sidebar with the folder tree (or your whole vault) and an outline of headings.
  • A graph of how your documents link to each other.
  • Live reload when the file changes on disk — same scroll position, same spot on the page.
  • Find in page with next, previous and a match count. Back and forward between linked notes.
  • Light, dark and system themes, plus text size, reading width and font settings.
  • Print and export to PDF, on white paper, with a real PDF outline built from your headings.
  • Updates that ask first: Plume tells you when a new version is out and installs it when you say so.
  • Nine languages on the website, following your browser.

Safe by default

Documents are sanitised, scripts never run, and links never launch programs. A note cannot make Plume pull files off other computers on your network. Plume saves Markdown and text and nothing else, so a flaw in the renderer cannot overwrite a shell profile or a script on your PATH.

Everything that touches the network happens in Plume's main process, so the window that renders your documents never has network access and keeps its full sandbox. Your vault password is hashed with scrypt; the account token is encrypted at rest with your system keychain.

Every release publishes SHA256SUMS.txt, and an automatic update is checked against it before it is allowed to run. A download that does not match is deleted rather than executed.

Worth saying plainly: Plume is not code-signed. Those checksums come from the same release as the download itself, so they protect you against a corrupted or swapped download — not against someone who controls the release. Signing is the fix, and it is next.

Downloads

System File
Windows 10 / 11, 64-bit Plume-Setup-1.1.1.exe
macOS, Apple silicon Plume-1.1.1-mac-arm64.dmg (or .zip)
macOS, Intel Plume-1.1.1-mac-x64.dmg (or .zip)
Linux, x64 Plume-1.1.1-linux-x86_64.AppImage or Plume-1.1.1-linux-amd64.deb

Or get them from plume-md.com/download, which offers the right build for your system.

Installing

Windows

Run Plume-Setup-1.1.1.exe. Plume installs for all users in C:\Program Files\Plume, so Windows asks for administrator approval once. The installer is not code-signed yet: if SmartScreen shows "Windows protected your PC", choose More info → Run anyway.

To make Plume the default for .md, right-click a Markdown file and choose Open with → Choose another app → Plume → Always, or use ⋯ → Make Plume the default for .md inside Plume.

macOS

Open the DMG and drag Plume into Applications. Plume is not notarized by Apple, so macOS blocks the first launch. Use either of these:

  • Right-click (or Control-click) Plume in Applications, choose Open, then Open again. On macOS 15 or later, try to open it once, then go to System Settings → Privacy & Security and click Open Anyway.
  • Or run xattr -cr /Applications/Plume.app in Terminal.

Linux

  • AppImage: make it executable with chmod +x Plume-1.1.1-linux-x86_64.AppImage, then run it.
  • Debian / Ubuntu: sudo apt install ./Plume-1.1.1-linux-amd64.deb. On Ubuntu 24.04 and later, use the .deb: it installs the AppArmor profile that Electron apps need to start there.

Plume v1.1.0

Choose a tag to compare

@github-actions github-actions released this 08 Oct 06:59

Plume is a feather-light Markdown viewer. Double-click a .md file and it opens straight into a clean reading view: no workspace to import, no project to set up, no editor chrome.

1.1.0 adds Git sync, and four colour palettes.

Git sync keeps a folder of notes in a Git repository: pull what changed elsewhere, commit what changed here, push. It is in ⋯ → Git sync…, and it is part of having a Plume Vault account. Plume never asks for a token and never stores one — it drives the Git already on your machine, so your credentials stay in your credential helper or SSH agent, and conflicts, submodules, LFS and signing behave exactly as they do in your terminal.

Starless, Greenwood, Commit and Lapis sit beside Plume's own under Reading settings → Palette. A palette recolours whichever of light or dark is in force rather than replacing that choice.

1.0.3 added four colour palettes. Starless, Greenwood, Commit and Lapis sit beside Plume's own under Reading settings → Palette. A palette recolours whichever of light or dark is in force rather than replacing that choice, so Auto still follows the system inside every one of them. The same five are on the website and the web app, in the footer. They are derived from four MIT-licensed Obsidian community themes, credited in the README.

1.0.2 fixed the updater, which could not install an update. "Install and restart" started the install and a second download at the same time, and the second one deleted the installer the first had just handed to Windows. Nothing was installed, Plume reopened on the old version, and offered the same update again — a loop with no way out of it.

If you are on 1.0.0 or 1.0.1, updating from inside Plume will not work, because the broken updater is the one you are running. Download 1.0.2 below or from plume-md.com/download and run it over the top — your files and settings are untouched. Updating from inside Plume works again from 1.0.2 onward.

1.0.1 fixed folder sync on a large notebook. Syncing stopped partway through and reported a number of failures with no reason. The vault asks a caller to slow down after six hundred requests a minute, and a thousand documents sent as fast as the network allows tripped that a few hundred in — everything after it failed. Sync now paces itself and waits when asked, plans against the 100 MB quota before it starts, and says why when a document is left out. The list of skipped files is also bounded, so pointing it at a folder full of things it will never send no longer costs memory on every rescan.

What it does

Opens the file you clicked

Plume registers itself for .md, .markdown, .mdown, .mkd, .mkdn, .mdwn, .mdtxt and .mdtext. A second file opens in a new window of the already-running app, so there is no cold start. Make it the default for .md once and every note opens in a calm, distraction-free window.

Reads Obsidian notes properly

[[wiki links]], ![[embeds]] and section transclusion, callouts including the foldable > [!warning]- kind, ==highlights==, #tags, %%comments%%, block ids and front-matter Properties — rendered the way Obsidian renders them, and resolved across the whole vault. For a note that really is inside an Obsidian vault, ⋯ → Open in Obsidian hands it over.

Everything GitHub-flavoured works too: tables, task lists, footnotes, definition lists, emoji shortcodes, syntax highlighting, KaTeX maths and Mermaid diagrams.

Edits when you ask it to

Press the pencil, or Ctrl+E, and the document becomes editable — the raw Markdown, in a plain editor, with no hidden formatting model. Ctrl+S saves. Esc goes back to reading.

Plume is a reader first, so editing is a mode you turn on rather than the state you are always in. The rules it keeps:

  • Nothing is written until you ask. Typing changes nothing on disk.
  • An unsaved change is never thrown away silently. A dot marks it, and leaving asks first.
  • A file changed elsewhere cannot overwrite your unsaved work. Plume tells you, and you choose.
  • Tab indents, Shift+Tab outdents, Enter continues a list.

Ctrl+Shift+E hands the file to VS Code, Cursor or your system editor.

Keeps a folder in sync, if you want

Create a free account and you get a 100 MB vault. There is no card, no trial and no paid tier.

Choose one folder and Plume keeps everything in it — notes, images and sub-folders — in your vault by itself while you are signed in. It watches the folder while Plume is open and checks again every few minutes, so edits made in any editor go up on their own. Your folder stays exactly where it is; nothing is moved or renamed.

  • Only documents and images are ever uploaded. Markdown, text, CSV, JSON, YAML, and PNG, JPEG, GIF, WebP and AVIF. Programs, installers and archives are refused by an allow-list and stay on your computer.
  • Folders are kept. Projects/Plume.md arrives as Projects/Plume.md, not as Plume.md.
  • Nothing is flattened. Each upload carries the revision this machine last saw. If the vault copy changed on another computer meanwhile, Plume refuses the write and asks which copy to keep.
  • Read it anywhere at plume-md.com, straight in a browser.
  • Pausing or stopping sync deletes nothing.

Everything else Plume does works with no account at all. The vault is entirely opt-in.

Gives an assistant a memory

Plume Vault ships an MCP server. Create an API token, point Claude Code, Codex or any MCP client at it, and it can keep project decisions, notes and running logs somewhere that is still there next week — and that you can open in Plume on any of your machines. Eight tools: list, read, write, append, search and delete documents, plus the vault graph and storage status.

The notes are plain Markdown. Nothing is proprietary, and a token can be revoked in one click.

The rest

  • A sidebar with the folder tree (or your whole vault) and an outline of headings.
  • A graph of how your documents link to each other.
  • Live reload when the file changes on disk — same scroll position, same spot on the page.
  • Find in page with next, previous and a match count. Back and forward between linked notes.
  • Light, dark and system themes, plus text size, reading width and font settings.
  • Print and export to PDF, on white paper, with a real PDF outline built from your headings.
  • Updates that ask first: Plume tells you when a new version is out and installs it when you say so.
  • Nine languages on the website, following your browser.

Safe by default

Documents are sanitised, scripts never run, and links never launch programs. A note cannot make Plume pull files off other computers on your network. Plume saves Markdown and text and nothing else, so a flaw in the renderer cannot overwrite a shell profile or a script on your PATH.

Everything that touches the network happens in Plume's main process, so the window that renders your documents never has network access and keeps its full sandbox. Your vault password is hashed with scrypt; the account token is encrypted at rest with your system keychain.

Every release publishes SHA256SUMS.txt, and an automatic update is checked against it before it is allowed to run. A download that does not match is deleted rather than executed.

Worth saying plainly: Plume is not code-signed. Those checksums come from the same release as the download itself, so they protect you against a corrupted or swapped download — not against someone who controls the release. Signing is the fix, and it is next.

Downloads

System File
Windows 10 / 11, 64-bit Plume-Setup-1.1.0.exe
macOS, Apple silicon Plume-1.1.0-mac-arm64.dmg (or .zip)
macOS, Intel Plume-1.1.0-mac-x64.dmg (or .zip)
Linux, x64 Plume-1.1.0-linux-x86_64.AppImage or Plume-1.1.0-linux-amd64.deb

Or get them from plume-md.com/download, which offers the right build for your system.

Installing

Windows

Run Plume-Setup-1.1.0.exe. Plume installs for all users in C:\Program Files\Plume, so Windows asks for administrator approval once. The installer is not code-signed yet: if SmartScreen shows "Windows protected your PC", choose More info → Run anyway.

To make Plume the default for .md, right-click a Markdown file and choose Open with → Choose another app → Plume → Always, or use ⋯ → Make Plume the default for .md inside Plume.

macOS

Open the DMG and drag Plume into Applications. Plume is not notarized by Apple, so macOS blocks the first launch. Use either of these:

  • Right-click (or Control-click) Plume in Applications, choose Open, then Open again. On macOS 15 or later, try to open it once, then go to System Settings → Privacy & Security and click Open Anyway.
  • Or run xattr -cr /Applications/Plume.app in Terminal.

Linux

  • AppImage: make it executable with chmod +x Plume-1.1.0-linux-x86_64.AppImage, then run it.
  • Debian / Ubuntu: sudo apt install ./Plume-1.1.0-linux-amd64.deb. On Ubuntu 24.04 and later, use the .deb: it installs the AppArmor profile that Electron apps need to start there.

Plume v1.0.3

Choose a tag to compare

@github-actions github-actions released this 08 Oct 03:24

Plume is a feather-light Markdown viewer. Double-click a .md file and it opens straight into a clean reading view: no workspace to import, no project to set up, no editor chrome.

1.0.3 adds four colour palettes. Starless, Greenwood, Commit and Lapis sit beside Plume's own under Reading settings → Palette. A palette recolours whichever of light or dark is in force rather than replacing that choice, so Auto still follows the system inside every one of them. The same five are on the website and the web app, in the footer. They are derived from four MIT-licensed Obsidian community themes, credited in the README.

1.0.2 fixed the updater, which could not install an update. "Install and restart" started the install and a second download at the same time, and the second one deleted the installer the first had just handed to Windows. Nothing was installed, Plume reopened on the old version, and offered the same update again — a loop with no way out of it.

If you are on 1.0.0 or 1.0.1, updating from inside Plume will not work, because the broken updater is the one you are running. Download 1.0.2 below or from plume-md.com/download and run it over the top — your files and settings are untouched. Updating from inside Plume works again from 1.0.2 onward.

1.0.1 fixed folder sync on a large notebook. Syncing stopped partway through and reported a number of failures with no reason. The vault asks a caller to slow down after six hundred requests a minute, and a thousand documents sent as fast as the network allows tripped that a few hundred in — everything after it failed. Sync now paces itself and waits when asked, plans against the 100 MB quota before it starts, and says why when a document is left out. The list of skipped files is also bounded, so pointing it at a folder full of things it will never send no longer costs memory on every rescan.

What it does

Opens the file you clicked

Plume registers itself for .md, .markdown, .mdown, .mkd, .mkdn, .mdwn, .mdtxt and .mdtext. A second file opens in a new window of the already-running app, so there is no cold start. Make it the default for .md once and every note opens in a calm, distraction-free window.

Reads Obsidian notes properly

[[wiki links]], ![[embeds]] and section transclusion, callouts including the foldable > [!warning]- kind, ==highlights==, #tags, %%comments%%, block ids and front-matter Properties — rendered the way Obsidian renders them, and resolved across the whole vault. For a note that really is inside an Obsidian vault, ⋯ → Open in Obsidian hands it over.

Everything GitHub-flavoured works too: tables, task lists, footnotes, definition lists, emoji shortcodes, syntax highlighting, KaTeX maths and Mermaid diagrams.

Edits when you ask it to

Press the pencil, or Ctrl+E, and the document becomes editable — the raw Markdown, in a plain editor, with no hidden formatting model. Ctrl+S saves. Esc goes back to reading.

Plume is a reader first, so editing is a mode you turn on rather than the state you are always in. The rules it keeps:

  • Nothing is written until you ask. Typing changes nothing on disk.
  • An unsaved change is never thrown away silently. A dot marks it, and leaving asks first.
  • A file changed elsewhere cannot overwrite your unsaved work. Plume tells you, and you choose.
  • Tab indents, Shift+Tab outdents, Enter continues a list.

Ctrl+Shift+E hands the file to VS Code, Cursor or your system editor.

Keeps a folder in sync, if you want

Create a free account and you get a 100 MB vault. There is no card, no trial and no paid tier.

Choose one folder and Plume keeps everything in it — notes, images and sub-folders — in your vault by itself while you are signed in. It watches the folder while Plume is open and checks again every few minutes, so edits made in any editor go up on their own. Your folder stays exactly where it is; nothing is moved or renamed.

  • Only documents and images are ever uploaded. Markdown, text, CSV, JSON, YAML, and PNG, JPEG, GIF, WebP and AVIF. Programs, installers and archives are refused by an allow-list and stay on your computer.
  • Folders are kept. Projects/Plume.md arrives as Projects/Plume.md, not as Plume.md.
  • Nothing is flattened. Each upload carries the revision this machine last saw. If the vault copy changed on another computer meanwhile, Plume refuses the write and asks which copy to keep.
  • Read it anywhere at plume-md.com, straight in a browser.
  • Pausing or stopping sync deletes nothing.

Everything else Plume does works with no account at all. The vault is entirely opt-in.

Gives an assistant a memory

Plume Vault ships an MCP server. Create an API token, point Claude Code, Codex or any MCP client at it, and it can keep project decisions, notes and running logs somewhere that is still there next week — and that you can open in Plume on any of your machines. Eight tools: list, read, write, append, search and delete documents, plus the vault graph and storage status.

The notes are plain Markdown. Nothing is proprietary, and a token can be revoked in one click.

The rest

  • A sidebar with the folder tree (or your whole vault) and an outline of headings.
  • A graph of how your documents link to each other.
  • Live reload when the file changes on disk — same scroll position, same spot on the page.
  • Find in page with next, previous and a match count. Back and forward between linked notes.
  • Light, dark and system themes, plus text size, reading width and font settings.
  • Print and export to PDF, on white paper, with a real PDF outline built from your headings.
  • Updates that ask first: Plume tells you when a new version is out and installs it when you say so.
  • Nine languages on the website, following your browser.

Safe by default

Documents are sanitised, scripts never run, and links never launch programs. A note cannot make Plume pull files off other computers on your network. Plume saves Markdown and text and nothing else, so a flaw in the renderer cannot overwrite a shell profile or a script on your PATH.

Everything that touches the network happens in Plume's main process, so the window that renders your documents never has network access and keeps its full sandbox. Your vault password is hashed with scrypt; the account token is encrypted at rest with your system keychain.

Every release publishes SHA256SUMS.txt, and an automatic update is checked against it before it is allowed to run. A download that does not match is deleted rather than executed.

Worth saying plainly: Plume is not code-signed. Those checksums come from the same release as the download itself, so they protect you against a corrupted or swapped download — not against someone who controls the release. Signing is the fix, and it is next.

Downloads

System File
Windows 10 / 11, 64-bit Plume-Setup-1.0.3.exe
macOS, Apple silicon Plume-1.0.3-mac-arm64.dmg (or .zip)
macOS, Intel Plume-1.0.3-mac-x64.dmg (or .zip)
Linux, x64 Plume-1.0.3-linux-x86_64.AppImage or Plume-1.0.3-linux-amd64.deb

Or get them from plume-md.com/download, which offers the right build for your system.

Installing

Windows

Run Plume-Setup-1.0.3.exe. Plume installs for all users in C:\Program Files\Plume, so Windows asks for administrator approval once. The installer is not code-signed yet: if SmartScreen shows "Windows protected your PC", choose More info → Run anyway.

To make Plume the default for .md, right-click a Markdown file and choose Open with → Choose another app → Plume → Always, or use ⋯ → Make Plume the default for .md inside Plume.

macOS

Open the DMG and drag Plume into Applications. Plume is not notarized by Apple, so macOS blocks the first launch. Use either of these:

  • Right-click (or Control-click) Plume in Applications, choose Open, then Open again. On macOS 15 or later, try to open it once, then go to System Settings → Privacy & Security and click Open Anyway.
  • Or run xattr -cr /Applications/Plume.app in Terminal.

Linux

  • AppImage: make it executable with chmod +x Plume-1.0.3-linux-x86_64.AppImage, then run it.
  • Debian / Ubuntu: sudo apt install ./Plume-1.0.3-linux-amd64.deb. On Ubuntu 24.04 and later, use the .deb: it installs the AppArmor profile that Electron apps need to start there.

Plume v1.0.2

Choose a tag to compare

@github-actions github-actions released this 08 Oct 02:10

Plume is a feather-light Markdown viewer. Double-click a .md file and it opens straight into a clean reading view: no workspace to import, no project to set up, no editor chrome.

1.0.2 fixes the updater, which could not install an update. "Install and restart" started the install and a second download at the same time, and the second one deleted the installer the first had just handed to Windows. Nothing was installed, Plume reopened on the old version, and offered the same update again — a loop with no way out of it.

If you are on 1.0.0 or 1.0.1, updating from inside Plume will not work, because the broken updater is the one you are running. Download 1.0.2 below or from plume-md.com/download and run it over the top — your files and settings are untouched. Updating from inside Plume works again from 1.0.2 onward.

1.0.1 fixed folder sync on a large notebook. Syncing stopped partway through and reported a number of failures with no reason. The vault asks a caller to slow down after six hundred requests a minute, and a thousand documents sent as fast as the network allows tripped that a few hundred in — everything after it failed. Sync now paces itself and waits when asked, plans against the 100 MB quota before it starts, and says why when a document is left out. The list of skipped files is also bounded, so pointing it at a folder full of things it will never send no longer costs memory on every rescan.

What it does

Opens the file you clicked

Plume registers itself for .md, .markdown, .mdown, .mkd, .mkdn, .mdwn, .mdtxt and .mdtext. A second file opens in a new window of the already-running app, so there is no cold start. Make it the default for .md once and every note opens in a calm, distraction-free window.

Reads Obsidian notes properly

[[wiki links]], ![[embeds]] and section transclusion, callouts including the foldable > [!warning]- kind, ==highlights==, #tags, %%comments%%, block ids and front-matter Properties — rendered the way Obsidian renders them, and resolved across the whole vault. For a note that really is inside an Obsidian vault, ⋯ → Open in Obsidian hands it over.

Everything GitHub-flavoured works too: tables, task lists, footnotes, definition lists, emoji shortcodes, syntax highlighting, KaTeX maths and Mermaid diagrams.

Edits when you ask it to

Press the pencil, or Ctrl+E, and the document becomes editable — the raw Markdown, in a plain editor, with no hidden formatting model. Ctrl+S saves. Esc goes back to reading.

Plume is a reader first, so editing is a mode you turn on rather than the state you are always in. The rules it keeps:

  • Nothing is written until you ask. Typing changes nothing on disk.
  • An unsaved change is never thrown away silently. A dot marks it, and leaving asks first.
  • A file changed elsewhere cannot overwrite your unsaved work. Plume tells you, and you choose.
  • Tab indents, Shift+Tab outdents, Enter continues a list.

Ctrl+Shift+E hands the file to VS Code, Cursor or your system editor.

Keeps a folder in sync, if you want

Create a free account and you get a 100 MB vault. There is no card, no trial and no paid tier.

Choose one folder and Plume keeps everything in it — notes, images and sub-folders — in your vault by itself while you are signed in. It watches the folder while Plume is open and checks again every few minutes, so edits made in any editor go up on their own. Your folder stays exactly where it is; nothing is moved or renamed.

  • Only documents and images are ever uploaded. Markdown, text, CSV, JSON, YAML, and PNG, JPEG, GIF, WebP and AVIF. Programs, installers and archives are refused by an allow-list and stay on your computer.
  • Folders are kept. Projects/Plume.md arrives as Projects/Plume.md, not as Plume.md.
  • Nothing is flattened. Each upload carries the revision this machine last saw. If the vault copy changed on another computer meanwhile, Plume refuses the write and asks which copy to keep.
  • Read it anywhere at plume-md.com, straight in a browser.
  • Pausing or stopping sync deletes nothing.

Everything else Plume does works with no account at all. The vault is entirely opt-in.

Gives an assistant a memory

Plume Vault ships an MCP server. Create an API token, point Claude Code, Codex or any MCP client at it, and it can keep project decisions, notes and running logs somewhere that is still there next week — and that you can open in Plume on any of your machines. Eight tools: list, read, write, append, search and delete documents, plus the vault graph and storage status.

The notes are plain Markdown. Nothing is proprietary, and a token can be revoked in one click.

The rest

  • A sidebar with the folder tree (or your whole vault) and an outline of headings.
  • A graph of how your documents link to each other.
  • Live reload when the file changes on disk — same scroll position, same spot on the page.
  • Find in page with next, previous and a match count. Back and forward between linked notes.
  • Light, dark and system themes, plus text size, reading width and font settings.
  • Print and export to PDF, on white paper, with a real PDF outline built from your headings.
  • Updates that ask first: Plume tells you when a new version is out and installs it when you say so.
  • Nine languages on the website, following your browser.

Safe by default

Documents are sanitised, scripts never run, and links never launch programs. A note cannot make Plume pull files off other computers on your network. Plume saves Markdown and text and nothing else, so a flaw in the renderer cannot overwrite a shell profile or a script on your PATH.

Everything that touches the network happens in Plume's main process, so the window that renders your documents never has network access and keeps its full sandbox. Your vault password is hashed with scrypt; the account token is encrypted at rest with your system keychain.

Every release publishes SHA256SUMS.txt, and an automatic update is checked against it before it is allowed to run. A download that does not match is deleted rather than executed.

Worth saying plainly: Plume is not code-signed. Those checksums come from the same release as the download itself, so they protect you against a corrupted or swapped download — not against someone who controls the release. Signing is the fix, and it is next.

Downloads

System File
Windows 10 / 11, 64-bit Plume-Setup-1.0.2.exe
macOS, Apple silicon Plume-1.0.2-mac-arm64.dmg (or .zip)
macOS, Intel Plume-1.0.2-mac-x64.dmg (or .zip)
Linux, x64 Plume-1.0.2-linux-x86_64.AppImage or Plume-1.0.2-linux-amd64.deb

Or get them from plume-md.com/download, which offers the right build for your system.

Installing

Windows

Run Plume-Setup-1.0.2.exe. Plume installs for all users in C:\Program Files\Plume, so Windows asks for administrator approval once. The installer is not code-signed yet: if SmartScreen shows "Windows protected your PC", choose More info → Run anyway.

To make Plume the default for .md, right-click a Markdown file and choose Open with → Choose another app → Plume → Always, or use ⋯ → Make Plume the default for .md inside Plume.

macOS

Open the DMG and drag Plume into Applications. Plume is not notarized by Apple, so macOS blocks the first launch. Use either of these:

  • Right-click (or Control-click) Plume in Applications, choose Open, then Open again. On macOS 15 or later, try to open it once, then go to System Settings → Privacy & Security and click Open Anyway.
  • Or run xattr -cr /Applications/Plume.app in Terminal.

Linux

  • AppImage: make it executable with chmod +x Plume-1.0.2-linux-x86_64.AppImage, then run it.
  • Debian / Ubuntu: sudo apt install ./Plume-1.0.2-linux-amd64.deb. On Ubuntu 24.04 and later, use the .deb: it installs the AppArmor profile that Electron apps need to start there.

Plume v1.0.1

Choose a tag to compare

@github-actions github-actions released this 08 Oct 01:28

Plume is a feather-light Markdown viewer. Double-click a .md file and it opens straight into a clean reading view: no workspace to import, no project to set up, no editor chrome.

1.0.1 fixes folder sync on a large notebook. Syncing stopped partway through and reported a number of failures with no reason. The vault asks a caller to slow down after six hundred requests a minute, and a thousand documents sent as fast as the network allows tripped that a few hundred in — everything after it failed. Sync now paces itself and waits when asked, plans against the 100 MB quota before it starts, and says why when a document is left out. The list of skipped files is also bounded, so pointing it at a folder full of things it will never send no longer costs memory on every rescan. If you sync a folder, please update.

What it does

Opens the file you clicked

Plume registers itself for .md, .markdown, .mdown, .mkd, .mkdn, .mdwn, .mdtxt and .mdtext. A second file opens in a new window of the already-running app, so there is no cold start. Make it the default for .md once and every note opens in a calm, distraction-free window.

Reads Obsidian notes properly

[[wiki links]], ![[embeds]] and section transclusion, callouts including the foldable > [!warning]- kind, ==highlights==, #tags, %%comments%%, block ids and front-matter Properties — rendered the way Obsidian renders them, and resolved across the whole vault. For a note that really is inside an Obsidian vault, ⋯ → Open in Obsidian hands it over.

Everything GitHub-flavoured works too: tables, task lists, footnotes, definition lists, emoji shortcodes, syntax highlighting, KaTeX maths and Mermaid diagrams.

Edits when you ask it to

Press the pencil, or Ctrl+E, and the document becomes editable — the raw Markdown, in a plain editor, with no hidden formatting model. Ctrl+S saves. Esc goes back to reading.

Plume is a reader first, so editing is a mode you turn on rather than the state you are always in. The rules it keeps:

  • Nothing is written until you ask. Typing changes nothing on disk.
  • An unsaved change is never thrown away silently. A dot marks it, and leaving asks first.
  • A file changed elsewhere cannot overwrite your unsaved work. Plume tells you, and you choose.
  • Tab indents, Shift+Tab outdents, Enter continues a list.

Ctrl+Shift+E hands the file to VS Code, Cursor or your system editor.

Keeps a folder in sync, if you want

Create a free account and you get a 100 MB vault. There is no card, no trial and no paid tier.

Choose one folder and Plume keeps everything in it — notes, images and sub-folders — in your vault by itself while you are signed in. It watches the folder while Plume is open and checks again every few minutes, so edits made in any editor go up on their own. Your folder stays exactly where it is; nothing is moved or renamed.

  • Only documents and images are ever uploaded. Markdown, text, CSV, JSON, YAML, and PNG, JPEG, GIF, WebP and AVIF. Programs, installers and archives are refused by an allow-list and stay on your computer.
  • Folders are kept. Projects/Plume.md arrives as Projects/Plume.md, not as Plume.md.
  • Nothing is flattened. Each upload carries the revision this machine last saw. If the vault copy changed on another computer meanwhile, Plume refuses the write and asks which copy to keep.
  • Read it anywhere at plume-md.com, straight in a browser.
  • Pausing or stopping sync deletes nothing.

Everything else Plume does works with no account at all. The vault is entirely opt-in.

Gives an assistant a memory

Plume Vault ships an MCP server. Create an API token, point Claude Code, Codex or any MCP client at it, and it can keep project decisions, notes and running logs somewhere that is still there next week — and that you can open in Plume on any of your machines. Eight tools: list, read, write, append, search and delete documents, plus the vault graph and storage status.

The notes are plain Markdown. Nothing is proprietary, and a token can be revoked in one click.

The rest

  • A sidebar with the folder tree (or your whole vault) and an outline of headings.
  • A graph of how your documents link to each other.
  • Live reload when the file changes on disk — same scroll position, same spot on the page.
  • Find in page with next, previous and a match count. Back and forward between linked notes.
  • Light, dark and system themes, plus text size, reading width and font settings.
  • Print and export to PDF, on white paper, with a real PDF outline built from your headings.
  • Updates that ask first: Plume tells you when a new version is out and installs it when you say so.
  • Nine languages on the website, following your browser.

Safe by default

Documents are sanitised, scripts never run, and links never launch programs. A note cannot make Plume pull files off other computers on your network. Plume saves Markdown and text and nothing else, so a flaw in the renderer cannot overwrite a shell profile or a script on your PATH.

Everything that touches the network happens in Plume's main process, so the window that renders your documents never has network access and keeps its full sandbox. Your vault password is hashed with scrypt; the account token is encrypted at rest with your system keychain.

Every release publishes SHA256SUMS.txt, and an automatic update is checked against it before it is allowed to run. A download that does not match is deleted rather than executed.

Worth saying plainly: Plume is not code-signed. Those checksums come from the same release as the download itself, so they protect you against a corrupted or swapped download — not against someone who controls the release. Signing is the fix, and it is next.

Downloads

System File
Windows 10 / 11, 64-bit Plume-Setup-1.0.1.exe
macOS, Apple silicon Plume-1.0.1-mac-arm64.dmg (or .zip)
macOS, Intel Plume-1.0.1-mac-x64.dmg (or .zip)
Linux, x64 Plume-1.0.1-linux-x86_64.AppImage or Plume-1.0.1-linux-amd64.deb

Or get them from plume-md.com/download, which offers the right build for your system.

Installing

Windows

Run Plume-Setup-1.0.1.exe. Plume installs for all users in C:\Program Files\Plume, so Windows asks for administrator approval once. The installer is not code-signed yet: if SmartScreen shows "Windows protected your PC", choose More info → Run anyway.

To make Plume the default for .md, right-click a Markdown file and choose Open with → Choose another app → Plume → Always, or use ⋯ → Make Plume the default for .md inside Plume.

macOS

Open the DMG and drag Plume into Applications. Plume is not notarized by Apple, so macOS blocks the first launch. Use either of these:

  • Right-click (or Control-click) Plume in Applications, choose Open, then Open again. On macOS 15 or later, try to open it once, then go to System Settings → Privacy & Security and click Open Anyway.
  • Or run xattr -cr /Applications/Plume.app in Terminal.

Linux

  • AppImage: make it executable with chmod +x Plume-1.0.1-linux-x86_64.AppImage, then run it.
  • Debian / Ubuntu: sudo apt install ./Plume-1.0.1-linux-amd64.deb. On Ubuntu 24.04 and later, use the .deb: it installs the AppArmor profile that Electron apps need to start there.

Plume v1.0.0

Choose a tag to compare

@github-actions github-actions released this 07 Oct 14:55

Plume is a feather-light Markdown viewer. Double-click a .md file and it opens straight into a clean reading view: no workspace to import, no project to set up, no editor chrome.

This is the first release.

What it does

Opens the file you clicked

Plume registers itself for .md, .markdown, .mdown, .mkd, .mkdn, .mdwn, .mdtxt and .mdtext. A second file opens in a new window of the already-running app, so there is no cold start. Make it the default for .md once and every note opens in a calm, distraction-free window.

Reads Obsidian notes properly

[[wiki links]], ![[embeds]] and section transclusion, callouts including the foldable > [!warning]- kind, ==highlights==, #tags, %%comments%%, block ids and front-matter Properties — rendered the way Obsidian renders them, and resolved across the whole vault. For a note that really is inside an Obsidian vault, ⋯ → Open in Obsidian hands it over.

Everything GitHub-flavoured works too: tables, task lists, footnotes, definition lists, emoji shortcodes, syntax highlighting, KaTeX maths and Mermaid diagrams.

Edits when you ask it to

Press the pencil, or Ctrl+E, and the document becomes editable — the raw Markdown, in a plain editor, with no hidden formatting model. Ctrl+S saves. Esc goes back to reading.

Plume is a reader first, so editing is a mode you turn on rather than the state you are always in. The rules it keeps:

  • Nothing is written until you ask. Typing changes nothing on disk.
  • An unsaved change is never thrown away silently. A dot marks it, and leaving asks first.
  • A file changed elsewhere cannot overwrite your unsaved work. Plume tells you, and you choose.
  • Tab indents, Shift+Tab outdents, Enter continues a list.

Ctrl+Shift+E hands the file to VS Code, Cursor or your system editor.

Keeps a folder in sync, if you want

Create a free account and you get a 100 MB vault. There is no card, no trial and no paid tier.

Choose one folder and Plume keeps everything in it — notes, images and sub-folders — in your vault by itself while you are signed in. It watches the folder while Plume is open and checks again every few minutes, so edits made in any editor go up on their own. Your folder stays exactly where it is; nothing is moved or renamed.

  • Only documents and images are ever uploaded. Markdown, text, CSV, JSON, YAML, and PNG, JPEG, GIF, WebP and AVIF. Programs, installers and archives are refused by an allow-list and stay on your computer.
  • Folders are kept. Projects/Plume.md arrives as Projects/Plume.md, not as Plume.md.
  • Nothing is flattened. Each upload carries the revision this machine last saw. If the vault copy changed on another computer meanwhile, Plume refuses the write and asks which copy to keep.
  • Read it anywhere at plume-md.com, straight in a browser.
  • Pausing or stopping sync deletes nothing.

Everything else Plume does works with no account at all. The vault is entirely opt-in.

Gives an assistant a memory

Plume Vault ships an MCP server. Create an API token, point Claude Code, Codex or any MCP client at it, and it can keep project decisions, notes and running logs somewhere that is still there next week — and that you can open in Plume on any of your machines. Eight tools: list, read, write, append, search and delete documents, plus the vault graph and storage status.

The notes are plain Markdown. Nothing is proprietary, and a token can be revoked in one click.

The rest

  • A sidebar with the folder tree (or your whole vault) and an outline of headings.
  • A graph of how your documents link to each other.
  • Live reload when the file changes on disk — same scroll position, same spot on the page.
  • Find in page with next, previous and a match count. Back and forward between linked notes.
  • Light, dark and system themes, plus text size, reading width and font settings.
  • Print and export to PDF, on white paper, with a real PDF outline built from your headings.
  • Updates that ask first: Plume tells you when a new version is out and installs it when you say so.
  • Nine languages on the website, following your browser.

Safe by default

Documents are sanitised, scripts never run, and links never launch programs. A note cannot make Plume pull files off other computers on your network. Plume saves Markdown and text and nothing else, so a flaw in the renderer cannot overwrite a shell profile or a script on your PATH.

Everything that touches the network happens in Plume's main process, so the window that renders your documents never has network access and keeps its full sandbox. Your vault password is hashed with scrypt; the account token is encrypted at rest with your system keychain.

Every release publishes SHA256SUMS.txt, and an automatic update is checked against it before it is allowed to run. A download that does not match is deleted rather than executed.

Worth saying plainly: Plume is not code-signed. Those checksums come from the same release as the download itself, so they protect you against a corrupted or swapped download — not against someone who controls the release. Signing is the fix, and it is next.

Downloads

System File
Windows 10 / 11, 64-bit Plume-Setup-1.0.0.exe
macOS, Apple silicon Plume-1.0.0-mac-arm64.dmg (or .zip)
macOS, Intel Plume-1.0.0-mac-x64.dmg (or .zip)
Linux, x64 Plume-1.0.0-linux-x86_64.AppImage or Plume-1.0.0-linux-amd64.deb

Or get them from plume-md.com/download, which offers the right build for your system.

Installing

Windows

Run Plume-Setup-1.0.0.exe. Plume installs for all users in C:\Program Files\Plume, so Windows asks for administrator approval once. The installer is not code-signed yet: if SmartScreen shows "Windows protected your PC", choose More info → Run anyway.

To make Plume the default for .md, right-click a Markdown file and choose Open with → Choose another app → Plume → Always, or use ⋯ → Make Plume the default for .md inside Plume.

macOS

Open the DMG and drag Plume into Applications. Plume is not notarized by Apple, so macOS blocks the first launch. Use either of these:

  • Right-click (or Control-click) Plume in Applications, choose Open, then Open again. On macOS 15 or later, try to open it once, then go to System Settings → Privacy & Security and click Open Anyway.
  • Or run xattr -cr /Applications/Plume.app in Terminal.

Linux

  • AppImage: make it executable with chmod +x Plume-1.0.0-linux-x86_64.AppImage, then run it.
  • Debian / Ubuntu: sudo apt install ./Plume-1.0.0-linux-amd64.deb. On Ubuntu 24.04 and later, use the .deb: it installs the AppArmor profile that Electron apps need to start there.