Show HN: Tolaria – Open-source macOS app to manage Markdown knowledge bases

Original Article ↗ Hacker News Discussion ↗

Overall reception

  • Many commenters find the app attractive, well-designed, and conceptually strong (Markdown + local files + git + relationships).
  • Several intend to try it, especially users coming from Obsidian/Logseq/Bear who like the UI and git-backed approach.
  • A few are immediately turned off by the “AI-first” positioning or the web technology stack.

Positioning vs existing tools

  • Frequent comparisons to Obsidian, Logseq, Notion, Bear, OneNote, VSCode, and Zettlr.
  • Distinguishing factors repeatedly cited:
    • Open source.
    • Git as first-class sync/versioning.
    • Focus on types, relationships, and structure over simple note editing.
    • AI agents as first-class consumers/producers of vault content.
  • Some argue Obsidian “already does this,” while others highlight that Obsidian is not open source and has different UX/assumptions.

Native vs webwrapper debate

  • Strong divide:
    • Some reject Tauri/Electron-style apps outright, insisting on “true” native macOS (AppKit/SwiftUI).
    • Others say Tauri is fast enough and are more interested in features and openness than implementation language.
  • Multiple native alternatives (e.g., mdnb, Typora, others) are suggested for those prioritizing Mac nativeness.

AI- and git-centric design

  • Discussion around AI agents editing the vault:
    • Ideas like treating AI as a git contributor, surfacing its activity in history, and even real-time presence indicators.
  • Git as a durable, auditable layer is widely praised; some note existing workflows where LLMs operate over git repos.

Performance, UX, and bugs

  • Claims of handling ~10k notes are attractive; one commenter asks about indexing vs lazy-loading (unclear from thread).
  • Reports of:
    • Sorting bugs after git commits.
    • Minor editor friction (keybindings, code fences behavior, large-file performance).
  • Others praise essentials like paste-from-clipboard images.

Mobile capture and ecosystem

  • Many stress that lack of good mobile capture/search often kills tools as daily drivers.
  • Workarounds shared: Drafts + git, Telegram bots + GitHub, iOS quick-note apps piping into Markdown vaults.
  • Several request a mobile version; the creator mentions plans and current use of a Telegram-based integration.

Open source, longevity, and ecosystem

  • Some skepticism about single-maintainer projects’ lifespan; others push back, arguing that open source + plain files mitigates risk.
  • Multiple commenters urge finding a sustainable monetization path while staying open source.
  • Thread becomes a hub for related “agent memory” and Markdown knowledge-base projects; collaboration interest is expressed.