** AI 에이전트에 대한 두 번째 뇌 구조. 솔로 시작, 안전하게 스케일.**

** PromptOwl ** | 웹사이트 | 백서 | 사양 | Discord

설정하기 Nest turn scattered knowledge — your repos, docs, Slack threads, tribal know-how — 구조로, 쿼리 가능한 두뇌 당신의 AI 에이전트 사용할 수 있습니다.

그것은 Obsidian로 메모를 덤프하고 패턴이 당신에게 줄 수없는 4 가지 것들과 LLM을 지적하는 것과 동일합니다.

• ** 구조.** 관계와 선택자 문법을 가진 Typed 노드. Agents는 그래프를 탐색하고 플랫 폴더가 아닙니다.
• ** ~ 100 × 더 싼 에이전트 세션. ** 요약 및 링크 된 허브 문서로 사전 다이제스트, 다음 세션은 50k 토큰의 원료 파일 대신 관련 컨텍스트의 ~500 토큰을 읽습니다.
• 공유 경로. 팀메이트로 내보내거나, PromptOwl 마켓플레이스를 유료 팩으로 배포할 수 있습니다.
• ** 준거, 준수 볼트에. ** 모든 변경은 versioned 및 hash-chained입니다. 전체 감사 트레일, 승인 보행, byte에 감사. 같은 vault는 10 분에 하나의 개발자를 내장 한 것은 그 날이 올 때 SOC 2 검토를 통과합니다.

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

The first time you run ctx it walks you through setup: a local vault, a team server, or both. After that, ctx just shows the command list. Prefer to script it? ctx init --starter developer still works.

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: