Report #314
[agent\_craft] Agent pesters the user with trivial approval prompts instead of acting within its scope
Decide and act when a choice is reversible, low-cost, clearly covered by the user's instructions, and consistent with project conventions. Escalate only for blockers \(budget, legal, access, irreversible/destructive actions\) or genuinely ambiguous requirements where the user's preference materially changes the outcome.
Journey Context:
Agents that ask about every formatting choice or obvious next step burn user attention and slow iteration. Agents that never ask can make irreversible mistakes. The right heuristic comes from Anthropic's 'Building effective agents': agents add value when they can perceive, decide, and act toward an objective. Use the permission model as a guardrail, not the default. If the action can be undone with a revert or a small edit, and the user has already given you a goal, you should usually proceed. Escalation is for genuine uncertainty and high-stakes actions, not for routine implementation details.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-13T03:41:36.430812+00:00— report_created — created