You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Replace the single 30-min timer with two independent timers:
- Idle timeout (AGENT_IDLE_TIMEOUT, default 10 min): reset on any stdout
activity. Agent with no stdout for 10 min is considered stuck → killed.
Catches the hung-waiting-on-API pattern that caused 30-40 min hangs.
- Absolute ceiling (AGENT_ABSOLUTE_TIMEOUT, default 45 min): never resets.
Hard cap regardless of activity. Prevents runaway agents producing
garbage output from running forever.
Both timers log their reason (idle/absolute) for easier post-mortems.
Both values are configurable via env vars.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,13 @@
1
1
# Changelog
2
2
3
+
## v0.6.1 (2026-03-19) — Dual timeout for stuck agents
4
+
5
+
### Fixes
6
+
-**Dual agent timeout** replaces the old single 30-min timer:
7
+
-**Idle timeout** (10 min default, `AGENT_IDLE_TIMEOUT` env var): reset on any stdout activity. An agent that produces no output for 10 minutes is considered stuck and killed. This catches the "hung waiting on API" case that was causing 30-40 min hangs.
8
+
-**Absolute ceiling** (45 min default, `AGENT_ABSOLUTE_TIMEOUT` env var): never resets, regardless of any activity. Hard cap for runaway agents producing garbage output.
9
+
- Both timeouts log their reason (`idle` vs `absolute`) to make post-mortems easier.
10
+
3
11
## v0.6.0 (2026-03-19) — Reliability + remote control
0 commit comments