You know this one
It learned your structure sixty commits ago
Nothing tells the agent that. Nothing tells you either, until it edits a file that moved last Tuesday — with complete confidence, because a stale map reads exactly like a fresh one.
Codebase map
A map that admits how stale it is
Your agent works from a picture of your repo. FlowKy checks that picture against HEAD at every session start and says how far it has drifted — before anything gets built on it.
Get FlowKy free
No card · Your own API key · Two minutes to set up
session start
12commits behind
changed · src/api/ packages/db/
SessionStart hook · git-aware
How it works
Mapped from the repo itself
Directory tree, symbols and import graph, generated from your code — not described by hand, so it cannot start out wrong.
Checked against HEAD every session
A session-start hook compares the map to the current commit. Drift is stated in commits, out loud, before work begins.
Refreshing is one command
“Your map is 14 commits old” is actionable in a way “maps go stale” never is. One command rebuilds it from the code as it stands.
Fair questions
- Is this another thing to keep updated?
- It measures its own staleness and says so. You refresh when the number bothers you — the failure mode of every other map is that it cannot tell you it is wrong.
- Which agents can read it?
- The map is files on disk. Claude Code, Cursor, Copilot, Gemini CLI, Windsurf and Cline all read files on disk.
Get FlowKy free
No card · Your own API key · Two minutes to set up