The information is compressed into raw key/value text, and task state, provider, and model details are not clearly separated.
Desired behaviour
Present status information in a compact, polished, mobile-friendly format suitable for Telegram. It should make the most important state immediately obvious and visually separate task and runtime/model information.
The exact wording and icons can follow existing Telegram UI conventions.
Acceptance criteria
/status has a clear heading and grouped sections.
Task states are shown on separate, readable lines.
Provider and model are clearly separated.
The response remains concise and readable on mobile.
Empty and unavailable values have a graceful fallback.
Tests cover the formatted response, including multiple task states and missing runtime details.
Close reason
Closed
Imported from beads archie-core-1786748942519-17-5999d55b · GitHub #512 · type task · priority P2 · created 2026-08-14 · closed 2026-08-15
## Problem
The `/status` command response is functional but lacks polish and is difficult to scan. The current output looks like:
```text
Task status: parked:2
Provider: deepseek Model: deepseek/deepseek-v4-pro
```
The information is compressed into raw key/value text, and task state, provider, and model details are not clearly separated.
## Desired behaviour
Present status information in a compact, polished, mobile-friendly format suitable for Telegram. It should make the most important state immediately obvious and visually separate task and runtime/model information.
For example:
```text
📊 Archie status
Tasks
⏸ Parked:2
Runtime
Provider: OpenAI
Model: openai/gpt-5.6-luna
```
The exact wording and icons can follow existing Telegram UI conventions.
## Acceptance criteria
- `/status` has a clear heading and grouped sections.
- Task states are shown on separate, readable lines.
- Provider and model are clearly separated.
- The response remains concise and readable on mobile.
- Empty and unavailable values have a graceful fallback.
- Tests cover the formatted response, including multiple task states and missing runtime details.
### Close reason
Closed
---
_Imported from beads `archie-core-1786748942519-17-5999d55b` · GitHub #512 · type task · priority P2 · created 2026-08-14 · closed 2026-08-15_
sam
added the mediumtask labels 2026-10-27 13:38:31 +00:00
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.
Problem
The
/statuscommand response is functional but lacks polish and is difficult to scan. The current output looks like:The information is compressed into raw key/value text, and task state, provider, and model details are not clearly separated.
Desired behaviour
Present status information in a compact, polished, mobile-friendly format suitable for Telegram. It should make the most important state immediately obvious and visually separate task and runtime/model information.
For example:
The exact wording and icons can follow existing Telegram UI conventions.
Acceptance criteria
/statushas a clear heading and grouped sections.Close reason
Closed
Imported from beads
archie-core-1786748942519-17-5999d55b· GitHub #512 · type task · priority P2 · created 2026-08-14 · closed 2026-08-15