Notes about code should be written by whoever read the codeWhy codebase notes for AI coding agents should be written by the agent that did the work, not reconstructed later from a transcript.6 min read·codebase-memory.hashnode.devAug 3
From four tools to twoAn origin story told through deletions, the traversal tools that were missing fields, the labels that were guesses and the server that served nothing13 min read·codebase-memory.hashnode.devAug 3
The tool the agent does not callYou can ship a tool, document it, and instruct the agent to prefer it and it will still reach for grep. Why availability isn't adoption.8 min read·codebase-memory.hashnode.devAug 3
Why an index of your code cannot answer the same question twiceA code graph makes each step of a search cheaper. It never reduces how many steps you need, and it can't hold a conclusion and that gap matters.10 min read·codebase-memory.hashnode.devAug 3
Where the tokens go in an agent sessionMost of what an agent session costs isn't the answer it produced — it's the same context, re-sent on every turn. Here's the one lever that matters.7 min read·codebase-memory.hashnode.devAug 3