Journals and outlines
A page for every day, blocks you can fold, zoom into and reference. Code fences, quotes and NOTE/TIP/WARNING callouts render like Logseq does.
Bitácora is a fast desktop outliner for your Logseq Markdown graphs. Written in Rust, drawn on the GPU, and fully compatible with the notes you already have — open your graph and keep writing.
In Spanish, bitácora is the binnacle — the stand beside the helm that holds the ship’s compass. It is also where the captain kept the logbook: course, weather, people aboard, what happened and when. One entry per watch, written plainly so anyone could read it years later.
That is the idea behind the app. A daily journal at the top, an outline under it, and plain Markdown files underneath everything — a record that belongs to you and outlasts any tool.
A page for every day, blocks you can fold, zoom into and reference. Code fences, quotes and NOTE/TIP/WARNING callouts render like Logseq does.
Its own SQLite + FTS5 index answers searches, backlinks and queries as you type, even on graphs with thousands of pages.
Every open task grouped Overdue, This week, Later and No date. Filter by marker, priority or page; pick a new date from a calendar.
A force layout of your pages with focus on N hops. Settings live in config.edn; export to SVG or PNG.
The right panel shows the local graph, page properties, backlinks with snippets and the blocks you opened with Shift+click.
Automatic commit, pull and push. Metadata conflicts resolve themselves; content conflicts are shown block by block — never as markers in your notes.
Command palette on Ctrl/⌘K, TODO/DOING/DONE on 1·2·3, keymaps grouped by context and tabs for everything.
Bitácora Light and Dark come from one set of design tokens. Fonts are embedded, so text looks the same on every system.
Rust and GPUI render the whole window on the GPU. A frameless window, its own top bar, and it reopens your last graph at startup.
Bitácora reads and writes the same Logseq 0.10 Markdown graph, with the same paths, file names and format. You can keep Logseq on the same folder and switch whenever you like.
logseq/custom.cssConnect Pando — managed by Bitácora or your own server — and your graph gains meaning-based search and an agent. In the app, amber always marks text the machine wrote and you have not accepted yet.
Keyword hits first, then blocks that match by meaning. Snippets always come from your local files.
Streaming answers and tool cards. Each proposed change is a diff with Apply and Deny, undoable and logged.
Pause at the end of a block and a faint continuation appears. Tab to accept, any other key to dismiss.
Ctrl/⌘J under any block. Review the draft, then insert, replace, retry or discard.
Summarise today or this week: themes, mood, tasks still open and next actions. On demand.
Related pages, links and tags for the page you are on — checked against your real blocks.
private:: content is never sentBitácora runs a Model Context Protocol endpoint on localhost, protected by a token, so the AI agents you already use can search and edit your notes. semantic_search and related_blocks are there too. The same powers come in a command-line tool.
# check the index and Pando connection bitacora-cli doctor --graph ~/logbook bitacora-cli semantic status --graph ~/logbook # search by meaning bitacora-cli semantic search "harbour charter" --limit 10
Free and open source under the MIT license. Coming from 1.x? Settings migrate on first launch.
Looking for an older build or the command-line tool? Browse all releases on GitHub or read what is new in the changelog.