# Upgrade Guide — v0.23.2

<!-- bump: patch -->

## What Changed

**Session respawn loop fixed — spawn-in-progress guard + user-visible failure messages.**

Previously, when a session died and kept failing to restart (due to session limit, quota exhaustion, or other errors), the system entered a silent respawn loop:
- Each incoming Telegram message triggered a new respawn attempt
- Respawn failures were only logged to console — never reported to the user
- The user saw repeated "🔄 Session restarting — message queued" messages with no explanation

Two fixes:

1. **Spawn-in-progress guard**: A per-topic lock prevents multiple concurrent spawn attempts for the same topic. If a spawn is already in progress, subsequent messages receive "Session is still starting up — please wait a moment" instead of triggering another spawn.

2. **Failure reporting**: When a respawn fails, the user now receives a Telegram message explaining what happened:
   - Session limit errors: "❌ Session restart failed — session limit reached. Close an existing session or increase maxSessions in your config, then try again."
   - Other errors: "❌ Session restart failed. Try sending your message again in a moment."

## What to Tell Your User

- **Session restart reliability**: "When my session dies and I can't restart it, I'll now tell you exactly what went wrong — including if you've hit the session limit — instead of just silently failing. Expect clearer error messages."

## Summary of New Capabilities

| Capability | How to Use |
|-----------|-----------|
| Respawn failure messages | Automatic — user receives error via Telegram when restart fails |
| Session limit error guidance | Automatic — specific message when session limit prevents restart |
| Spawn deduplication | Automatic — rapid messages during startup no longer create duplicate sessions |
