refactoringhq/tolaria

Tolaria is a note-taking app, not an AI product: it gives a structured editor and navigation layer over markdown files you own, and its git backing is the interesting part. Worth a try if you already keep a large plaintext vault and want an app that treats the filesystem as the source of truth.

The problem

You keep notes as markdown files, want to browse and edit them quickly, and want history and sync. The usual routine is an editor plus a separate git client plus some hand-rolled folder convention, with links and frontmatter maintained by hand. Tolaria opens a vault as a git repository, gives you an editor, command palette and type-based navigation, and commits on save. The result is a working note environment where the files remain normal .md files with YAML frontmatter that other tools can read.

What's different

The central choice is that the vault is a git repository and the app has no server account. Commits happen in the background, so version history comes from git rather than a proprietary sync service, and any remote works. Types are described as navigation lenses rather than schemas: no required fields, no validation, just categories for finding notes. That keeps the vault portable, but it also means consistency depends on your own habits rather than enforcement.

AI is present as a workflow, not a feature. The README lists Claude Code, Codex CLI and Gemini CLI setup paths and ships an AGENTS file for agents to read, and says a markdown vault works as context or memory for assistants. That is a sensible use of a files-first design, but it is external tooling around the vault, not an in-app assistant.

The trade-off is scope. A keyboard-first app aimed at a 10,000-note personal vault carries a learning curve: the command palette and editor are designed for power users, and the app will feel heavier than a plain text editor for someone with a few dozen notes. The repository's own history is short — created February 2026 — and the mobile app is in TestFlight beta, so the cross-device story is the least settled part.

Who should try it

Good fit: someone with an existing markdown vault who wants desktop editing, git history and fast navigation without giving up file ownership. The onboarding vault gives a guided tour if you want to evaluate the interaction model before moving your own notes. A secondary fit is a team organizing docs as agent context, since the git-first layout fits that use.

Poor fit: anyone who wants a hosted, zero-setup note app with built-in sync, or who expects strict schemas and field validation. Also poor fit if you work mostly on a phone today — iOS is beta and access is through the Discord community. Linux users should note that the README's development prerequisites are macOS or Linux, but there is no Windows development path listed.

Requirements and limitations

Installation is straightforward: a Homebrew cask on macOS or a signed installer for Windows, macOS and Linux. Windows installers are Authenticode-signed, but company-managed machines may still need IT to approve the publisher, which matters if you rely on an employer laptop.

Building from source is a bigger commitment: Node 20+, pnpm 8+, Rust stable and macOS or Linux. On Linux, Tauri 2 needs WebKit2GTK 4.1 and GTK 3, and the bundled MCP server spawns the system node binary at runtime, so Node must be installed from the distro package manager for external AI tooling. Ongoing care is ordinary git work: you own merge conflicts and remote setup, and mobile sync goes through iCloud or Files against the same repository. The AGPL-3.0 license and trademark policy also matter if you plan to distribute a fork.

HotRepo's take

HotRepo recorded five daily-board appearances between 2026-06-29 (17,389 stars) and 2026-10-26 (20,341 stars), with gains of 150–280 on the June–July dates and 61 on the October date. That is a thin, non-continuous sample, so persistence cannot be judged from it. The Show HN thread drew 318 points and 142 comments, which indicates discussion volume only. Before committing, check the installation and first-launch docs and confirm whether the mobile beta fits your daily workflow.