The modules
Parachute is four committed-core pieces that compose into one system. Install any one on its own; run them together and you have a memory layer for everything you think with.
Everything runs through the Hub — one parachute command, one portal, one OAuth issuer. Install a module and the hub supervises it; the Vault holds your knowledge, Surface renders it, and Scribe turns voice into text on the way in. Each module is its own open-source repo and its own npm package.
Vault
Memory graphYour knowledge graph — notes, tags, wikilinks — in one SQLite-backed store that speaks both REST and MCP. Any AI or app reads and writes the same source of truth, with full-text search and lossless portable-markdown export for git projection or Obsidian round-trip. Reach for it the moment you want your memory to outlive a single chat or tool.
parachute install vaultSurface
UI hostThe UI host module, with Notes bundled as its first canonical surface: an installable, offline-capable PWA for browsing, searching, editing, and voice-capturing into your vault — multi-vault, one install for every vault on your hub. Drop additional custom SPAs under the same supervisor. Use it when you want a screen on your vault, or a starting point for a UI shaped to your own brain.
parachute install surfaceScribe
TranscriptionA Whisper-compatible transcription worker. It turns voice notes into text on the way into your vault — running locally by default, or against a cloud provider you bring if you'd rather. Install it when you want to capture by speaking; Surface's voice capture wires up to it automatically.
parachute install scribeHub
Portal · CLIThe coordinator everything else runs through: the portal on :1939, the OAuth issuer that mints per-vault scoped tokens, the supervisor that keeps every module alive, and the parachute CLI itself — install, start, stop, expose, lifecycle for the whole system. It's the first thing you install; parachute init brings it up and drops you into the setup wizard.
bun add -g @openparachute/hub && parachute initAgent
Experimental previewAn early preview of agent-in-the-loop work, built on your vault. You define an agent as a note (#agent/definition) — its system prompt and config live in the vault — and a message to it becomes a turn: the daemon runs a sandboxed Claude Code turn and writes the reply back as a note. Reachable from chat (Telegram today), and — because every message is just a note — from other agents and automations too. The shape is still moving — treat it as a preview of where agent-in-the-loop work is heading, not a settled module.
Experimental — runs from source (the npm package is a deprecated prior version). See the parachute-agent repo.
Install the whole thing
One command brings up the hub and walks you through the rest in the setup wizard — vault, surface, and scribe install from there.
bun add -g @openparachute/hub && parachute init
Or read the roadmap for where each module is headed.