Harry Bayliss 0c960fa859 Clarify sub-agent reply routing in MCP tool descriptions
A sub-agent's reply to send_message lands in the caller's own pane
tagged [sub-agent:<name>], not in the sub-agent's output. The
descriptions for wait_for_pattern, send_message, both
timer_fire_when_idle_*, and the server-instructions preamble now
spell this out, along with the canonical send_message →
timer_fire_when_idle_any → read-own-pane pattern. help('readiness')
and help('coordination') updated to match. Previously agents reached
for wait_for_pattern on the sub-agent and deadlocked until timeout
because the reply had already been delivered to their own pane.
2026-05-15 16:08:07 +01:00
2026-05-14 16:37:46 +01:00
2026-05-14 16:03:49 +01:00
wip
2026-05-15 00:28:06 +01:00
wip
2026-05-15 00:28:06 +01:00
wip
2026-05-15 00:28:06 +01:00
2026-05-14 14:00:45 +01:00
2026-05-14 13:37:20 +01:00
2026-05-15 16:07:58 +01:00
Description
Terminal-based agent orchestration shell. Named after my dog.
3.1 MiB
v0.0.7 Latest
2026-05-18 13:02:46 +01:00
Languages
Go 99.6%
Makefile 0.4%