Concepts
Transports
Platform abstraction layer. Telegram/GitHub-specific send/edit/typing/parse. 50 LOC per platform. Reuses 2400+ agent LOC.
TL;DR: Abstracts platform APIs. Agents call transport.send(). Handles Telegram 4096-char splits, GitHub comments/reactions.
Table of Contents
Interface
Core methods agents use:
Telegram Impl
Splits >4096 chars. Markdown fallback. Typing indicator.
apps/telegram-bot/src/transport.ts
GitHub Impl
Comments on issues/PRs. Reactions. XML context blocks.
apps/github-bot/src/transport.ts
Comparison
| Feature | Telegram | GitHub |
|---|---|---|
| send | 4096-char split/Markdown | Comment on issue/PR |
| edit | editMessageText | updateComment |
| typing | sendChatAction | N/A |
| parse | webhook -> text/chatId | Payload -> XML context |
| LOC | ~50 | ~50 |
Reduces duplication 6x!
Quiz: Transports vs Agents?
A: Transports handle platform APIs; Agents contain logic ✅
Related: Router -> | Deployment ->
Next: Memory MCP ->