How-To Guides
Reject and re-scope
A rejection isn't a failure — it's a signal that the objective needs more precision. Here's how to close the loop and set up the next agent run to succeed.
- 1
Click Reject and write a specific note
The rejection note is written to the audit chain and will be visible to the next agent that claims this objective. Be specific about what failed. “The login button is missing on mobile” is actionable. “Didn't quite work” is not.
- 2
The objective returns to Backlog
After rejection, the objective moves back to Backlog. The rejection reason, timestamp, and your identity are recorded in the audit chain. The agent's next run will be a fresh claim — it doesn't continue from where it left off.
- 3
Diagnose what failed
Most rejections fall into one of three patterns:
A criterion wasn't met
Clarify or add the specific criterion that failed. Make it more explicit about what "done" looks like.
The objective was too broad
Split it into two smaller objectives. Return this one to Backlog and create a second for the remaining scope.
The agent made wrong assumptions
Add the missing constraint or context to the description. Be explicit about what the agent got wrong.
- 4
Edit the objective
Open the objective from the Backlog. Update the acceptance criteria, description, or scope based on your diagnosis. Don't change the title if the intent is still the same — the audit chain links the history to the original objective.
- 5
Re-schedule
Click Schedule to move the objective back to the Scheduled lane. An agent will pick it up and start a fresh run. The rejection note and prior run history are visible to the agent at claim time.