# Anita Gateway Restart (Jul 7, 2026)

Anita's Hermes gateway stopped working when the `restart-anita-gateway.sh` cron executed. The restart succeeded but the new gateway started with **no Telegram connection** because:

## Root cause 1: Bot token was wrong

The main gateway's Telegram bot token was in Anita's `.env` instead of her own bot token. Two gateways can't share the same bot token. When the restart happened, it tried to use the main token and got `"Telegram bot token already in use (PID 1164)"`.

**Fix:** Anita's `.env` must have its own `TELEGRAM_BOT_TOKEN` (from her own BotFather creation), not a copy of the main token.

## Root cause 2: Allowed users list blocked messages

Anita's `TELEGRAM_ALLOWED_USERS` only had Germaine's ID (`5813481339`). When Anita sent a message, the gateway logged `Blocked unauthorized user 8200236464`. She could send messages but they were silently dropped.

**Fix:** `TELEGRAM_ALLOWED_USERS=5813481339,8200236464`

## Gateway restart limitation

`hermes gateway restart` cannot be run from within the gateway process itself — it kills the process before the command completes. Restarting Anita's gateway had to be done from a separate shell or via cron.

## Data preservation

Anita's session database (`/root/.hermes/profiles/anita/state.db`, 16MB, 9 sessions) survived the restart intact. Gateway restarts do not touch the SQLite session store.

## Needed for Anita to work

1. Correct TELEGRAM_BOT_TOKEN in her `.env`
2. TELEGRAM_ALLOWED_USERS includes her Telegram ID (8200236464)
3. Gateway independently started (not sharing main gateway's bot)
