Telegram: separate task status from chat runtime status #896

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

Split Telegram task and runtime status into distinct commands. MVP from Sam:\n\n/tasks:\n- command name is exactly /tasks\n- show only when running tasks exist; when none are running, explain how to set up workflows for continuous development\n- let the user select a running task by its description/title; first verify task records actually carry usable titles/descriptions, otherwise treat that as a blocker\n\n/status:\n- show session details\n- show configured provider\n- show configured model\n- show installed plugins\n- Hermes-style session metadata is the reference direction; exact fields can expand later\n\nDo not mix task state into /status.

Acceptance Criteria

/tasks is the sole task-status command; it lists selectable running tasks by usable title/description, or gives workflow setup guidance when none run; implementation is blocked/escalated if task records lack usable titles. /status reports only chat/runtime state: session details, configured provider, configured model, and installed plugins. Task and runtime outputs do not mix. Telegram menu/help/executable parity and tests cover both commands.


Imported from beads archie-core-1786637499369-365-d0a0d56c · GitHub #386 · type bug · priority P2 · created 2026-08-08 · closed 2026-08-08

Split Telegram task and runtime status into distinct commands. MVP from Sam:\n\n/tasks:\n- command name is exactly /tasks\n- show only when running tasks exist; when none are running, explain how to set up workflows for continuous development\n- let the user select a running task by its description/title; first verify task records actually carry usable titles/descriptions, otherwise treat that as a blocker\n\n/status:\n- show session details\n- show configured provider\n- show configured model\n- show installed plugins\n- Hermes-style session metadata is the reference direction; exact fields can expand later\n\nDo not mix task state into /status. ### Acceptance Criteria /tasks is the sole task-status command; it lists selectable running tasks by usable title/description, or gives workflow setup guidance when none run; implementation is blocked/escalated if task records lack usable titles. /status reports only chat/runtime state: session details, configured provider, configured model, and installed plugins. Task and runtime outputs do not mix. Telegram menu/help/executable parity and tests cover both commands. --- _Imported from beads `archie-core-1786637499369-365-d0a0d56c` · GitHub #386 · type bug · priority P2 · created 2026-08-08 · closed 2026-08-08_
sam added the mediumbug labels 2026-10-27 13:38:11 +00:00
sam self-assigned this 2026-10-27 13:38:11 +00:00
sam closed this issue 2026-10-27 13:38:11 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#896