The "context rot" framing is spot on. I've seen the same thing discussed a lot in CI/CD tooling circles — agents lose track of what's already been tried and start suggesting the same fixes in loops.
Storing the reasoning as markdown in git is a clever move. It means the context survives not just across sessions but across team members too. Someone can pick up a task and see why certain approaches were rejected, not just the final code.
Curious if you've found that agents actually read the prior context reliably, or if you need to explicitly inject it at the start of each session.
Storing the reasoning as markdown in git is a clever move. It means the context survives not just across sessions but across team members too. Someone can pick up a task and see why certain approaches were rejected, not just the final code.
Curious if you've found that agents actually read the prior context reliably, or if you need to explicitly inject it at the start of each session.