pickfit

BrowseOther

Writer Computer

Local-first desktop markdown editor for plain-text folders on macOS.

Tested on macOSKnown vulnerabilities

Use it

Before you install: known vulnerabilities

pickfit found 13 known high or critical vulnerabilities in the packages a fresh install brings (OSV.dev, 3 Nov 2026). Weigh this before you install it.

  • crates:zip 4.6.1 zip: Critical Parser Differential & Security Control Bypass via Dual-Header Inconsistencies (Zip Cloaking) Leading to Arbitrary File Overwrite & RCE (GHSA-m665-v7pm-7grj, critical, fixed in 9.0.5)
  • npm:dompurify 3.4.7 DOMPurify SAFE_FOR_TEMPLATES bypass: split template expressions survive in attached shadow root content on DOM output modes (GHSA-cg2g-xh64-v4q7, critical, fixed in 3.4.17)
See 8 more

3 more findings not listed here.

macOS arm64

  1. Install Writer via brew cask

    brew install --cask --appdir=$HOME/Applications writer

Check that it works

/opt/homebrew/bin/writer --version

The output should contain “writer 0.8.0”.

Open Writer from Applications.

What it does

  • Edit markdown files where they are saved
    Not tested
  • Show tables and Mermaid diagrams
    Not tested
  • Work in more than one window
    Not tested
  • Open large workspaces quickly
    Not tested

How far pickfit got

macOS arm64

  1. Installs
  2. Opens to its setup screen
  3. 0 of 4 features work
  4. Works offline

Good for

  • open a folder and edit markdown files in place
  • edit files in Obsidian vaults
  • render Mermaid diagrams in notes

An alternative to Apple Notes and Obsidian.

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

macOS arm64

It opens to its first-run screen

  • Replayed from scratch
  • Checked on 1 Nov 2026
  • Version 0.8.0

When pickfit opened it, its first-run (setup) screen rendered. That shows it installs and starts; pickfit did not use any of its features. The launch passed again with the network off.

Differences the test machine hit

  • README: open a folder and edit its files in place
    In the test: open a file directly (open ~/pickfit-in/table.md -a ~/Applications/Writer.app) which renders immediately; the Add Folder button and cmd+o never opened a folder chooser in this VM
  • README: renders extended markdown such as tables and Mermaid diagrams
    In the test: direct file open showed formatted table and Mermaid diagram A->B rendered without any Preview toggle

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.