// Chrome extension
Your CI status, live in the toolbar
Know the moment a build breaks, without keeping a GitHub tab open. The toolbar icon turns green, yellow or red for all the repositories you care about. Click it for every workflow, live run timers and one-click links to the runs.
// At a glance
One icon for all your repositories
Green
Every workflow's latest run passed.
Yellow
Something is queued or running. Checks speed up to every 5 seconds until it finishes.
Red
Something failed. It flashes red and green when some repositories passed and others failed. A number on the icon counts the failing repositories.
// Features
Made for real projects
See why it failed
Each repository is a compact card whose state line names the failed job and step. Expand it for the lines from the log that say why, every workflow with its last ten runs, and the commit, pull request and author behind the run.
Keep it in view
Dock it in Chrome's side panel while you browse, pop it out into its own window, or keep it on top of every other window in a corner of your screen.
Step lights
A running workflow lights a small light for each step as it finishes, the current one pulsing, so you can see how far along it is at a glance.
Every workflow counts
The latest run of each workflow decides the status, so a failing CI is never hidden by a deploy that finished after it. Switch off noisy workflows; cancelled and skipped runs never raise false alarms.
Live run timers
Running workflows count up as they go; finished ones show how long they took. Click any workflow to open its run.
Rate-limit safe
When nothing changed, GitHub answers "not modified", which does not count against your API limit. The settings page shows live usage.
Branches, workflows and pausing
Watch all branches or a specific one, pin a single workflow to its own card, and pause the ones you are not working on. On a repository's GitHub page, add it in one click.
The commit it is for
Each result shows its commit, so a green run of an older commit is never mistaken for the one you just pushed. A failure links straight to the failed job's log.
Alerts and reviews
Optional desktop notifications when a workflow starts, succeeds or fails, naming the failed step. Runs waiting for a deployment review are marked, with a link to review them.
Read-only by default
A read-only token is all it needs. Re-run and cancel buttons are there only if you switch them on. It talks only to GitHub's API: no server, no analytics.
// Setup
About two minutes
- Open the settings page: right-click the toolbar icon and choose Options, or click ⚙️ in the popup.
- Choose features (optional). The number on the icon, notifications, and whether to show re-run and cancel buttons. They come first because re-run and cancel decide the token's permission, so you only ever make one token. Leave them off to stay read-only.
- Create the token. Click Create a read-only token on GitHub (or Create a token with re-run and cancel). GitHub's form opens with the name, a 90-day expiry and Actions: Read-only (or Read and write) already set. Under Repository access choose All repositories (or the ones to monitor), then Generate token.
- Paste it and click Save Token. The extension checks it right away: account, token type, how many repositories it can see, remaining API requests.
- Add repositories. Click the toolbar icon, then + Add: type an Owner (your username or an organization), pick the Repository from the list of all its repositories, pick a branch (or "All branches"), optionally one Workflow, and click Add Repo. On a repository's GitHub page, just click Add it. Owners you use are remembered for next time.
For an organization's repositories, choose the organization as the token's Resource owner. Some organizations must approve fine-grained tokens before they work.
// Support
Getting help
The settings page's Test Token button answers most questions: it shows what your token can see and whether it works. Common ones:
| Symptom | What to do |
|---|---|
| "Bad token" | The token expired or was revoked. Settings, then Create a read-only token on GitHub and save the new one. |
| "Repo not found or no access" | Check the owner/repo spelling, and that the token's Repository access includes that repository. |
| Organization repositories missing | Create the token with the organization as Resource owner; the organization may need to approve it. |
| The icon stays gray | No token yet, no repositories added, or none has workflow runs. Click Refresh Now in the popup. |
| "Rate limited" | The popup shows when checking resumes. Pause repositories you are not working on; the settings page shows live usage. |
| Re-run or cancel says the token cannot do this | Run controls need a token with Actions: Read and write. Settings, Setup, Connect GitHub shows how to add it to your existing token on GitHub; the token's value does not change, so there is nothing to paste again. |
| No notifications | Check they are on in the settings page, and that Chrome is allowed to show notifications in your operating system's settings. |
Still stuck, found a bug, or have an idea? Get in touch. Mention your Chrome version and what the settings page shows.
// Privacy
Private by design
No server, no analytics, nothing sent to the developer. The extension talks only to GitHub's API with your own token, and keeps its data in your browser. Your token stays on your device unless you choose to sync it. Read the privacy policy.