Obsidian plugin
Khiip ships an Obsidian plugin (v0.2.0) that talks to your local daemon:
- a capture command to khiip a URL into your vault, and
- a recall sidebar for semantic search over everything you’ve captured.
Because the vault is plain Markdown + YAML frontmatter, captures appear as ordinary notes — Obsidian reads them directly, with no special viewer required. You get backlinks, graph view, search, and every other Obsidian feature over your captured corpus for free.
Install the plugin
Pick whichever path fits — all three install the same plugin.
Community plugins (recommended)
- Obsidian → Settings → Community plugins → Browse.
- Search Khiip → Install → Enable.
BRAT (track GitHub releases)
BRAT installs a plugin straight from its repo:
- Install BRAT from Community plugins → enable it.
- BRAT → Add beta plugin →
KhiipAI/khiip-obsidian→ Add plugin. - Enable Khiip under Community plugins.
Manual
From the latest release, download
main.js, manifest.json, and styles.css into
<your-vault>/.obsidian/plugins/khiip/, then enable Khiip under Community plugins.
Install the daemon
The plugin talks to the Khiip daemon — install it if you don’t already run one:
uv tool install khiip # or: pipx install khiipkhiipd serveSee Installation for the full setup, including per-source credentials.
Connect
The plugin connects to the daemon at 127.0.0.1:8478 and reads the same Bearer token from
~/.config/khiip/auth.toml that the CLI uses — no manual token entry in the common case.
Run khiipd serve, then use the capture command or open the recall sidebar.
Running the daemon on another host (Tailscale, a remote box)? Set the daemon URL and API key in the plugin settings.
Khiip Plus renders automatically
Khiip Plus lives on the daemon, not the plugin — so when Plus is active, the plugin’s captures and renders pick up the styled output and deeper extraction with nothing to install or toggle in Obsidian. There is no separate “Plus plugin”; the same plugin reflects whatever tier your daemon runs.
Type alignment
The plugin’s types.ts mirrors all v0.1 payload models from the daemon
(see Typed payloads), additively — so the plugin stays
in lock-step with what the daemon emits.