---
compaction_strategy: structured
---

# omnius-telegram-docs

Use Omnius Telegram docs for bridge setup, scoped persona state, public tools, reply preferences, and delivery failures.

## Triggers

- Omnius Telegram
- /telegram
- Telegram bridge
- Telegram persona
- Telegram reply preferences
- Telegram failure feedback
- public Telegram tools

## Workflow

1. Read `docs/guides/telegram.md`.
2. For media generation from Telegram, read `docs/guides/media-generation.md`.
3. For public-surface safety, read `docs/operations/security-and-remote-access.md`.
4. Preserve user, chat, reply, and media scope when answering implementation questions.

## Key Facts

- Telegram state is scoped by user and group.
- Reply preferences are durable persona state, not regex routing.
- Raw platform/tool failures should be fed back as observations, not hardcoded string rules.
