chat: /agents command is permanently unconfigured in production #1458

Closed
opened 2026-10-27 13:40:28 +00:00 by sam · 0 comments
Owner

internal/gateway.Router.Agents (AgentReader interface, AgentInfo{ID,Title,Status,Identity}) backs the /agents command (handleAgents, gateway.go:1127), and /agents is registered and advertised: in gateway.go's localCommands/localCommandSpecs (description: 'List tasks currently being worked'), and in internal/channels/telegram/commands.go's gatewayCommandSpecs (same description, published to Telegram's command menu and /help).

Verified via grep across internal/: Router.Agents is NEVER assigned outside of gateway_test.go's fakeAgentReader. None of the four composition-root call sites that build a Router (bootstrap.go's web/email/webhook routers, telegram_setup.go's buildTelegramRouter) ever set router.Agents. So in every real deployment, typing /agents in any channel returns the hardcoded fallback: 'Agent listing is not configured.' -- despite Telegram advertising it in its command menu with a description implying it works.

Found while implementing archie-core-wp9s (the /status vs /tasks split): the new /tasks command (gateway.ChatTaskLister-backed) covers almost exactly what /agents' AgentInfo{ID,Title,Status,Identity} shape was meant to show, just fuller (adds workflow/stage/age/park-reason). AgentReader/AgentInfo appear to be an earlier, abandoned attempt at the same feature that was never connected during wiring.

Sam's call, not resolved here: (a) wire AgentReader to a real implementation (e.g. an adapter over the same ListChatTasks path /tasks now uses, if /agents is meant to mean something distinct from /tasks -- e.g. actively-executing containers rather than all non-terminal store tasks), (b) delete /agents (AgentReader, AgentInfo, handleAgents, both command-spec registrations, and their tests) now that /tasks exists and covers the same ground, or (c) something else entirely if 'agents' was meant to be a different concept than 'tasks'. See docs/prds/status-health-surface.md's note on this for the /tasks cross-reference.

Acceptance criteria

A decision is recorded (wire, delete, or redefine) and /agents' advertised behavior in Telegram's menu/help matches what it actually does when invoked -- no command may be discoverable and described as functional while permanently returning a not-configured placeholder.

Notes

2026-09-19: recorded on behalf of archie-core-wp9s, whose acceptance criterion 'the command descriptions registered with the platform match what each actually does' is UNMET for /agents and cannot be met from that bead. Published on both surfaces as 'List tasks currently being worked', while Router.Agents is assigned nowhere (bootstrap.go, telegram_setup.go) so it always answers 'Agent listing is not configured'. Sam's call on wire/repurpose/delete; /tasks now covers most of the shape /agents was for.

Close reason

Closed on GitHub; syncing bead state


Imported from beads archie-core-mxls · GitHub #735 · type bug · priority P2 · created 2026-09-02 · closed 2026-09-26

internal/gateway.Router.Agents (AgentReader interface, AgentInfo{ID,Title,Status,Identity}) backs the /agents command (handleAgents, gateway.go:1127), and /agents is registered and advertised: in gateway.go's localCommands/localCommandSpecs (description: 'List tasks currently being worked'), and in internal/channels/telegram/commands.go's gatewayCommandSpecs (same description, published to Telegram's command menu and /help). Verified via grep across internal/: Router.Agents is NEVER assigned outside of gateway_test.go's fakeAgentReader. None of the four composition-root call sites that build a Router (bootstrap.go's web/email/webhook routers, telegram_setup.go's buildTelegramRouter) ever set router.Agents. So in every real deployment, typing /agents in any channel returns the hardcoded fallback: 'Agent listing is not configured.' -- despite Telegram advertising it in its command menu with a description implying it works. Found while implementing archie-core-wp9s (the /status vs /tasks split): the new /tasks command (gateway.ChatTaskLister-backed) covers almost exactly what /agents' AgentInfo{ID,Title,Status,Identity} shape was meant to show, just fuller (adds workflow/stage/age/park-reason). AgentReader/AgentInfo appear to be an earlier, abandoned attempt at the same feature that was never connected during wiring. Sam's call, not resolved here: (a) wire AgentReader to a real implementation (e.g. an adapter over the same ListChatTasks path /tasks now uses, if /agents is meant to mean something distinct from /tasks -- e.g. actively-executing containers rather than all non-terminal store tasks), (b) delete /agents (AgentReader, AgentInfo, handleAgents, both command-spec registrations, and their tests) now that /tasks exists and covers the same ground, or (c) something else entirely if 'agents' was meant to be a different concept than 'tasks'. See docs/prds/status-health-surface.md's note on this for the /tasks cross-reference. ### Acceptance criteria A decision is recorded (wire, delete, or redefine) and /agents' advertised behavior in Telegram's menu/help matches what it actually does when invoked -- no command may be discoverable and described as functional while permanently returning a not-configured placeholder. ### Notes 2026-09-19: recorded on behalf of archie-core-wp9s, whose acceptance criterion 'the command descriptions registered with the platform match what each actually does' is UNMET for /agents and cannot be met from that bead. Published on both surfaces as 'List tasks currently being worked', while Router.Agents is assigned nowhere (bootstrap.go, telegram_setup.go) so it always answers 'Agent listing is not configured'. Sam's call on wire/repurpose/delete; /tasks now covers most of the shape /agents was for. ### Close reason Closed on GitHub; syncing bead state --- _Imported from beads `archie-core-mxls` · GitHub #735 · type bug · priority P2 · created 2026-09-02 · closed 2026-09-26_
sam added the mediumbug labels 2026-10-27 13:40:28 +00:00
sam self-assigned this 2026-10-27 13:40:28 +00:00
sam closed this issue 2026-10-27 13:40:28 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1458