npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

granola-toolkit

v0.67.0

Published

Unofficial open-source toolkit for syncing, browsing, exporting, and automating Granola locally

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

nima__nima__

Keywords

automationbyoacligranolanotessearchsynctranscriptstuiweb

Readme

granola-toolkit

npm version CI Docs License

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:

  1. command-line flags
  2. environment variables
  3. .granola.toml
  4. 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