You started a run in Run your first task, and it paused. Before DIJJI.ai writes any code, it produces a plan and waits for you to approve it. This page walks through that decision.
For what a plan is and why the checkpoint exists, see Plans and plan approval. This page is the hands-on part.
Open the run
From the task’s page, open the run detail page for the current run. While the plan is still being written, the run shows Running with a Planning label — give it a moment.
Once the plan is ready, the run moves to Awaiting Plan Approval and the plan appears on the run detail page in its own card. Nothing is written, nothing is merged, and no further credits are spent until you decide.
Read the plan
The plan card holds the proposed work, written out as a formatted document — read it top to bottom, the way you’d read a short design note from a teammate. It describes the approach DIJJI.ai intends to take and the changes it expects to make.
The card shows a version, Plan v1 for a first attempt. If you reject a plan and run the task again, the next plan reads Plan v2, and so on.
As you read, you’re answering one question: did DIJJI.ai understand the task the way you meant it? Check that it targets the right area, takes a sound approach, and doesn’t skip something that matters.
Approve it
If the plan looks right, approve it. The run leaves Awaiting Plan Approval, returns to Running, and DIJJI.ai begins the work — carrying on through the pipeline you designed.
Approving is a go-ahead, not a final sign-off. You still review the pull request the run opens at each stage. The plan is your check on intent; the gate is your check on the result.
Reject it
If the plan misreads the task or heads in the wrong direction, reject it instead. You’ll be asked for a reason, and the reason is required — it’s how you tell DIJJI.ai what was wrong. Be specific: name what the plan got wrong or left out, so the next attempt can do better.
Rejecting does two things:
- The run is cancelled. This attempt is over. DIJJI.ai does not revise the plan in place or try again on its own.
- Your reason is posted to the source issue. It’s added as a comment on the GitHub issue the task came from, so the feedback lives alongside the original request — you’ll see it, and any other comments, in the task’s Issue tab (Add context with issue comments).
To try again, return to the task and select Re-run. The new run reads your rejection reason, produces a fresh plan, and brings you back to Awaiting Plan Approval with a new version to review.
Take your time
There’s no time limit. A run in Awaiting Plan Approval waits indefinitely — it won’t approve itself, expire, or move on without you. The decision is always yours, and the run holds its place until you make it.
The one exception: if the project has Auto-approve plan turned on, runs approve their own plans and never pause here at all. See Plans and plan approval.
What’s next
Approve a sound plan and your first run is fully underway. From here it works through your pipeline, opening a pull request at each stage and pausing at any gate you set. To follow where it goes, see Run states for every state a run can pass through.