Skip to content
Instar

Self-Healing

Your agent recovers from problems on its own. No silent failures, no stale sessions, no unanswered messages.

Stall Detection

Section titled “Stall Detection”

If a Telegram message goes unanswered for 2+ minutes, an LLM-powered triage nurse activates:

  1. Diagnoses the problem (session crashed, session stalled, session busy)
  2. Treats it (nudge the session, interrupt, or restart)
  3. Verifies recovery
  4. Escalates if treatment fails
Terminal window
curl localhost:4040/triage/status
curl localhost:4040/triage/history

Session Monitoring

Section titled “Session Monitoring”

Polls all active sessions every 60 seconds. Detects:

  • Dead sessions — Process no longer running
  • Unresponsive sessions — Running but not producing output
  • Idle sessions — No activity for too long

Coordinates automatic recovery for each case.

Promise Tracking

Section titled “Promise Tracking”

When the agent says “working on it” or “give me a minute,” a timer starts. If no follow-up arrives within the expected window, the agent is nudged and the user is notified.

Orphaned Work Detection

Section titled “Orphaned Work Detection”

A background build or autonomous session can die before committing its work, leaving edited files stranded in a worktree with no promise registered for them — invisible, silently lost. The OrphanedWorkSentinel closes that gap: it detects worktrees holding uncommitted changes whose owning session has died and settled, records each durably, and raises one calm agent-health notice. It needs nothing registered — it reads the stranded work straight off disk. Signal-only (it never deletes or mutates the work); an optional, off-by-default preservation patch can snapshot the changes non-destructively.

Terminal window
curl localhost:4040/orphaned-work

Loud Degradation

Section titled “Loud Degradation”

When a fallback activates (e.g., LLM provider unavailable, file write failed), it’s:

  • Logged with full context
  • Reported via Telegram
  • Surfaced in the health dashboard

Never silently swallowed. All catch blocks are audited with zero silent fallbacks allowed.

Unanswered Message Detection

Section titled “Unanswered Message Detection”

When context compaction drops a user message mid-session, the agent detects the gap and re-surfaces the unanswered message. No more silent drops during long sessions.