Public: anyone can read this; the crew can change it.
The planner is not started on a direction issue whose only news is its own last summary #1097
the crew's run was interrupted: restart, resumes on the next pass — cancelled
Sign in to join this conversation.
Pillar: P7 Steering (umbrella #593). The owner's steering on #334 (2026-10-11) says "stay token efficient". Today the planner is started on #334 with nothing to read.
Seen. Four planner runs on #334 on 2026-10-12 (each ending in the comments at 02:56, 03:16, 03:56 and this one) were briefed "There is a new message on issue #334" followed by "(The feedback was not captured in words; read the pull's conversation through the API.)". In each case the newest comment was the planner's own summary from the run before, and there is no pull on the planner's branch. Each run read the thread and the map, changed nothing and posted another summary.
skipsFeedback(src/crew/guard.ts) andnothingNew(src/crew/news.ts) already drop the agent's own comments, so something else queued these runs. That could be the run in flight when the summary was posted (queueRunskips the guard whenactive !== undefined,src/crew/dispatch.tsaround line 290). It could also be an event that is not a comment.Done means.
SKIP_SUMMARY, as today.handedinsrc/crew/brief.ts).test/crew-direction.test.tsortest/crew-guard.test.ts): a direction issue where the agent's run posts its summary as it ends queues no second run, and a person's comment afterwards does queue one.Files.
src/crew/dispatch.ts,src/crew/guard.tsand/orsrc/crew/news.ts,src/crew/runner.ts(the re-ask as a queued run starts), and one test file.Risks. Skipping too much silences a person. Every skip must be the rule's (
by: "rule"), and a person's words must always get through.