How it works

Map. Route. Prove.

KnoSky maps your code and docs on your machine. Claude Code, Cursor, Codex and Hermes ask it for a route instead of searching, and go straight to the right file — with an optional allow/deny receipt when you need governance.

Ink drawing of a city made of your files and docs: a KnoSky satellite overhead, one AI agent walking a light-blue route straight to the right building for a receipt, while agents without a route are lost in a maze and dead ends

1 · Map

Index the maze

Build a navigable model of repos and docs on the user’s machine. Live files stay the source of truth.

2 · Route

Share one menu

Assistants ask for paths via MCP — not freestyle monorepo walks. Multiple agents, one protocol.

3 · Prove

Optional Mode B

Identity → policy → receipt (or a useful deny). Advisory and governed paths stay labeled honestly.

Doctor honesty

Only promise what knosky doctor shows on that install. Help for several AI helpers (L3) is early — not a finished “safe multi-AI everywhere” product.

Try it free Protocol on wiki

For people

The city is how people see the map

The city view is how people walk the same map. What agents get is the GPS: one shared route to the right file — still GPS for agents.

Install & open the city from your code

Ink drawing of two teammates looking over a town of districts with a paper map whose route matches the streets