Stoplights & Status
When several agents are running, the status indicators help identify which ones are working, waiting, or in error. The sidebar shows agent and pull-request status separately.
Agent stoplights
Section titled “Agent stoplights”Every running agent shows a colored dot — on its tab, and on its branch in the sidebar (one dot per agent on that branch):
| Color | Means | What to do |
|---|---|---|
| 🟢 Green | Working | A request is in flight or a tool is running. Leave it. |
| 🟡 Amber | Waiting on you | The agent finished its turn or is asking a question. Your move. |
| 🔴 Red | Error | The last request failed (e.g. an upstream or network error). Worth a look. |
Amber means the agent needs your attention. It may be waiting for a response or have finished its current turn.
To avoid flicker between rapid turns, an agent that briefly yields stays green for a moment before going amber; an agent that’s genuinely parked on a question (an interactive prompt) goes amber right away.
Pull request & CI status
Section titled “Pull request & CI status”Each branch also shows a pull-request icon, colored by its state. This status indicator describes the pull request and CI state:
| Color | State | Means |
|---|---|---|
| 🟢 Green | Ready | Checks passed and the branch is currently eligible to merge. |
| 🟣 Violet | Awaiting review | Checks passed; the only thing left is a human reviewer. |
| 🟡 Amber | Pending | CI is still running or settling. |
| 🔴 Red | Blocked | CI failed, there are conflicts, the branch is behind a protected base, or changes were requested. |
| ⚪ Muted | Draft | A draft PR — not meant to merge yet. |
A branch with no open PR simply shows a plain branch icon.
The distinct violet “awaiting review” state separates passed checks from a pull request that still needs human review.
The reverse direction has its own place in the sidebar. PENDING REVIEWS, above Projects, lists every open pull request where GitHub asked you for a review, oldest request first. A click opens the branch in the review workspace — see Code Review.
Lattis reads PR and CI state from the GitHub API with your connected GitHub account, so it reflects what GitHub actually reports — including a branch that’s behind a protected base, which it treats as blocked because GitHub won’t let you merge it as-is. It refreshes about once a minute, plus immediately after every in-app PR action. If no GitHub account is connected, branches simply show no PR state; see Pull Requests & CI to set it up.
Reading the sidebar
Section titled “Reading the sidebar”Put the two together and a single branch row tells you a lot:
●● feat/split-tender #214 +420 −38 $4.82That’s two agents working (two green dots), an open PR (#214), the line churn on the branch, and the dollars spent so far. Scan the column and you know the state of the entire project without opening anything.
- Pull Requests & CI — act on those PR states.
- Code Review — clear the reviews your team owes you.
- Changes & Spend — the numbers next to each branch.