Agent idle timeout — warn or stop after N minutes of silence

Feature request for product/service

Cursor IDE

Describe the request

I left a simple agent question running in a background tab — answerable in seconds. It
ran for over 6 hours with no visible chat output. No error. No timeout. No completion.

On a laptop left on battery overnight, the pack drained to empty — a bad combination
with a silent, hung agent. No idle timeout means that can happen again: a stuck
session can run indefinitely with no warning and no auto-stop, with ongoing CPU/network
use and no user-visible progress.

Please add a configurable agent idle timeout:

  • Warning at N minutes (suggested default: 5 min) with no new chat output: show a
    banner with [Stop] and [Keep waiting] options.
  • Auto-stop at M minutes (suggested: 10–15 min): cancel the task and report last
    known state.
  • Setting: cursor.agent.idleTimeoutSeconds (0 = disabled).
  • Bonus: tighter threshold when on battery.

The main gap is UX and safety: a timeout would surface endless “Planning next moves”
with no user-visible progress and cap how long a stuck session can burn resources in the
background.

Related forum posts (max two URLs for new forum users; both Bug Report threads):

Happy to test a build.