Check your CI jobs without leaving your terminal. You can see which jobs passed or failed, read their logs, and see which machine sizes are available. Your coding agent can use the same commands to help you investigate a failed job.
These commands only read information. They don’t change, cancel, or rerun jobs.
Before you start
Install or upgrade the CLI and sign in with your API key:
See the CLI reference for more on signing in.
List your jobs
See your recent CI jobs:
Narrow the list by status, repository, or workflow. For example, show only failed jobs in one repository:
See job details
Use a job ID from the list to see its status, machine size, branch, and a link to the job on GitHub:
Read job logs
Print the logs for a job:
Add --step to see the logs for one step only. For example, show step 4:
Check runner sizes
See the machine sizes you can use, with their CPU, memory, and disk:
Use a size’s label in your workflow’s runs-on line. See runner sizes to pick the right one.
Use the output in scripts and coding agents
Add --json to any of these commands to get output that a script or coding agent can read:
If a job never started, use troubleshooting to find out what blocked it. Last modified on November 5, 2026
