Prime Session Watchdog incident digest (automated, Windows)

[telemetrya2018-dotcom]

Automated two-hour incident batch

This message was rendered from structured, allowlisted metadata only. It contains no prompts, raw logs, session identifiers, usernames, absolute paths, or file contents.

• Confirmed cases: 25
• Underlying error events: 25
• Affected session count: 9
• UTC window: 2026-08-31T13:49:18.192000Z — 2026-09-01T14:59:40.370000Z
• Watchdog version: 0.2.0

kernel-runtime

• Cases: 1
• Categories: daemon-stale-working × 1
• Severity: high × 1
• Providers: hermes-local × 1
• Models: zai/glm-5.3-flash × 1
• Existing related report: no title/body match found during the preflight inventory.

provider-retry-state

• Cases: 2
• Categories: retry-exhausted-needs-input × 2
• Severity: high × 2
• Providers: hermes-local × 2
• Models: zai/glm-5.3-flash × 2
• Existing related report: Retry exhaustion silently parks tasks in needs_input and makes the UI look stuck #1934

provider-stream-lifecycle

• Cases: 6
• Categories: daemon-hard-stale-streaming × 1, subagent-hard-stale-streaming × 5
• Severity: critical × 5, high × 1
• Providers: openai-codex × 6
• Models: gpt-5.6-sol × 1, gpt-5.6-terra × 5
• Existing related report: no title/body match found during the preflight inventory.
• Structural diagnosis: The active model stream exceeded the hard-stale window while both daemon activity and the session file remained unchanged and no tool, bash, or compaction work was active.
• Source review found that the in-flight WebSocket event wait has an abort listener but no inactivity timer; the existing idle expiry applies only after a cached connection is no longer busy.
• Suggested safe fix: reset a configurable in-flight inactivity timer on each event, abort only that request through its existing AbortSignal, close the affected connection, and release the child runtime without exiting a shared process.

rlm-lifecycle

• Cases: 16
• Categories: rlm-metadata-stale-running × 6, rlm-passive-completed-listed-live × 10
• Severity: high × 6, medium × 10
• Existing related report: Deleting RLM subagents races with completion on Windows: repeated EPERM and a hidden live session #1935
• Structural diagnosis: Completed passive children can remain labelled live even when isSessionActive is false, while stop rejects them as unknown active; stopped children can also remain marked running in RLM metadata.
• Suggested safe fix: reconcile daemon lifecycle and RLM metadata after abort/dispose, and expose an idempotent release operation for passive completed children that preserves session history.

Publication policy

Retries from one failure episode are merged into one case. The global publisher performs at most one GitHub write per two hours. New cases remain queued until the next permitted batch.

[awhite0030]

Investigated this report and produced a candidate fix, validated on a fork of this repository.

Root cause, fix and validation from the working notes:

Root cause: WebSocket streams lack inactivity timeout checking, which causes hanging streams when the connection silently drops. Furthermore, passive completed children remain labelled live in the daemon due to incorrect registry status resolution.

Fix: Added a 30s inactivity timer in parseWebSocket (in openai-codex-responses.ts) which is reset on each message, aborting and closing the websocket on timeout. Also introduced releasePassiveRlmChildSession in AgentSession (in agent-session.ts and daemon-mode.ts) to cleanly drop RLM tracking of passive children and updated daemon status resolution to require daemonChild.status === "running" for a running state.

Validation: Pre-commit checks passed (npm run check) and automated tests verified (npx vitest --run test/suite/regressions/agent-session-passive-rlm-child-release.test.ts passed).

Upstream discussion: #1958

Diff: awhite0030/prime-agent@main...fix-websocket-inactivity-and-rlm-lifecycle-3642992307708068967
Full pull request: awhite0030#39

The change passes npm run check and the focused regression tests against current main. If a fix for this is still wanted, I can open a pull request.