Tine

A fast, local, Logseq-compatible outliner. Reads and writes the same markdown graph as Logseq — swap between the two on the same files.

English | 简体中文 The English README is authoritative if the versions differ.

▶ Browse a demo graph — the onboarding graph, published with Tine's own HTML export.

What is Tine?

Tine is a desktop outliner built to look and feel like Logseq (opens in a new tab) while being much faster. It operates directly on the standard Logseq graph layout — journals/, pages/, assets/, and logseq/config.edn — so you can point it at the graph you already use and keep editing in either app (one at a time). Files are written back in Logseq-compatible markdown, so there's no import/export step and no lock-in.

Why build it? Logseq's UI is Electron + DataScript with heavy re-rendering, and it gets sluggish on large graphs. Tine is a ground-up rewrite: a small native shell (Tauri/WebKitGTK), a pure-Rust core for parsing and indexing, and a fine-grained reactive frontend (SolidJS) that never diffs a virtual DOM. The editor keeps the live block tree in the frontend, so keystrokes never round-trip to Rust, and whole-graph reads (search, backlinks, queries) hit an in-memory cache instead of re-parsing.

Status: a usable daily-driver for outlining, linking, tasks, journals, search, queries, and PDF annotation. Linux is the primary, best-tested platform; macOS and Windows builds are produced too but are newer. Not yet 1.0 — see [Roadmap](#roadmap--non-goals).

Command line

The desktop binary also supports terminal workflows. Run tine --help for the full reference.

--output is an existing absolute folder outside the graph; the export creates one new child there and never replaces an existing one. Linux .deb and .rpm packages install the generated man tine page.

What Tine adds on top of Logseq

These are the things that started as "I wish Logseq did this" — Tine's reasons to exist beyond raw speed. (Comparisons are against current Logseq desktop core, no plugins.)

• Native speed. Pure-Rust core + SolidJS fine-grained reactivity + a tiny Tauri/WebKitGTK

runtime instead of Electron — typing stays in the frontend tree, reads hit an in-memory index.

• Built-in tabs. Middle-click anything to open it in a background tab; pin, drag-reorder,

Mod+W to close, and use the overflow overview when titles no longer fit. (Logseq core has none.)

• Search that grows into a query. Open all Ctrl+K results in a persistent tab, switch the