Have your coding agent list what your code change affects
A developer built LayerMap so coding agents can see which web addresses and tests a code edit reaches; in the author's tests agents found 97.9% of affected endpoints versus 58.8%.
Done with Claude Codegpt-5.5
What they did
A developer built LayerMap, a local add-on for Claude Code and Codex. It reads unsaved code changes and lists the web addresses and existing tests they reach. In a replayed session on the open-source app Miniflux, one call found every path to a function.
How it went
The author reports agents found 97.9% of affected endpoints with the map versus 58.8% without, when limited to 15 requests. Claude Code cost a third less with no limit.
Worth knowing
The author notes these are small samples on tasks they wrote. On small everyday tasks the map changed nothing but added about a fifth more time and cost.
Try it yourself with Claude Code
Before I commit, look at my uncommitted changes in this repository. Trace every place that calls the code I changed, up to the web routes, scheduled jobs or commands that start them. List the affected routes and the existing tests that cover them, then run those tests. Show me the list and test results and wait for my go-ahead before changing any code.
Source: X · @Griffin_Liu · Oct 20, 2026
Written with AI assistance from the original post and checked against our editorial guidelines. Results are as reported by the source, not independently verified. Spotted a mistake? Tell us.
