Block a user
Discussion: architecture as a project document, separate build plans, and how detailed plans should be
A milestone that legitimately changes nothing has no way forward
The planner can't say 'no more milestones', and 'next milestone' forces one
Also: moving on ignores the PR's state. On the same run, PR #166 opened at 12:54:14, and project complete arrived nine seconds later and was accepted. The operator had never reviewed #166,…
The publisher commits build artifacts into PRs (git add -A)
The planner's transcript: scope it to the task, attribute who acted, and include orchestrator facts
Widened after the second live run. Two more problems come from the same design: the planner renders the shared log raw.
1. It can't tell who acted. The executor's tool calls and messages…
The planner can't say 'no more milestones', and 'next milestone' forces one
The planner's transcript: scope it to the task, attribute who acted, and include orchestrator facts
Correction: the executor is not affected. Its full read_events() scan (LLMExecutor._scope) only finds the latest PlanSubmitted, and its turns read from that event on, so it already sees…
Make the agent conversational: questions, explanations and asking back, in Matrix
A concrete case from the second live run: a task sent in IDLE, before use <project>, gets "no active project; say 'use '". That reads as "discarded", so the operator sent the task…
The transcript is not scoped to the task: a new task's planner sees the previous task
Make the agent conversational: questions, explanations and asking back, in Matrix
Redeliver an interrupted review comment, and close the issue on completion
Adopt an already-published PR instead of publishing again
Bind approvals and feedback to the revision they were about