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
#44 proposes an agent that works the repo's issue queue automatically: triage → plan → draft PR.
That pipeline is the skill chain — /triage, /to-spec, /to-tickets, /implement — which
makes #44 the AFK end of the same spectrum this map's other tickets sit on, with the wayfinder panel
as the HITL end.
It is sequenced last deliberately, and its verdict may legitimately be defer.
Once the panel, invocation and routing are settled, decide:
Question
#44 proposes an agent that works the repo's issue queue automatically: triage → plan → draft PR.
That pipeline is the skill chain —
/triage,/to-spec,/to-tickets,/implement— whichmakes #44 the AFK end of the same spectrum this map's other tickets sit on, with the wayfinder panel
as the HITL end.
It is sequenced last deliberately, and its verdict may legitimately be defer.
Once the panel, invocation and routing are settled, decide:
working skill invocation?
off to the loops map ([Feature]: supervise long-running threads — turns complete while background subagents are still working, and nothing restarts the run #38, [Feature]: Self-paced loops — the Claude binary can already wake a T3 thread; surface it, bound it, and give models a durable T3-native
wake_meinstead #42) — since an unattended agent working a queue is a loop by any othername?
is real work versus already-solved by whatever the panel needs?
Blocked on the panel, invocation and manifest decisions.