Crash investigations stall when the client and agent trail tell different stories.
Daily release velocity protects users from waiting, while weakly connected evidence risks sending engineers after the wrong cause.
Who you’d be doing this for
“I spent half the afternoon matching crash logs to agent runs, and the release train kept moving.”
Rita Fontana · Staff Software Engineer
Leads a platform team that relies on agent sessions while maintaining a large desktop codebase.
What is at stake
Recurring crashes after agent sessions are consuming investigation time because the evidence does not agree. You must decide what AI can rank safely and what engineers need to verify before a fix ships.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- daily release speed vs. root-cause confidence
- ranked AI hypotheses vs. engineer verification
- client telemetry vs. agent workflow evidence
- useful automation vs. noisy investigation output
Why Cursor
Cursor Editor depends on reliable Electron sessions and agent workflows for developers who use the editor throughout their daily work.
Written with these in mind
Not your kind of problem? 42 more at Cursor, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.