epicsagas/alcove

→ Quick start
English ·
한국어 ·
日本語 ·
简体中文 ·
Español ·
हिन्दी ·
Português ·
Deutsch ·
Français ·
Русский
Alcove is an HTTP API server that gives AI coding agents on-demand access to your private project docs — **BM25 + vector hybrid search** for precision retrieval, **tree-sitter code indexing** so agents understand your codebase structure, and **policy enforcement** for doc consistency. No context bloat, no leaking docs into public repos, no per-project config for every agent.
Demo
> *Claude, Codex — search · switch projects · global search · validate & generate. One setup.*
CLI demo
> *alcove search · project switch · --scope global · alcove validate*
The problem
Your AI agent starts every session from zero.
It doesn't know your architecture. It ignores constraints from decisions you already made. It asks you to explain the same things every session.
The context window is the bottleneck. Every token costs money and attention. Loading 10 architecture docs into context wastes 50K+ tokens on every run — and Anthropic's own docs warn that bloated config files make agents *ignore your actual instructions*.
So you have three bad options:
**Stuff everything into agent config** — every file loads into context on every run. 10 docs = context bloat = slower, more expensive, less accurate responses.
**Copy-paste into every chat** — works once, doesn't scale past one session.
**Don't bother** — your agent invents requirements you already documented, ignores constraints from decisions you already made, and you re-explain the same architecture every Monday morning.
Now multiply it across 5 projects and 3 agents. Every time you switch, you lose context.
How Alcove solves this
Alcove doesn't inject your docs. **Agents search for what they need, when they need it.**
**Switch agents anytime. Switch projects anytime. The document layer stays standardized.**
Why Alcove
Alcove gives your agents a memory that survives between sessions.
Agents don't load your docs into context. **They search for what they need, when they need it.** Architecture docs, design decisions, runbooks, constraints — all in one place, searchable, never in your public repo.
Agent config is for agent behavior. Alcove is for project knowledge.
| Without a doc layer | With Alcove |
|---------------------|-------------|
| Docs in agent config bloat context on every run | Hybrid search (BM25 + RAG) — agents pull only what they need, ranked by relevance |
| Agent only sees text docs, not code structure | Tree-sitter code indexing — agents understand modules, functions, and types across 12 languages |
| Internal docs scattered across Notion, Google Docs, local files | One doc-repo, structured by project |
| Each AI agent configured separately for doc access | One setup, all agents share the same access |
| Switching projects means re-explaining context | CWD auto-detection, instant project switch |
| Agent search returns random matching lines | Ranked results — best matches first, one result per file |
| "Search all my notes about OAuth" — impossible | Global search across every project in one query |
| Sensitive docs sitting in project repos | Private docs on your machine, never in public repos |
| Doc structure differs per project and team member | policy.toml enforces standards across all projects |
| No way to check if docs are complete | validate catches missing files, empty templates, missing sections |
| Stale docs with broken links or WIP markers go unnoticed | lint detects broken links, orphans, and stale markers automatically |
| Notes from Obsidian or other tools stay siloed | promote brings any note into your doc-repo with one command |
Quick start
> **Required**: Run alcove setup once after installation to configure your docs root and enable full functionality. Plugins start the API server automatically, but Alcove cannot search or index documents until setup has been run.
>
> **Using Obsidian?** See the Ecosystem section for the docs structure and vault configuration.
Claude Code
Auto-installs the binary and starts the API server on next session start.
Updates with claude plugin update alcove@epicsagas.
Codex
Auto-installs the skill and starts the API server (the plugin is enabled automatically). Available immediately — no further steps needed.
Updates with codex plugin marketplace upgrade && codex plugin add alcove@epicsagas.
Antigravity (Gemini CLI)
Auto-installs the plugin (API server, skill, hooks) and starts it on next session start.