What it unlocks
- Retrieval without the MCP protocol layer
- Bundled second-brain recipes the agent can follow
- Capture with structured provenance straight from the agent
- The same index every other GNO surface reads
Codex + GNO
Codex, with your documentation in reach
Install GNO for the OpenAI Codex CLI as an agent skill, an MCP server, or both. The skill path is the lighter one: no protocol handshake, just a CLI the agent already knows how to call, plus bundled recipes for brain-first lookup, capture with provenance, meeting ingestion, and citation discipline.
- 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 Codex in one command.
gno skill install --target codexgno mcp install --target codexgno skill show --file recipes/brain-first-lookup.mdProve it actually works
A written config file is not a working integration. GNO distinguishes the two, and so should you.
- Run
gno skill pathsto 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