GPS for AI coding agents · free · runs locally

GPS for your AI agents.
Straight to the right code.

KnoSky maps your code and docs on your machine. Claude Code, Cursor, Codex and Hermes ask it for a route instead of wandering through files.

  • 6× faster to the right file
  • 68% fewer tokens
  • 70% fewer tool calls

Our own small guided-vs-wandering test (5 tasks), not a guarantee for every project.

The maze is the product problem

Agents don’t need another chat box. They need navigation through thousands of files and docs — without thrashing.

Wrong corridor

Open twelve files. Miss the one that matters.

Token thrash

Every dead end is money before a good edit.

No shared GPS

Each tool invents its own shortcuts.

No receipt

Permission is vibes after the fact.

Even GitHub hit the bill

Agentic workflows on every PR can quietly accumulate large API bills.

Industry problem proof — not a KnoSky score. GitHub Blog →

When navigation is guided

From our own small test suite — not someone else’s marketing numbers.

68%fewer tokens
70%fewer tool calls
6×faster to the right file

Small guided-vs-wandering test (5 tasks): guided found the right file every time; wandering didn’t. Details in the docs if you want them.

Three GPS moves

1 · Map

Index the maze

Build a navigable model of repos & docs on the user’s machine.

2 · Route

Share one menu

Assistants ask for paths via MCP — not freestyle monorepo walks.

3 · Prove

Optional Mode B

Identity → policy → receipt (or a useful deny).

Try it free
What's in the box

Everything that ships with KnoSky

One local protocol for map → route → optional receipt. Less thrash cost for teams. Less upload risk for careful CTOs. Here’s what ships — including the optional Enterprise path for proof.

See package on GitHub
Value for builders & careful orgs

Efficiency

Our own small guided vs wandering study: 68% fewer tokens, 70% fewer tool calls, 6× faster to the right file. Not someone else’s deck.

Risk averted

Local-first (no body vault). Map tools stay read-only. Share-safe can fail closed on secret-like text. Audit pack a CISO can re-check.

Outcomes

Fewer dead AI pilots after Security. Less “where is billing?” thrash. Optional architecture hangboard so risk districts show up before outage week.

2

City HTML (human skin)

Isometric city so people can walk the same map agents route through.

  • Not the agent GPS hero metaphor
  • Self-contained city file
  • Teammate-shareable picture of the system
For people
4

Mode A and Mode B

Advisory tips or identity + policy + audit receipts.

  • Mode A: labeled ADVISORY_UNAUTH
  • Mode B: ALLOW / DENY_* + lease
  • agent-register mints leaseId
Checked answers
5

Connect your tools

Wire once, same GPS across tools you already use.

  • : Claude Code, Cursor, Codex, Hermes
  • : VS Code, Greptile recipe, GHA PR-GPS
  • Coding packs omit audit tools on purpose
Connect your tools
6

Doctor and honest limits

Know what you may honestly say for this install.

  • knosky doctor scorecard
  • Ladder L0 to L3 honesty
  • Windows lockdown realism
Health check
7

L3 swarm foundation

Local multi-agent coordinator — leases, claims, quotas, heatmap, bench.

  • Not multi-tenant cloud fleet product
  • Not swarm-safe everywhere marketing
  • Doctor: FOUNDATION present
Several helpers (early)
8

PR-GPS Action

Advisory navigation comments on pull requests.

  • Never blocks the build by default
  • Structure/import hints — not a body store
Pull request tips
9

Docs and guides

Tool menu, decision codes, ladder, wiki, llms.txt.

  • knosky.com and knosky.wiki
  • Agent-readable product summary
  • Open protocol under FSL-1.1-MIT
Guides & docs
11

Architecture intel

District hangboard: docs, ownership, tests, churn, drift, risk.

  • knosky intel
  • Local proxies — not a full bank SAST/CVE box
  • CODEOWNERS helps ownership scores
Architect view
12

Private synthetic gauntlet

Disposable attack hosts + multi-role checks + rollup report.

  • Secrets, ignores, traversal, injection, stale…
  • Private by default — not a public “attack-tested” logo
  • Never customer source as fixtures
Private proof
Not in the box: a coding model, a hosted vault of your source, always-on product telemetry, a promise of production swarm-safe fleets on every laptop, or a public “attack-tested everywhere” badge by default. Those are deliberate non-goals — public copy stays within what doctor proves on that install.
Ink drawing of two teammates on a terrace looking over a town of districts, one pointing, the other holding a paper map whose light-blue route matches the route on the streets

Human skin · your folders and docs as a town you can walk

For people, not agents

The city is how humans see the map

Agents need routes through a maze. Humans need a place they can walk. The multi-depth isometric city is the skin of KnoSky — a place humans walk, on the same local map agents route through. Agents get the route; people get the city — the product is still GPS for agents.

Explore districts, find buildings, hand a teammate a picture of the system. Depth and protocol still live behind install + wiki.

Install KnoSky — see the city from your code

Run npx knosky@latest . in your repo. KnoSky builds a local city from your folders and files — not a canned marketing skyline.

Install on your machine

One command in your project folder. No account. Builds a local map from your code.

npx knosky@latest . Install steps