Sam's words: "/status is fucking annoying. I'm invoking an actual status update, receiving minor information as well as shit I can get elsewhere. What's worse is that the /tasks command is meant to be for viewing the running agents, not /status."
Observed 2026-08-24, the entire output of /status was:
Two problems in one screen. It answers the question /tasks should own (what work is in flight), and it answers it thinly -- a count, with no task identity, no stage, no age, nothing actionable. Everything else it shows is static configuration available elsewhere. Later in the same session /status reported "Running: 1" for a task that was stuck in a failure loop and going nowhere, which is the specific case where a bare count actively misleads.
The division of labour to restore
/tasks owns WORK: what is running, what is parked and why, what needs the operator. This is the live view of the agents, and it is where task identity, workflow, stage, attempt and age belong.
/status owns HEALTH: is the daemon well. Broker connectivity, provider reachability, channel state, container pool, queue depth, last poll, version. The things an operator checks when something feels wrong and which are NOT visible elsewhere in chat.
Neither should be a thin duplicate of the other, and neither should pad itself with static config the operator already knows.
Related, decide together
archie-core-624 (task_action chat tool) adds operator verbs for tasks. /tasks is the natural surface for discovering the ids those verbs act on, so the two should be designed as one flow: see the work, then act on it. Check what internal/gateway/task_tools.go already returns before adding a new query path -- ChatTaskSummary may already carry most of what /tasks should show.
Steps to Reproduce
Run /status in chat with tasks parked and one running.
Observe a parked/running COUNT plus provider and model, with no way to identify or act on any task.
Run /tasks and observe the overlap.
Acceptance Criteria
/tasks shows the live work with enough identity and state to act on it (id, title, status, workflow/stage, age) and is the documented way to view running agents; /status reports daemon health that is not obtainable elsewhere in chat and does not duplicate the task list; a task that is running but not progressing is distinguishable from one making progress; the command descriptions registered with the platform match what each actually does.
Notes
Phase 1 shipped 2026-09-03 (commit 370b0ee): /tasks is a new command (identity, title, status, workflow/stage, age via UpdatedAt, attempt once retried, parked reason), sorted actionable-first; /status's itemized per-status task counts replaced with one aggregate 'Queue: N in flight (...)' line (running/waiting/parked only). Runtime (provider/model) left in place for now -- open question below.
Phase 2 (broker connectivity, provider reachability, channel state, container pool, last poll) is NOT implemented -- proposed resolution in docs/prds/status-health-surface.md, verified against the real tree and split into cheap (broker connectivity via nats.Conn.Status(), container pool's already-tracked active count, a new last-poll timestamp) vs needs-a-decision (provider reachability: live probe vs last-known-outcome; channel state: likely via the existing ChannelManager). Awaiting Sam's sign-off before implementing Phase 2 -- do not close this bead until Phase 2 lands or is explicitly descoped.
Also found while doing this (filed separately, not folded in): archie-core-mxls -- /agents is registered and advertised (Telegram command menu + /help) but Router.Agents is never wired by any composition-root call site, so it always answers 'not configured' in production. /tasks now covers most of what /agents' shape was for; Sam's call whether to wire/delete/redefine /agents.
2026-09-19: Phase 2 authorised by Sam; implementation delegated to a subagent in an isolated worktree. Parent session holds the claim and will verify + close.
SHIPPED for review: PR #892, branch feat/wp9s-status-health-surface, commit 36c6a748 (21 files, +1616/-73). INDEPENDENTLY VERIFIED by the parent session: task check exit 0 on that exact commit in a fresh worktree (clean tree after); internal/gateway/health.go and app/archied/status_health.go read line by line — the 'truthful or absent' rule is structural (nil source -> section omitted, no invented zeroes), and my own mutation (commenting out outcomes.record at the sendChatTurn choke point) fails TestSendChatTurnRecordsEachCallOutcome, proving the chat-model line is not dead wiring. OPEN, recorded in the PRD: (1) Runtime block left in /status — product call; (2) health is per-process, not pooled across daemon and standalone Gateway; (3) channel Detail can be stale after recovery (producer split, out of scope). UNMET ACCEPTANCE ELEMENT: '/agents' is published as 'List tasks currently being worked' but Router.Agents is assigned nowhere, so it always answers 'not configured' — left to archie-core-mxls by design. Not closing until the PR merges.
Close reason
LANDED on main: merged as 800352a6 (PR #892). /status now reports daemon health (broker, container pool, channel state, last-known chat-model outcome, last poll) instead of duplicating a thin task list; /tasks owns the work view; command copy fixed on both published surfaces with a drift guard. Independent verification: task check exit 0 re-run by the parent session on that exact commit in a fresh worktree; internal/gateway/health.go and app/archied/status_health.go read line by line (the 'truthful or absent' rule is structural - nil source omits the section, no invented zeroes); and the parent's own mutation (commenting out outcomes.record at the sendChatTurn choke point) fails TestSendChatTurnRecordsEachCallOutcome, proving the chat-model line is live wiring. Maintainer decisions recorded in docs/prds/status-health-surface.md: the Runtime (provider/model) block stays, and health stays per-process. One acceptance element deferred to archie-core-mxls: /agents is published as 'List tasks currently being worked' while Router.Agents is assigned nowhere (noted on that bead).
Imported from beads archie-core-wp9s · GitHub #631 · type bug · priority P2 · created 2026-08-24 · closed 2026-09-19
Sam's words: "/status is fucking annoying. I'm invoking an actual status update, receiving minor information as well as shit I can get elsewhere. What's worse is that the /tasks command is meant to be for viewing the running agents, not /status."
Observed 2026-08-24, the entire output of /status was:
Tasks Parked: 2
Runtime Provider: OpenAI Model: openai/gpt-5.6-luna
Two problems in one screen. It answers the question /tasks should own (what work is in flight), and it answers it thinly -- a count, with no task identity, no stage, no age, nothing actionable. Everything else it shows is static configuration available elsewhere. Later in the same session /status reported "Running: 1" for a task that was stuck in a failure loop and going nowhere, which is the specific case where a bare count actively misleads.
## The division of labour to restore
- `/tasks` owns WORK: what is running, what is parked and why, what needs the operator. This is the live view of the agents, and it is where task identity, workflow, stage, attempt and age belong.
- `/status` owns HEALTH: is the daemon well. Broker connectivity, provider reachability, channel state, container pool, queue depth, last poll, version. The things an operator checks when something feels wrong and which are NOT visible elsewhere in chat.
Neither should be a thin duplicate of the other, and neither should pad itself with static config the operator already knows.
## Related, decide together
archie-core-624 (task_action chat tool) adds operator verbs for tasks. /tasks is the natural surface for discovering the ids those verbs act on, so the two should be designed as one flow: see the work, then act on it. Check what internal/gateway/task_tools.go already returns before adding a new query path -- ChatTaskSummary may already carry most of what /tasks should show.
## Steps to Reproduce
1. Run /status in chat with tasks parked and one running.
2. Observe a parked/running COUNT plus provider and model, with no way to identify or act on any task.
3. Run /tasks and observe the overlap.
## Acceptance Criteria
/tasks shows the live work with enough identity and state to act on it (id, title, status, workflow/stage, age) and is the documented way to view running agents; /status reports daemon health that is not obtainable elsewhere in chat and does not duplicate the task list; a task that is running but not progressing is distinguishable from one making progress; the command descriptions registered with the platform match what each actually does.
### Notes
Phase 1 shipped 2026-09-03 (commit 370b0ee): /tasks is a new command (identity, title, status, workflow/stage, age via UpdatedAt, attempt once retried, parked reason), sorted actionable-first; /status's itemized per-status task counts replaced with one aggregate 'Queue: N in flight (...)' line (running/waiting/parked only). Runtime (provider/model) left in place for now -- open question below.
Phase 2 (broker connectivity, provider reachability, channel state, container pool, last poll) is NOT implemented -- proposed resolution in docs/prds/status-health-surface.md, verified against the real tree and split into cheap (broker connectivity via nats.Conn.Status(), container pool's already-tracked active count, a new last-poll timestamp) vs needs-a-decision (provider reachability: live probe vs last-known-outcome; channel state: likely via the existing ChannelManager). Awaiting Sam's sign-off before implementing Phase 2 -- do not close this bead until Phase 2 lands or is explicitly descoped.
Also found while doing this (filed separately, not folded in): archie-core-mxls -- /agents is registered and advertised (Telegram command menu + /help) but Router.Agents is never wired by any composition-root call site, so it always answers 'not configured' in production. /tasks now covers most of what /agents' shape was for; Sam's call whether to wire/delete/redefine /agents.
2026-09-19: Phase 2 authorised by Sam; implementation delegated to a subagent in an isolated worktree. Parent session holds the claim and will verify + close.
SHIPPED for review: PR #892, branch feat/wp9s-status-health-surface, commit 36c6a748 (21 files, +1616/-73). INDEPENDENTLY VERIFIED by the parent session: task check exit 0 on that exact commit in a fresh worktree (clean tree after); internal/gateway/health.go and app/archied/status_health.go read line by line — the 'truthful or absent' rule is structural (nil source -> section omitted, no invented zeroes), and my own mutation (commenting out outcomes.record at the sendChatTurn choke point) fails TestSendChatTurnRecordsEachCallOutcome, proving the chat-model line is not dead wiring. OPEN, recorded in the PRD: (1) Runtime block left in /status — product call; (2) health is per-process, not pooled across daemon and standalone Gateway; (3) channel Detail can be stale after recovery (producer split, out of scope). UNMET ACCEPTANCE ELEMENT: '/agents' is published as 'List tasks currently being worked' but Router.Agents is assigned nowhere, so it always answers 'not configured' — left to archie-core-mxls by design. Not closing until the PR merges.
### Close reason
LANDED on main: merged as 800352a6 (PR #892). /status now reports daemon health (broker, container pool, channel state, last-known chat-model outcome, last poll) instead of duplicating a thin task list; /tasks owns the work view; command copy fixed on both published surfaces with a drift guard. Independent verification: task check exit 0 re-run by the parent session on that exact commit in a fresh worktree; internal/gateway/health.go and app/archied/status_health.go read line by line (the 'truthful or absent' rule is structural - nil source omits the section, no invented zeroes); and the parent's own mutation (commenting out outcomes.record at the sendChatTurn choke point) fails TestSendChatTurnRecordsEachCallOutcome, proving the chat-model line is live wiring. Maintainer decisions recorded in docs/prds/status-health-surface.md: the Runtime (provider/model) block stays, and health stays per-process. One acceptance element deferred to archie-core-mxls: /agents is published as 'List tasks currently being worked' while Router.Agents is assigned nowhere (noted on that bead).
---
_Imported from beads `archie-core-wp9s` · GitHub #631 · type bug · priority P2 · created 2026-08-24 · closed 2026-09-19_
sam
added the mediumbug labels 2026-10-27 13:41:14 +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.
Sam's words: "/status is fucking annoying. I'm invoking an actual status update, receiving minor information as well as shit I can get elsewhere. What's worse is that the /tasks command is meant to be for viewing the running agents, not /status."
Observed 2026-08-24, the entire output of /status was:
Tasks Parked: 2
Runtime Provider: OpenAI Model: openai/gpt-5.6-luna
Two problems in one screen. It answers the question /tasks should own (what work is in flight), and it answers it thinly -- a count, with no task identity, no stage, no age, nothing actionable. Everything else it shows is static configuration available elsewhere. Later in the same session /status reported "Running: 1" for a task that was stuck in a failure loop and going nowhere, which is the specific case where a bare count actively misleads.
The division of labour to restore
/tasksowns WORK: what is running, what is parked and why, what needs the operator. This is the live view of the agents, and it is where task identity, workflow, stage, attempt and age belong./statusowns HEALTH: is the daemon well. Broker connectivity, provider reachability, channel state, container pool, queue depth, last poll, version. The things an operator checks when something feels wrong and which are NOT visible elsewhere in chat.Neither should be a thin duplicate of the other, and neither should pad itself with static config the operator already knows.
Related, decide together
archie-core-624 (task_action chat tool) adds operator verbs for tasks. /tasks is the natural surface for discovering the ids those verbs act on, so the two should be designed as one flow: see the work, then act on it. Check what internal/gateway/task_tools.go already returns before adding a new query path -- ChatTaskSummary may already carry most of what /tasks should show.
Steps to Reproduce
Acceptance Criteria
/tasks shows the live work with enough identity and state to act on it (id, title, status, workflow/stage, age) and is the documented way to view running agents; /status reports daemon health that is not obtainable elsewhere in chat and does not duplicate the task list; a task that is running but not progressing is distinguishable from one making progress; the command descriptions registered with the platform match what each actually does.
Notes
Phase 1 shipped 2026-09-03 (commit 370b0ee): /tasks is a new command (identity, title, status, workflow/stage, age via UpdatedAt, attempt once retried, parked reason), sorted actionable-first; /status's itemized per-status task counts replaced with one aggregate 'Queue: N in flight (...)' line (running/waiting/parked only). Runtime (provider/model) left in place for now -- open question below.
Phase 2 (broker connectivity, provider reachability, channel state, container pool, last poll) is NOT implemented -- proposed resolution in docs/prds/status-health-surface.md, verified against the real tree and split into cheap (broker connectivity via nats.Conn.Status(), container pool's already-tracked active count, a new last-poll timestamp) vs needs-a-decision (provider reachability: live probe vs last-known-outcome; channel state: likely via the existing ChannelManager). Awaiting Sam's sign-off before implementing Phase 2 -- do not close this bead until Phase 2 lands or is explicitly descoped.
Also found while doing this (filed separately, not folded in): archie-core-mxls -- /agents is registered and advertised (Telegram command menu + /help) but Router.Agents is never wired by any composition-root call site, so it always answers 'not configured' in production. /tasks now covers most of what /agents' shape was for; Sam's call whether to wire/delete/redefine /agents.
2026-09-19: Phase 2 authorised by Sam; implementation delegated to a subagent in an isolated worktree. Parent session holds the claim and will verify + close.
SHIPPED for review: PR #892, branch feat/wp9s-status-health-surface, commit 36c6a748 (21 files, +1616/-73). INDEPENDENTLY VERIFIED by the parent session: task check exit 0 on that exact commit in a fresh worktree (clean tree after); internal/gateway/health.go and app/archied/status_health.go read line by line — the 'truthful or absent' rule is structural (nil source -> section omitted, no invented zeroes), and my own mutation (commenting out outcomes.record at the sendChatTurn choke point) fails TestSendChatTurnRecordsEachCallOutcome, proving the chat-model line is not dead wiring. OPEN, recorded in the PRD: (1) Runtime block left in /status — product call; (2) health is per-process, not pooled across daemon and standalone Gateway; (3) channel Detail can be stale after recovery (producer split, out of scope). UNMET ACCEPTANCE ELEMENT: '/agents' is published as 'List tasks currently being worked' but Router.Agents is assigned nowhere, so it always answers 'not configured' — left to archie-core-mxls by design. Not closing until the PR merges.
Close reason
LANDED on main: merged as
800352a6(PR #892). /status now reports daemon health (broker, container pool, channel state, last-known chat-model outcome, last poll) instead of duplicating a thin task list; /tasks owns the work view; command copy fixed on both published surfaces with a drift guard. Independent verification: task check exit 0 re-run by the parent session on that exact commit in a fresh worktree; internal/gateway/health.go and app/archied/status_health.go read line by line (the 'truthful or absent' rule is structural - nil source omits the section, no invented zeroes); and the parent's own mutation (commenting out outcomes.record at the sendChatTurn choke point) fails TestSendChatTurnRecordsEachCallOutcome, proving the chat-model line is live wiring. Maintainer decisions recorded in docs/prds/status-health-surface.md: the Runtime (provider/model) block stays, and health stays per-process. One acceptance element deferred to archie-core-mxls: /agents is published as 'List tasks currently being worked' while Router.Agents is assigned nowhere (noted on that bead).Imported from beads
archie-core-wp9s· GitHub #631 · type bug · priority P2 · created 2026-08-24 · closed 2026-09-19