When something breaks in production, the story of what happened is never simple. An agent flags an anomaly. A developer starts investigating. A pull request lands. CI runs. Another agent proposes a fix. If the process is particularly bad, we've seen cases where someone leaves a note for the on-call engineer picking up the next shift.

When you're in the middle of an outage, the last thing you need is to try to piece together the context from scratch, trying to figure out which action was taken by an agent, which was a human decision, and what was the reason behind every choice taken.

To that end, we’ve redesigned the problem timeline to better distinguish between agent findings, human actions, and external events like pull requests and CI runs, as well as new commenting features like threading.

Interfere aims to be the centralized place where agents and humans collaborate together, especially during urgent issues like an outage. We're actively shaping the roadmap around how teams actually use Interfere during incidents, and we want your input. What's still missing? What would make the problem timeline more useful for your team? Where are the gaps between what Interfere surfaces and what you need to make a fast decision? Let us know!