graincrawl

Why it's ranked here

Its strongest case is controlled access to meeting history without modifying the Granola profile. Multiple source options, diagnostics, structured automation output, and portable archives make it unusually practical. The main reservation is dependence on Granola access boundaries that the tool cannot always cross.

What's good

Every Granola source is read-only, while writes stay confined to Graincrawl configuration, cache, and database storage. The command surface covers interactive browsing and automation. Snapshot imports support merging or exact restoration, and read-only SQL gives engineers flexible analysis without granting database mutation through that interface.

Tradeoffs

Private desktop access can fail when newer Granola versions keep encryption keys in an app-scoped Keychain item. Plaintext cache fallback only works when that cache remains readable. The public API omits panels and deletion events. Markdown export defaults to a limited batch unless the user raises the limit.

How to use it well

It suits engineers and operators who want a private, queryable meeting archive for search, scripts, migration, or backup. Start with diagnostics, choose the richest available source, automate through JSON, and create snapshots before moving machines. It does not replace Granola, edit its profile, or provide missing public API data.

Observed

License

MIT

Primary language

Go

Packaging and install

Homebrew tap formula or source installation through the Go toolchain

Interfaces

Command-line interface, terminal browser, JSON output, shell completion, and read-only SQL

Storage

Private local SQLite archive with portable snapshot import and export

Source support

Private desktop API session, readable plaintext desktop cache, and official public API

Quality gates

Make targets cover formatting, vetting, dead-code analysis, vulnerability checks, tests, smoke checks, and snapshot builds