Skip to content

/goal should treat repeated blocking conditions as completion criteria #23067

@Tuo-Luo

Description

@Tuo-Luo

Problem

When /goal automatically continues and repeatedly hits the same blocking condition, it can keep re-entering the same state without making progress. The agent may keep restating the same blocker, while the goal remains active because the original objective is not finished.

Workaround

Add a rule like this to AGENTS.md:

When a goal automatically continues, list the blocking conditions.
When creating or describing a long-running goal, include a completion criterion that treats the same blocking condition repeating twice as goal completion.

Why this works

The important part is making the repeated blocker part of the goal's completion criteria up front. Then, when the same blocker appears twice, marking the goal as complete is no longer pretending the blocked action succeeded. It means the goal reached its defined stop condition: the same blocking condition repeated and was recorded.

This avoids an automatic continuation loop while preserving the blocker reason for the user to resolve later.

Metadata

Metadata

Assignees

No one assigned

    Labels

    agentIssues related to the core agent loopenhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions