fix: No combined wall-clock + idle cap for action-agent sessions (#334)
Add ACTION_MAX_LIFETIME env var (default 8h) that caps total session wall-clock time independently of ACTION_IDLE_TIMEOUT. A background watchdog sleeps for the remaining lifetime and, when triggered, kills the tmux session, posts a summary comment on the issue, writes PHASE:failed with a max_lifetime reason, and escalates to the supervisor. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
f1b3bf25a4
commit
42620a1341
2 changed files with 44 additions and 0 deletions
|
|
@ -270,6 +270,7 @@ issues labeled `action` that have no active tmux session, then spawns
|
|||
- `CODEBERG_TOKEN`, `CODEBERG_REPO`, `CODEBERG_API`, `PROJECT_NAME`, `CODEBERG_WEB`
|
||||
- `MATRIX_TOKEN`, `MATRIX_ROOM_ID`, `MATRIX_HOMESERVER` — Matrix notifications + human input
|
||||
- `ACTION_IDLE_TIMEOUT` — Max seconds before killing idle session (default 14400 = 4h)
|
||||
- `ACTION_MAX_LIFETIME` — Max total session wall-clock seconds (default 28800 = 8h); caps session independently of idle timeout
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue