Package Exports

granola-toolkit
granola-toolkit/dist/cli.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (granola-toolkit) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

granola-toolkit

The unofficial open-source Swiss army knife for Granola.

Sync your meeting archive locally, browse it in the browser or terminal, export anything you need, and run your own agents against transcripts and notes.

granola-toolkit is for people who want more than a flat export command: a local-first Granola archive, a real browser and terminal workspace, and automation you control.

Why Use It

Local-first control instead of being trapped in one app surface
CLI, browser, and TUI on one shared runtime and one local index
Bring your own agent workflows on top of transcripts and notes
Export notes and transcripts into files you actually own
Open-source and scriptable, with local prompts, rules, skills, and plugins

What You Get

granola sync for local indexing and refresh
granola web for a browser workspace
granola tui / granola attach for keyboard-first terminal use
granola notes and granola transcripts for file exports
granola automation plus harnesses/rules for BYOA review workflows
local diagnostics, sync history, and inspectable runtime state

Install

npm install -g granola-toolkit
granola --help

Without a global install:

npx granola-toolkit --help

The published package exposes both granola and granola-toolkit as executable names.

If you do not want to install via npm, each GitHub release also publishes standalone archives for macOS arm64, Linux x64, and Windows x64. Extract the archive and run granola (or granola.exe on Windows).

Quick Start

granola init --provider openrouter
granola auth login --api-key grn_...
granola web

granola init creates a local .granola.toml, starter harnesses, starter automation rules, and prompt files under ./.granola/ so the first-run setup is not just “read docs and assemble JSON by hand”.

If you start with granola web, the browser now walks you through the same first-run path: enter a Granola API key, import your meetings, choose an agent provider, and land in a workspace with a starter reviewable notes pipeline already configured.

granola web now prefers the long-running background-service path by default: it will reuse the existing service when one is already running, or start it for you when you have not asked for a foreground/debug session.

granola service start is still available when you want to warm the local sync loop without opening a browser first.

If you prefer to reuse the desktop app session instead, granola auth login still imports it from supabase.json.

Set Default Configuration

granola init writes a project-local .granola.toml for you. If you want to edit it directly, the file can look like this:

agent-provider = "openrouter"
agent-model = "openai/gpt-5-mini"
agent-harnesses-file = "./.granola/agent-harnesses.json"
automation-rules-file = "./.granola/automation-rules.json"
pkm-targets-file = "./.granola/pkm-targets.json"
output = "./exports/notes"
transcript-output = "./exports/transcripts"
debug = false

The CLI reads configuration in this order:

command-line flags
environment variables
.granola.toml
platform defaults

Relative paths in .granola.toml resolve from the directory that contains the config file.

Debug Logging

Yes, the toolkit supports a real debug mode.

granola sync --debug
granola web --debug --foreground
DEBUG_MODE=1 granola service start

Useful when you want to see config resolution, auth mode selection, sync behaviour, and runtime paths while diagnosing local-state issues.

Documentation

The detailed documentation now lives at kkarimi.github.io/granola-toolkit.

Local docs development:

npm run docs:dev
npm run docs:check

Key docs entry points:

Release history is also tracked in CHANGELOG.md.

Contributing

Contributions are welcome. See CONTRIBUTING.md for local setup, QA expectations, and contribution workflow.

Local Development

curl -fsSL https://vite.plus | bash
vp install
npm run web:check
vp pack
node dist/cli.js --help