Annotating boards
Circle what's wrong, send it to your agent and review the fix on the same board.
Boards are live
A board is not an archive you file into — it is a surface someone is listening to. What you draw on it becomes work on the other side, usually within seconds.
Circle it, say one sentence
Draw a region on the screen itself, right where the problem is, and write one sentence. Pick what you want done — fix, investigate, refactor, redesign, a reminder, a task, or something else. To re-capture a screen, use the card's reshoot action instead: that click is sent at once. The screenshot, the region, the elements under it and the branch it came from travel with the annotation; you never describe where you were or how you got there.
If the sentence needs to point at a specific element — "this button, not that one" — mark the element directly and it rides along as an explicit reference, ranked above everything the region merely overlaps.
Where it goes
Your annotations stage on the board until you send them: press Send to claude · N at the foot of the board's Annotations panel (the board's ⋯ menu offers the same as wake claude), and the batch lands on the work queue for the project and branch behind the board. An agent session listening in that repository picks it up — replies in the thread come from claude by default; mention @eve in the thread and that reply routes to eve instead.
You do not manage the queue. Annotate, send, keep testing; the queue is the agent's problem.
What happens next
Each annotation shows its state on the board:
- Staged — drawn, not yet sent.
- Open — sent, waiting for a listening agent.
- Working — an agent has taken it and is changing code.
- In review — the fix is in: the after-shot hangs beside your region and a thread reply says what was done.
- Resolved — only you can set this. The agent never closes its own work; you accept it on the board or send it back with another sentence.
You can withdraw an annotation at any point — it then shows as cancelled; an agent mid-flight on it reverts its changes and moves on. If a fix misses, reply in the thread — the conversation stays anchored to the region.
Answering board questions
Agents ask back the same way you annotate: a question appears in the board's Questions panel, docked beside the canvas, with one-click answer pills, optionally tied to a card. Click your pick — there is always an inline "Other" if none of the options fit, and typing it is the pick.
Picks are staged, not sent. Clicking composes your answers; nothing reaches the agent until you press ↑ send on the last question — so you can answer a whole batch, change your mind, and commit once.
Need context before choosing? Ask for more information on a question and the answer streams in live, mid-selection. The full question surface — including how PMs use it for structured decisions — is on Questions.