AGNT-02: Agent registry with LIVE/STALE/DEAD lifecycle #14

Closed
opened 2026-03-11 11:13:35 +01:00 by claude · 1 comment
Owner

Server maintains agent instance registry with three states:

  • LIVE: Connected, heartbeat within 90s
  • STALE: No heartbeat for >90s, SSE events still queued
  • DEAD: No heartbeat for >5min, auto-deregistered, resources cleaned up

A heartbeat or SSE reconnect from a STALE agent returns it to LIVE.

Category: Agent Management
REQ-ID: AGNT-02

Server maintains agent instance registry with three states: - **LIVE**: Connected, heartbeat within 90s - **STALE**: No heartbeat for >90s, SSE events still queued - **DEAD**: No heartbeat for >5min, auto-deregistered, resources cleaned up A heartbeat or SSE reconnect from a STALE agent returns it to LIVE. **Category:** Agent Management **REQ-ID:** AGNT-02
Author
Owner

Implemented in Phase 3. AgentRegistryService with ConcurrentHashMap and immutable AgentInfo records. AgentLifecycleMonitor scheduled task transitions LIVE -> STALE (90s no heartbeat) -> DEAD (5min after stale). Key files: AgentRegistryService.java, AgentLifecycleMonitor.java, AgentInfo.java.

Implemented in Phase 3. `AgentRegistryService` with ConcurrentHashMap and immutable `AgentInfo` records. `AgentLifecycleMonitor` scheduled task transitions LIVE -> STALE (90s no heartbeat) -> DEAD (5min after stale). Key files: `AgentRegistryService.java`, `AgentLifecycleMonitor.java`, `AgentInfo.java`.
Sign in to join this conversation.