The Telegram responder currently calls runtime.Chat with MaxSteps=1 and no tool set. Email and webhook routers receive a nil responder. The central tool registry is empty/unconsumed; MCP transports are started without initialize/list/register/stop; the memory manager is not part of chat; skills and guardrails are not available to gateway turns. Replace the one-shot responder with one shared session-scoped conversational agent path used by Telegram, email, and webhook, preserving archie-core's daemon-owned safety boundaries.
Acceptance Criteria
A gateway turn can use approved built-in tools, configured MCP tools, memory, skills, compression, and guardrails through a multi-step agent loop; Telegram, email, and webhook share this path; tool transports are initialized, discovered, registered, and shut down; an end-to-end test proves an inbound message causes a tool call and a delivered reply.
Close reason
Closed on GitHub; syncing bead state
Imported from beads archie-core-1786637497724-301-9a5dee08 · GitHub #322 · type feature · priority P2 · created 2026-08-08 · closed 2026-09-26
The Telegram responder currently calls runtime.Chat with MaxSteps=1 and no tool set. Email and webhook routers receive a nil responder. The central tool registry is empty/unconsumed; MCP transports are started without initialize/list/register/stop; the memory manager is not part of chat; skills and guardrails are not available to gateway turns. Replace the one-shot responder with one shared session-scoped conversational agent path used by Telegram, email, and webhook, preserving archie-core's daemon-owned safety boundaries.
### Acceptance Criteria
A gateway turn can use approved built-in tools, configured MCP tools, memory, skills, compression, and guardrails through a multi-step agent loop; Telegram, email, and webhook share this path; tool transports are initialized, discovered, registered, and shut down; an end-to-end test proves an inbound message causes a tool call and a delivered reply.
### Close reason
Closed on GitHub; syncing bead state
---
_Imported from beads `archie-core-1786637497724-301-9a5dee08` · GitHub #322 · type feature · priority P2 · created 2026-08-08 · closed 2026-09-26_
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.
The Telegram responder currently calls runtime.Chat with MaxSteps=1 and no tool set. Email and webhook routers receive a nil responder. The central tool registry is empty/unconsumed; MCP transports are started without initialize/list/register/stop; the memory manager is not part of chat; skills and guardrails are not available to gateway turns. Replace the one-shot responder with one shared session-scoped conversational agent path used by Telegram, email, and webhook, preserving archie-core's daemon-owned safety boundaries.
Acceptance Criteria
A gateway turn can use approved built-in tools, configured MCP tools, memory, skills, compression, and guardrails through a multi-step agent loop; Telegram, email, and webhook share this path; tool transports are initialized, discovered, registered, and shut down; an end-to-end test proves an inbound message causes a tool call and a delivered reply.
Close reason
Closed on GitHub; syncing bead state
Imported from beads
archie-core-1786637497724-301-9a5dee08· GitHub #322 · type feature · priority P2 · created 2026-08-08 · closed 2026-09-26