No chat/messaging code exists today (confirmed: grep for Telegram across the repo returns nothing outside a skills-PRD example). Define a chat channel plugin interface (parallel to forge.Forge) and implement Telegram as the first channel, with a read-only /status command reading daemon/task state. Full spawn/control action parity (the write side of the interview requirement) is split into archie-core-abg.13 since it needs its own task-creation semantics for chat-initiated (non-issue-backed) tasks. Per docs/prds/multi-agent-collaboration.md phase C.
Acceptance Criteria
A chat.Channel interface exists (Name, Listen, Send or similar) implemented by a Telegram channel using the Bot HTTP API (long polling, no new heavy dependency). Sam can message the bot /status and get a real answer about current daemon/task state. Channel is wired into daemon startup behind an optional [chat] config block (absent = disabled, matching the [nats]/[containers] pattern).
Imported from beads archie-core-1786637498113-315-a82884f8 · GitHub #336 · type feature · priority P2 · created 2026-08-08 · closed 2026-08-08
No chat/messaging code exists today (confirmed: grep for Telegram across the repo returns nothing outside a skills-PRD example). Define a chat channel plugin interface (parallel to forge.Forge) and implement Telegram as the first channel, with a read-only /status command reading daemon/task state. Full spawn/control action parity (the write side of the interview requirement) is split into archie-core-abg.13 since it needs its own task-creation semantics for chat-initiated (non-issue-backed) tasks. Per docs/prds/multi-agent-collaboration.md phase C.
### Acceptance Criteria
A chat.Channel interface exists (Name, Listen, Send or similar) implemented by a Telegram channel using the Bot HTTP API (long polling, no new heavy dependency). Sam can message the bot /status and get a real answer about current daemon/task state. Channel is wired into daemon startup behind an optional [chat] config block (absent = disabled, matching the [nats]/[containers] pattern).
---
_Imported from beads `archie-core-1786637498113-315-a82884f8` · GitHub #336 · type feature · priority P2 · created 2026-08-08 · closed 2026-08-08_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
No chat/messaging code exists today (confirmed: grep for Telegram across the repo returns nothing outside a skills-PRD example). Define a chat channel plugin interface (parallel to forge.Forge) and implement Telegram as the first channel, with a read-only /status command reading daemon/task state. Full spawn/control action parity (the write side of the interview requirement) is split into archie-core-abg.13 since it needs its own task-creation semantics for chat-initiated (non-issue-backed) tasks. Per docs/prds/multi-agent-collaboration.md phase C.
Acceptance Criteria
A chat.Channel interface exists (Name, Listen, Send or similar) implemented by a Telegram channel using the Bot HTTP API (long polling, no new heavy dependency). Sam can message the bot /status and get a real answer about current daemon/task state. Channel is wired into daemon startup behind an optional [chat] config block (absent = disabled, matching the [nats]/[containers] pattern).
Imported from beads
archie-core-1786637498113-315-a82884f8· GitHub #336 · type feature · priority P2 · created 2026-08-08 · closed 2026-08-08