Rank, 14 days: 121 on the Claude Code sheet
44 people reported

All time, since Sep 14, including 41 thumbs-up on GitHub.

Monitor expires after 30 minutes

“Since around 2.1.268 (still on 2.1.272), a Monitor armed with persistent: true is capped at 30 minutes.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/claude-code/issues/629/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Fading. No reports and thumbs-up in the last 7 days and 3 the week before, down from 19 a week at the late-September peak.

Monitor expires after 30 minutes despite persistent flag. Tool result says "expires in 30m unless the source ends first"; timeout_ms above 3600000 is rejected with a schema validation error.

Is this your bug?

File my report
Where
Monitor tool
Error text
"message": "timeout_ms must be <= 3600000"
Versions
2.1.270 to 2.1.285
Platforms
Linux, macOS
How bad
Breaks a normal workflow. Most reports say it used to work.

Original reports3, newest first

  1. Monitor timesout after 30 minutes#98450
  2. Monitor with persistent: true is capped at 30 minutes since 2.1.26x ("expires in 30m unless the source ends first")#94553
  3. Monitor tool: doesn't respect persistent flag and timeout_ms schema caps at 3600000 but actual lifetime is ~30 minutes, even during active (non-idle) sessions#94393

Do you work on Claude Code?

Claim its RAP Sheet to see what your users report and answer them in one place.