Why can I not pause a running agent, correct its course, and have it resume cleanly?
Opportunity
Long-running agent tasks span hundreds of tool calls and can run for hours, but the only controls available today are letting the task finish or killing it entirely. A user who spots an error mid-run has no way to inject a correction, inspect the accumulated state, or redirect the task without losing all prior progress or feeding the agent context that desynchronizes it from the world state it has been acting on. An April 2026 arXiv paper is the first systematic study of interruptibility in environmentally constrained agent settings and shows how fragile current agents are when user intent changes mid-execution. Infrastructure vendors released durable execution runtimes in late 2025 and early 2026 that handle crash recovery, but semantic interruption, the ability to change what the agent is trying to accomplish rather than just restart it, remains unbuilt.
Why it matters
Semantic interruptibility is what converts a demo that runs once into a production tool a non-engineer can trust.
How I score the opportunity
The Opportunity Score is my own read, not a measurement: how much it hurts, how often it bites, and how little exists to solve it today. Higher means I think it is more worth building.
How much pain it causes when it shows up.
How often people actually run into it.
How little good tooling exists for it today.
More problems worth solving
Why does every AI app forget me the moment I close the tab?
AIWhy is learning a new field still gated by knowing what to ask?
AIWhy can a non-expert not verify what an AI just told them?
AIWhy do we test models on benchmarks but ship them on vibes?
AIWhy do AI agents have no memory of their own mistakes?
AIWhy can't I audit what a model was actually trained on?