Skip to content

A message the supervisor routed to the owner as a question isn't unanswered - #129

Merged
hhff merged 1 commit into
mainfrom
routed-messages
Nov 6, 2026
Merged

hhff merged 1 commit into
mainfrom
routed-messages

Conversation

@hhff

@hhff hhff commented Nov 6, 2026

Copy link
Copy Markdown
Member

What

  • devteam.mjs: a new helper, handledMessages(). A message counts as handled when a reply cites it (--re) or a question cites it (ask --re). It's used by:
    • metrics (unanswered-message and reply waits);
    • the dashboard's open_messages;
    • messages --open;
    • a session's open asks;
    • the phase warning.
  • Test: a worker's blocked message is open until the supervisor asks the owner a question that cites it, then it isn't.

Why

Stacks showed six unanswered-message findings, up to 15 hours old. Each had already been routed to the owner as a question citing it (re: m-…), so the planner was waiting on the owner, not the supervisor (that's what blocked-on-owner shows). Meanwhile Stacks' supervisor rightly reported no pending worker messages.

Migration

None.

🤖 Generated with Claude Code

…swered

When the supervisor answers a worker's or planner's message by asking the
owner (ask --re <message>), the message now waits on the owner, which its
question shows. metrics still counted it as unanswered-message, the dashboard
listed it as open, and messages --open kept it: Stacks showed six messages
open for up to 15 hours whose questions were already in the owner's Inbox,
while its supervisor rightly reported no worker messages pending. A question
that cites a message now handles it, like a reply does.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@hhff

hhff commented Nov 6, 2026

Copy link
Copy Markdown
Member Author

Merging (upstream loop).

@hhff
hhff merged commit d5a9f3a into main Nov 6, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant