Give Qoder a verifiable outcome and let it plan and iterate toward that result.
Use Goal for multi-step work with a measurable end state, such as reaching a test-coverage target, completing a migration, or removing a defined class of defects.
Open Add context in the task composer and select Goal, or type
Qoder plans the path, executes work, checks progress, and continues when the goal is not yet satisfied. Follow the task record to review commands, file changes, tests, and evidence.
The Goal panel shows elapsed time and provides Edit goal, Pause goal, and Delete goal. Use Edit goal to clarify constraints without changing the objective, and review the task response and verification evidence before treating the result as complete. Create a separate task if the desired result becomes a different objective.
This goal gives Qoder a result, boundaries, and a verification method, so it can decide whether another iteration is needed.
When to use Goal
- Improve test coverage, performance, or a measurable quality target.
- Migrate an API, dependency, or framework across directories.
- Find and remove a defined, verifiable class of issues.
- Run repeated implementation, testing, and correction when the full path cannot be listed in advance.
Start a goal
Open Add context in the task composer and select Goal, or type /goal and select Goal from the suggestions. Describe the result rather than a sequence of steps, and include the completion criteria and boundaries. The composer shows Turn off goal mode while Goal is active.
Write a reliable goal
- Use a result that can be checked.
- State files, APIs, environments, or behavior that must not change.
- Include the required test, build, benchmark, or manual verification.
- Split broad objectives into separate goals with independent acceptance criteria.