CI pipeline status in the Changes tab

  • Desktop app
  • All plans
View as Markdown

What it does

After a push, the Changes tab shows whether the CI pipeline of that commit is running, passed or failed, for GitHub Actions and GitLab CI (gitlab.com or a self-hosted instance). When it failed, it lists the failed jobs with the end of their log, and Send to agent to fix hands one job to an agent: the job name, its link, the commit and the log lines, so nobody has to copy a log and brief an agent by hand. It can also notify you when the pipeline of a branch you pushed from AgentsRoom finishes.

Where to find it

Inside a project, right panel, Changes tab: the CI badge sits next to the Fetch / Pull / Push buttons. It follows the checkout picked in the worktree selector. On the phone: project, Changes, the CI line under the worktree selector.

How to use it

  1. Connect GitHub or GitLab once with Import from GitHub or Import from GitLab (the same account is used, nothing else to set up).
  2. Push. The badge shows CI queued, CI running, then CI passed or CI failed. Click it to open the pipeline page.
  3. On CI failed, the arrow next to the badge opens Failed jobs: each job shows its stage, the end of its log and Open job.
  4. Pick New agent (the default, a quick agent started in that checkout) or an agent already working in that checkout, then Send to agent to fix.

Settings

  • ciPipelineNotifications (global, account-synced, Settings > Notifications > CI pipeline finished): notify (desktop banner, and the paired phone when you are away) when the pipeline of a branch pushed from AgentsRoom passes, fails or is canceled. Default on.

Agent tools (MCP)

None. Agents receive the brief as a normal message.

Providers

All providers, no difference: the brief is a plain message, or the first prompt of a new quick agent.

Mobile

Same badge, same failed jobs and same Send to agent to fix on the phone's Changes screen; the brief is built and sent by the desktop. A tap on the pipeline notification opens the project's Changes screen.

Limits

  • GitHub.com and GitLab only. GitHub Enterprise, Bitbucket, Azure DevOps, Jenkins and other CI services show no badge.
  • The status is the one of the pushed commit (the upstream tip): a branch never pushed shows nothing.
  • GitLab: pipelines need a token with the read_api scope (the token link of the GitLab connection now pre-ticks it); a token with read_repository only shows "CI unavailable" and asks to reconnect. GitHub: a classic token with repo, or a fine-grained token with Actions read access.
  • Up to 10 failed jobs are listed, with the last 80 lines of each log.
  • The notification follows pushes made from AgentsRoom (Changes tab or phone), not pushes made in a terminal.

Common questions

  • Can AgentsRoom show whether my GitHub Actions passed? Yes, the CI badge next to Push in the Changes tab, once GitHub is connected with Import from GitHub.
  • Can an agent fix my failed pipeline? Open the failed jobs from the badge and click Send to agent to fix: the agent gets the job, its link, the commit and the end of the log.
  • The badge says CI unavailable on GitLab. The token cannot read pipelines: reconnect GitLab with a token that has the read_api scope.
  • How do I stop the pipeline notifications? Settings > Notifications, untick CI pipeline finished.

Related