You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat: add /goal command for autonomous task completion #31762
Add a /goal slash command that sets a completion condition and keeps the agent working across turns until the condition is met. This is inspired by Claude Code's /goal command and OpenAI Codex's Goal Mode.
Motivation
Currently, users must manually prompt the agent after each step for multi-step tasks. A /goal command would allow users to define a completion condition once and let the agent work autonomously until the goal is achieved.
Proposed Behavior
Commands
/goal <condition> - Set a new goal and start working toward it
/goal (no args) - Show current goal status
/goal clear - Clear the active goal
How it works
User sets a goal with a completion condition
Agent works toward the goal in the current turn
After each turn, an evaluator model checks if the condition is met
If not met, the evaluator's reason is fed back and the agent continues
If met, the goal clears and an achieved entry is logged
Evaluator
Uses a configurable small/fast model (default: session's configured model)
Only judges from the conversation transcript (does not run tools)
Returns yes/no decision with a short reason
Conditions should be phrased around observable output
Goal State
Stored per-session in the database
Tracks: condition, status (active/achieved/cleared), iterations, tokens, timestamps
Emits events for UI updates
Example Usage
/goal All tests in test/auth pass and lint is clean
The agent will then:
Run the tests
Check lint
If tests fail, fix them and re-run
Continue until both conditions are met
Design Decisions
Independent from todos: Goal is a session-level objective, separate from task lists
Configurable evaluator: Users can specify a custom evaluator model
Session-scoped: Goals are per-session, not persistent across sessions
V1 command system: Matches existing /init and /review pattern
Feature requests must use the Feature Request template, which requires the title to start with [FEATURE]: and include the verification checkbox confirming the feature hasn't been suggested before.
Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
Activity
github-actions commentedon Jun 10, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
[FEATURE]:and include the verification checkbox confirming the feature hasn't been suggested before.Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
If you believe this was flagged incorrectly, please let a maintainer know.
github-actions commentedon Jun 10, 2026
This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.
Feel free to open a new issue that follows our issue templates.