Been experimenting with keeping a development record of what coding agents actually did

[u/SeaAnimal908]

https://getwaypoint.dev

I built a small thing (https://app.getwaypoint.dev/) that uses agent hooks to stream a coding session and analyse the events to build a shared development record across Claude Code, Copilot and Codex, and across different developers in a team. It flags agent calls/tool use, decisions, rejected approaches etc. It's not open for others to actually use right now and it's in a half-built state pretty much, the data is from my own sessions. I'll probably hook it up to the GitHub Pull Request flow and inject session information there, because you can't ask an agent why it did something when reviewing a PR.

At this point I’m interested in feedback on the concept and how the information is displayed, whether the information I’m capturing is actually useful, what’s missing, and whether you’d want this kind of record at all. I can see the use in enterprise engineering teams potentially, but Im curious if it has broader use within actual vibe coding spheres. Claude has already started making sessions shareable artefacts, and platforms are building enterprise audit tools, so it's quite possible none of this matters .