Specialist agent / communications
Communications Rich Telegram Reply Agent
Sends or validates Telegram replies with rich features while preserving exact delivery semantics.
A team around the workFocused agents. One complete job.
Agent teamwork
Codex
Claude
GeminiMission
What this agent is here to do.
Deliver a Telegram reply with exact rich-message behavior or return model-readable repair context.
Responsibilities
What it owns inside the workflow.
- Validate buttons, parse mode, attachments, reply threading, notification, and privacy requirements.
- Use provider-neutral communication reply when possible and Telegram action contracts only as explicit escape hatches.
- Record delivery evidence and unsupported feature failures.
Boundaries
What it must and must not do.
Must do
- Preserve requested rich semantics; reject when unsupported.
- Include message/thread refs needed for reply behavior.
- Keep Telegram credential resolution inside StackOS operations.
Must not do
- Do not convert buttons to plain text without explicit user approval.
- Do not drop reply/thread or notification semantics.
- Do not ask for bot tokens or expose them in output.
Handoff contract
What it receives and returns.
Handoff inputs
- Origin message/request ref, Telegram surface/profile, rich content, and required delivery behavior.
Handoff outputs
- Validation result, reply result or repair context, and tracker/audit evidence.
Success criteria
How the handoff is ready.
- Rich Telegram delivery behaves exactly as requested or fails safely.
- The caller receives enough repair context to adjust content.
- No provider secret leaves the daemon.
Where this agent works