Getting started
Complete the first run
Enable the work loop and follow one job from GitHub signal to evidence.
Choose the first agent
Code Agent is the clearest end-to-end check because it begins with a Ready project issue and should leave a branch, commit, pull request, and validation trail. Issue Planner is a good alternative when you want to start from a rough brief.
Check readiness
The repository overview and agent editor surface configuration and runner problems before the job starts.
- The workspace runner is online.
- The repository work loop is enabled.
- The agent has a provider, model, supported thinking level, and usable image.
- The GitHub issue or pull request satisfies the agent trigger.
- Workspace and repository capacity are available.
Follow the evidence
Open Runs at the workspace level or repository level. The detail view records status transitions, attempts, events, token usage, failures, and the verified GitHub outcome.
Frequently asked questions
How quickly does eligible work start?
It depends on polling, runner connectivity, schedules, and available workspace and repository capacity.
Where can I see all jobs?
Use the workspace Runs page for cross-repository activity or the repository Runs tab for a focused view.
What does Needs attention mean?
The run is blocked, failed, interrupted, or otherwise requires operator judgment. Open the run to inspect its recorded reason and events.
Will a failed run create a false success artifact?
No. The runner verifies the artifact contract and reports failures or blockers when the expected outcome is missing.