Hacker News new | ask | show | jobs
by skydhash 98 days ago
I think those are better suited to an issue tracker. As for changes that affected the source code, you can grep the patch in the git log too.
1 comments

Issue trackers are full of intent and decisions, that's true, but that's not the point here... It's about a storage that agents can use natively without the need of callings external APIs or MCPs.

And there is a slight difference between what you capture in issue trackers and what happens in reality in coding sessions.