Agentic Workflows [1]: Honeyguide: who maintains the understanding when agents write the code?
Coding agents make code easier to write and change, but what an agent works out about a repository usually stays in one private conversation. Honeyguide keeps that understanding as a checkable map meant to be shared: every claim cites its source lines, a separate Checker reads those lines against the claim, and a refresh keeps the map current as the code changes. On the repo I tested, the map didn't measurably help an agent answer more accurately. This post shows how the checking and the upkeep work and what they cost. The shared team workflow isn't built yet, and whether it saves engineering time is open.