You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
squad watch --interval 5 "Nick, Run scheduled tasks" silently drops the quoted message. Ralph runs its normal polling loop with no indication the message was ignored.
Users expect the message to be routed to the named agent on each cycle, because direct addressing (Nick, do something) works in interactive sessions.
Root Cause
In cli-entry.ts lines 322-329, only --interval is parsed. Extra args are silently ignored.
Fix
Detect extra args and warn:
Warning: Watch mode does not route messages. Ignoring: "Nick, Run scheduled tasks"
To address Nick directly, use an interactive session.
Hey — this behavior has been investigated and a fix is in PR #704.
What's happening:squad watch is a triage polling loop (Ralph), not a message router. The quoted message ("Nick, Run scheduled tasks") was silently ignored — watch mode only parses --interval.
⚠️ Watch mode does not route messages to agents. Ignoring: "Nick, Run scheduled tasks"
To address an agent directly, use an interactive session instead.
Docs updated — ralph.md and cli.md now clearly explain watch vs direct addressing
How to do what you want:
Direct agent addressing works in interactive sessions: squad → then Nick, Run scheduled tasks
Recurring triage: squad watch --interval 5 polls GitHub and routes issues based on squad:{member} labels
Route to Nick specifically: create a GitHub issue, add the squad:nick label, and squad watch will triage it to Nick on the next cycle
Update: PR #704 was closed without merge, so this is still unfixed.
The fix approach from #704 (warn on unused message args) was a partial solution. The root cause is that the watch command passes the prompt as a CLI argument which breaks on quotes/special chars.
The proper fix is to write the prompt to a temp file and pass it via -p @tempfile\ instead of as an inline argument. PR #830 (next-gen watch) may have changed the execution path — need to verify if this is still reproducible on insider.
Activity
github-actions commentedon Mar 30, 2026
📋 Assigned to EECOM (Core Dev)
Issue: #703 — fix(cli): squad watch silently ignores quoted message
EECOM will pick this up in the next Copilot session.
github-actions commentedon Mar 30, 2026
🏗️ Squad Triage — Flight (Lead)
Issue: #703 — fix(cli): squad watch silently ignores quoted message
Assigned to: FIDO (Quality Owner)
Reason: Issue relates to testing/quality work
@copilot evaluation: No strong capability match — routed to squad member.
Team roster:
squad:flightsquad:proceduressquad:eecomsquad:fidosquad:paosquad:capcomsquad:controlsquad:surgeonsquad:boostersquad:gncsquad:networksquad:retrosquad:incosquad:guidosquad:telemetrysquad:voxsquad:dskysquad:simssquad:handbooksquad:ralphsquad:copilotfix(cli): warn when squad watch receives unused message args (#703)
docs: clarify that squad watch does not route messages to agents
tamirdresher commentedon Mar 30, 2026
Hey — this behavior has been investigated and a fix is in PR #704.
What's happening:
squad watchis a triage polling loop (Ralph), not a message router. The quoted message ("Nick, Run scheduled tasks") was silently ignored — watch mode only parses--interval.The fix (PR #704):
How to do what you want:
squad→ thenNick, Run scheduled taskssquad watch --interval 5polls GitHub and routes issues based onsquad:{member}labelssquad:nicklabel, andsquad watchwill triage it to Nick on the next cycleSee PR #704 for the full fix.
diberry commentedon Mar 31, 2026
🔄 Ralph status: PR #704 addresses this. Needs rebase (behind dev). Small fix — 3 files, warning-only change.
docs: add changelog entry for #703 squad watch silent arg ignore fix
fix(cli): warn when squad watch receives unused message args (#703)
docs: clarify that squad watch does not route messages to agents
docs: add changelog entry for #703 squad watch silent arg ignore fix
3 remaining items
fix(cli): warn when squad watch receives unused message args (#703)
fix(cli): warn when squad watch receives unused message args (#703)
fix(cli): warn when squad watch receives unused message args (#703)
feat(coordinator): compaction recovery + restraint rules + result per…
fix(cli): warn when squad watch receives unused message args (#703)
feat(coordinator): compaction recovery + restraint rules + result per…
feat(coordinator): compaction recovery + restraint rules + result per…
feat(coordinator): compaction recovery + restraint rules + result per…
tamirdresher commentedon Apr 12, 2026
Update: PR #704 was closed without merge, so this is still unfixed.
The fix approach from #704 (warn on unused message args) was a partial solution. The root cause is that the watch command passes the prompt as a CLI argument which breaks on quotes/special chars.
The proper fix is to write the prompt to a temp file and pass it via -p @tempfile\ instead of as an inline argument. PR #830 (next-gen watch) may have changed the execution path — need to verify if this is still reproducible on insider.
bradygaster commentedon Apr 12, 2026
Closing as duplicate of #874 — both trace back to the obsolete \gh copilot --message\ flag. See #874 for tracking the fix.
fix(cli): warn when squad watch receives unused message args (github#703
feat(coordinator): compaction recovery + restraint rules + result per…