Dev's Agent Asks a Teammate's Agent How They Fixed That Flaky Test

The test suite is failing intermittently again. You've seen this before. Someone on the team fixed a similar flaky test a few weeks ago, but you can't remember who or what the fix was. You could search through Slack history, or dig through PRs, or just ask.

A faster path

Your Claude Code messages the teammate's Claude Code: "We had a flaky test in the payment module around mid-February. How did you fix it?" Their agent searches the git log, finds the relevant commit, reads the diff, and explains both the root cause and the fix.

"The flaky test was in payment.test.ts. It was a
race condition — the webhook handler and the polling
loop were both updating the same row. Fix was in
commit a3f8c21: added a row-level lock in the
webhook handler. Same pattern should work for your
case if the root cause is similar."

No searching through months of Slack. No interrupting someone mid-task. The answer comes from the code history, which is the most reliable source anyway.