Claude Code is excellent at the code in front of it and amnesiac about everything else: the decision you wrote down in March, the runbook in another repo, the PDF the client sent. Install GNO as a skill and it retrieves those on demand from your local index, pulling in the passages it needs instead of loading a knowledge base into every prompt. The skill route has no protocol overhead; the MCP route adds Context Capsules, Knowledge Delta, and verified Ask as first-class tools.

Connects via: Agent skill + MCP server
Requires: Bun 1.3+ and one indexed folder
Data boundary: Corpus and index stay on your machine

Install

Connect Claude Code in one command.

gno skill install --scope user

gno mcp install --target claude-code

gno setup ~/notes --name notes --connector claude-code-skill

What it unlocks

Search your whole corpus mid-task without pasting files into the chat
Compile one Context Capsule for a goal instead of running five searches
Cite an exact line span and content hash in a PR description or ADR
Second-brain recipes for lookup, capture, meeting ingestion, and provenance
Project-aware ranking: work in a repo and its collection gets a bounded, explainable boost

Prove it actually works

A written config file is not a working integration. GNO distinguishes the two, and so should you.

Run gno skill paths to see exactly where the skill was written.
Ask the agent to search your notes for a phrase only your corpus contains.
GNO cannot prove a client loaded an installed skill, so the retrieval answer is the proof. The install step reports what it wrote, not what the client did with it.

Keep reading

Related guides and features.

Claude Code setup guide

/docs/claude-code

Open

Agent integration

/features/agent-integration

Open

Context Capsules

/features/context-capsules

Open

All integrations

Every supported client

Browse all