Problem (one or two sentences)
Premature coding: the agent is forced to act, not think.
Context (who is affected and when)
In any work mode, when the agent is asked a question, instead of answering it interprets it as a task to solve and jumps into action even when explicitly ordered to just respond — because attempt_completion (the tool the agent uses to end every message) forces it to always close with a concrete action. It may respond well at first, but sooner or later the tool pushes it to act, interrupting the conversation and breaking the interaction flow. This is serious because that back-and-forth — asking questions, bouncing ideas, refining details — is essential to resolving any task properly.
It's like the agent has this design anti-pattern in its DNA.
Desired behavior (conceptual, not technical)
Solving a problem requires back-and-forth between the user and the agent: brainstorming, debating, questioning, refining — without being forced to switch to Ask mode. The agent must be able to sustain that dialogue in any mode, not just blindly execute. Every time the agent gets the impulse to act without listening, valuable time is lost and the flow of the conversation breaks.
Constraints / preferences (optional)
How is it possible that you have to fill out 100 text boxes just to report a problem? Is it for fun, or to scare people away?
Request checklist
Zoo Code Task Links (optional)
No response
Acceptance criteria (optional)
No response
Proposed approach (optional)
No response
Trade-offs / risks (optional)
No response
Problem (one or two sentences)
Premature coding: the agent is forced to act, not think.
Context (who is affected and when)
In any work mode, when the agent is asked a question, instead of answering it interprets it as a task to solve and jumps into action even when explicitly ordered to just respond — because attempt_completion (the tool the agent uses to end every message) forces it to always close with a concrete action. It may respond well at first, but sooner or later the tool pushes it to act, interrupting the conversation and breaking the interaction flow. This is serious because that back-and-forth — asking questions, bouncing ideas, refining details — is essential to resolving any task properly.
It's like the agent has this design anti-pattern in its DNA.
Desired behavior (conceptual, not technical)
Solving a problem requires back-and-forth between the user and the agent: brainstorming, debating, questioning, refining — without being forced to switch to Ask mode. The agent must be able to sustain that dialogue in any mode, not just blindly execute. Every time the agent gets the impulse to act without listening, valuable time is lost and the flow of the conversation breaks.
Constraints / preferences (optional)
How is it possible that you have to fill out 100 text boxes just to report a problem? Is it for fun, or to scare people away?
Request checklist
Zoo Code Task Links (optional)
No response
Acceptance criteria (optional)
No response
Proposed approach (optional)
No response
Trade-offs / risks (optional)
No response