With a project created and a pipeline designed, your project is ready to do work. This page walks through running your first task — picking one off the Tasks page and starting a run against it.
For what tasks and runs are, see Projects, tasks, and runs. This page is the hands-on part.
Before you start
Two things need to be in place:
- A connected GitHub repository. A run works on your project’s repository, so the project must have GitHub access. You set this up in Connect GitHub and Create your first project.
- At least $10 in your balance. Starting a task requires a minimum balance of $10.00 — separate from, and lower than, the $100.00 it takes to create a project. For what a balance is, see Credits and billing.
You don’t strictly need a saved pipeline to run a task, but if you followed Design your first pipeline you already have one — and the run will travel through it.
Find your tasks
Open your project and go to Deliver > Tasks.
A task is a unit of work — a feature, a bug, a change. Tasks come from your project-management tool: every issue in your connected GitHub repository becomes a task here, automatically. There’s no manual sync step and no separate place to file work — the issue you’d write anyway is the task.
If no tasks have come in yet — or none match the status you’re filtering on — the Tasks page shows an empty state. With the default Pending filter it reads:
No tasks found — No tasks with status “Pending”.
If you see this, open an issue in your GitHub repository. It appears on the Tasks page shortly after.
Read the task list
The Tasks page lays your tasks out two ways — Board or List — using the view switcher (see Switch task views). Board is the default: it groups tasks by status into columns, giving you the whole project at a glance. For a first task, switch to List — a flat, single-status view that’s easy to follow.
List shows one status at a time. Pick the status with the filter tabs across the top — Pending, Queued, Running, Completed, Failed, Cancelled, or Archived — and narrow further with the search box. It opens on Pending, which is exactly where a fresh task lands, so leave it there for now.
Each task on the list shows:
- Title — the issue’s title, and a link through to the task’s own page.
- Issue reference — the source GitHub issue number, linking back to GitHub.
- State — where the task stands. A fresh task reads Pending: synced, not yet run. Other states include Queued, Running, Completed, Failed, Cancelled, and Archived.
- Run number — once a task has been run, which run is current, for example Run #2.
- Last updated — how long ago the task changed.
Pick a Pending task to run first — ideally a small, well-described issue, so the first run is easy to follow.
Run the task
On the task’s row, select Run. (For a task that has already failed or been cancelled, the same button reads Re-run — it starts a fresh attempt.)
Before the run starts, DIJJI.ai checks two things:
- Your balance. If it’s below the $10.00 minimum, DIJJI.ai blocks the run and shows your current balance against what’s required, with a shortcut to top up. Add credit, then select Run again. See Credits and billing.
- Other active runs. A project works on one run at a time. If another task in the same project is already running, DIJJI.ai doesn’t start a second straight away — it asks Add to queue?. Confirm, and the task waits its turn in the project’s queue (see The task queue), then starts automatically when the active run finishes. Your first task, on a fresh project, has nothing ahead of it, so it starts right away.
There’s no confirmation dialog. When the checks pass, the run starts and DIJJI.ai takes you to the task’s page.
One more step can appear in between: if your code changed outside DIJJI.ai since it last looked, you may be offered Sync first before the run begins — a chance to bring its picture of your repository up to date so results stay accurate. Syncing is free. Choose Sync first, or start the run anyway.
What happens next
The task moves from Pending to Running — passing briefly through Queued as the run takes hold — and a run, one attempt at the task, begins. The task’s page now shows that run, and you can open the run detail page to follow it step by step.
A run’s first work is to read the task and produce a plan — the proposed work, before any code is written. While it does this, the run shows Running, often with a Planning label.
When the plan is ready, the run pauses at Awaiting Plan Approval and waits for you. Nothing else happens until you approve or reject it — a paused run holds its place indefinitely.
For every state a run can pass through, see Run states.
What’s next
Your first run is underway and waiting on you. The next step is to read the plan it produced and decide whether to approve it — see Approve a plan. For what a plan is and what approving or rejecting one does, see Plans and plan approval.