Эта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал
Structured, versioned context for AI agents. Context Nest organizes knowledge as markdown documents in a vault, with versioning, integrity verification, and a query language — accessible via CLI or...
Обзор
Context Nest turns scattered knowledge — your repos, docs, Slack threads, tribal know-how — into a structured, queryable brain your AI agents can use. It's the same instinct as dumping your notes into Obsidian and pointing an LLM at them, with four things that pattern doesn't give you: - Typed nodes with relationships and a selector grammar. Agents navigate a graph, not a flat folder. - Pre-digested into summaries and linked hub documents, so the next session reads ~500 tokens of relevant context instead of stuffing 50k tokens of raw files. - Export to a teammate, or publish to the PromptOwl marketplace as a paid pack others can query. - Every change is versioned and hash-chained. Full audit trail, approval-ready, auditable down to the byte. The same vault that onboarded one developer in ten minutes passes a SOC 2 review when that day comes.
README
Показан фрагмент оригинального README. Открыть оригинал.
Context Nest
A structured second brain for your AI agents. Start solo, scale safely.
by PromptOwl | Website | Whitepaper | Specification | Discord
Context Nest turns scattered knowledge — your repos, docs, Slack threads, tribal know-how — into a structured, queryable brain your AI agents can use.
It’s the same instinct as dumping your notes into Obsidian and pointing an LLM at them, with four things that pattern doesn’t give you:
- Structure. Typed nodes with relationships and a selector grammar. Agents navigate a graph, not a flat folder.
- ~100× cheaper agent sessions. Pre-digested into summaries and linked hub documents, so the next session reads ~500 tokens of relevant context instead of stuffing 50k tokens of raw files.
- A sharing path. Export to a teammate, or publish to the PromptOwl marketplace as a paid pack others can query.
- Governed, not a compliance bolt-on. Every change is versioned and hash-chained. Full audit trail, approval-ready, auditable down to the byte. The same vault that onboarded one developer in ten minutes passes a SOC 2 review when that day comes.
Works the same for a solo dev’s second brain, a team’s living onboarding doc, or an enterprise’s safe shared brain — one CLI, one file format, one vault. Start solo; scale when you need to.
Quick Start
npm install -g @promptowl/contextnest-cli
ctx init --starter developer
Getting started is one question: what are you trying to capture? Point your agent at a codebase, a folder of docs, an old wiki, or just tell it what’s in your head. It’ll build the first usable version in ten minutes and get denser every time you come back.
See all starters: ctx init --list-starters
What the install puts on your disk
Two packages, no nesting, and no install scripts — nothing of ours executes when you install. The MCP server installs zero dependencies. For a lean install without terminal colour:
npm install -g @promptowl/contextnest-cli --omit=optional
That leaves exactly one package. The rest of the code is compiled into the published bundle rather
than resolved from npm, so the install is deterministic — and every bundled package is listed with
its version and licence alongside the installed ones in
DEPENDENCIES.md. CI regenerates that file on every run and fails on drift, and
uploads the machine-readable graph as the dependency-graph build artifact.
What leaves your machine
Nothing, unless you run a command that names a destination or opt in:
| Trigger | Destination | Sent | Default |
|---|
Установка
docker run -i --rm contextnest-mcp # demo vault baked into the imageКонфигурация
{
"mcpServers": {
"contextnest": {
"command": "node",
"args": ["/absolute/path/to/packages/mcp-server/dist/index.js"],
"env": {
"CONTEXTNEST_VAULT_PATH": "/path/to/your/vault"
}
}
}
}