A Markdown editor that keeps Markdown visible
Writer sits between a source editor and a rich-text writing app. It stores ordinary .md and .markdown files in folders you choose, but folds much of the syntax into a formatted editing surface. Headings look like headings, tables render as tables, images appear inline, Mermaid blocks become diagrams, and LaTeX formulas typeset through KaTeX. Move the caret into an element and its Markdown source becomes editable again.
That approach is the main attraction. There is no import step, account, private database, or new document format. Writer watches files for external changes, respects the workspace's .gitignore, and can open an existing documentation repository or Obsidian vault. Titles come from frontmatter or the first heading without rewriting the file. Internal Markdown and wiki links navigate through the workspace, including Obsidian-style image embeds and paths containing spaces.
The app is built with Tauri v2, a React and CodeMirror frontend, and Rust commands for filesystem work, indexing, watching, settings, updates, and command-line integration. The downloadable v0.4.0 DMG is only about six megabytes, a welcome contrast to many desktop editors built around a full browser runtime. GPL-3.0 licensing also keeps the application itself firmly open source.
The editing details are the strongest evidence
Writer's changelog shows unusual care around the unglamorous parts of Markdown editing. Lists preserve hanging indentation while scrolling and provide stable caret positions around hidden markers. Tables switch between rendered cells and editable source, including links and inline formatting. Heading markers appear only when editing the line. Images reserve their measured height so the document does not jump as they load.
Version 0.4.0 added inline and display math with rules that avoid treating ordinary currency as a formula. It also fixed arrow-key movement around headings, disappearing list indentation, image-related scroll jumps, and a recent-files list that could appear empty or be damaged by a crash. Recent-file persistence now uses a temporary file and rename, a small implementation choice with direct data-safety value.
Workspace navigation is equally thoughtful. The sidebar has pinned, recent, and complete file sections; files and folders can be moved by drag and drop without silently overwriting collisions. A command palette supports fuzzy navigation. Opening a single file can create a compact window without indexing an entire workspace, and external watching follows the active file through link navigation. Multiple windows avoid stacking in exactly the same screen position.
This is not feature breadth for its own sake. Most changes reduce friction in long writing sessions, where a one-pixel caret jump or unstable scroll position becomes more irritating than a missing AI button. Writer currently has no advertised AI writing layer, which is a strength for people seeking a quiet editor rather than another prompt surface.
Platform support is the hard boundary
The official product today is Apple Silicon macOS software. The v0.4.0 release contains an arm64 DMG, a Mac application tarball for updates, and the updater manifest. The release documentation says Windows, Linux, and x86_64 macOS are outside the current process. Releases are built, signed, notarized, and uploaded from the maintainer's machine rather than CI.
Tauri is cross-platform, and the repository contains icons and configuration for other targets, but that is not the same as supported packages. An open Linux request confirms there are no official builds. Source users need the Vite+ vp tool, JavaScript dependencies, Rust, Cargo, and the platform libraries required by Tauri. They must validate the resulting application themselves. MarkText or Zettlr is the safer choice for someone who simply needs a supported Windows or Linux download.
Even on the intended platform, the updater needs attention. One open v0.4.0 report says Writer repeatedly offers to install v0.4.0 when that version is already installed. The application continues working, but update prompts lose trust quickly. Because the updater reads the latest manifest from GitHub, users can also download releases manually while this behavior is unresolved.
Local-first has deliberate limits
Writer's local storage makes it easy to pair with Git, Dropbox, iCloud, Syncthing, or another tool, but those integrations are not built-in collaboration. There are no project accounts, shared comments, simultaneous editing, or mobile client in the documented product. An open request asks for version control, so respecting .gitignore should not be confused with managing commits or showing file history.
The file browser also hides dot-files and dot-folders. A current issue calls out .agents specifically, because skills stored there cannot be viewed inside Writer. Developers with documentation, configuration, or agent files under hidden directories will still need another editor. A separate open request for a source code mode shows the cost of Writer's rendered-first approach for users who want raw syntax visible all the time.
Hyperlinks remain another edge. One issue reports that automatic links can make URLs inside inline code or link destinations awkward to edit, and asks for a setting to disable link activation. These are not document corruption reports, but they matter in technical prose where URLs and code frequently meet.
Very young, very active
The repository was created on April 30, 2026, published ten releases between late May and July 20, and was pushed on August 9. Issues were updated in August, and the combined open count is modest. That is striking momentum, although a rapid v0.x cadence is not the same as years of compatibility history.
Documentation is uneven. The main README is barely more than an architecture summary and development commands. The changelog and feature specs are exceptionally detailed, while the release guide carefully documents signing and notarization. End users receive less guidance than contributors, especially outside macOS.
For the supported Mac, Writer already gets the central job right: edit Markdown comfortably while leaving files portable. Use it if that narrow promise matches your hardware and workflow. If you need collaboration, version history, hidden-file access, or dependable cross-platform distribution, its clean interface does not erase those gaps.