Coding agents
Visual plans
A visual plan is what your coding agent proposes to build, published as a page your team can read and comment on. Wireframes, architecture, the steps, the files it will touch, and the questions it wants answered, all before the first line is written.
Everyone in your workspace can read a visual plan, pin feedback on it, and approve it or ask for changes. Each plan also carries a visibility control: its author can keep it to themselves, or open the link to anyone who has it — for a reviewer with no account in your workspace.
#What a visual plan is for
Reviewing a pull request means reviewing a decision already made. A visual plan moves that conversation earlier: your coding agent researches the codebase, writes down what it intends to do, and stops. You read it, say what is wrong, and it builds the corrected version.
A visual plan includes a written overview, wireframes for any screens, a diagram for the architecture, the implementation steps, the list of files it will touch, the data-model and API changes, and its open questions.
#Asking for one
Ask your coding agent to create a visual plan with inline before it starts building. It publishes the visual plan, hands you a share link, and waits.
The visual plan tools arrive over the same connection as the pre-PR review tools, so a coding agent you have already connected can author them with no further setup. See Coding agents.
#Reviewing one
Visual plans
Implementation plans authored by coding agents over MCP, awaiting human review. Open a plan to see wireframes and architecture, pin feedback, and approve before any code is written.
Open the link and read it. Comment puts you in pinning mode, and a click anywhere on the visual plan pins your feedback to that spot, so a note about a wireframe stays attached to the wireframe.
The Feedback panel gathers every pin in one list with the replies under each, which is the view to work down when several people have commented. Answer an open question by pinning a comment on the question itself.
The two decisions are Approve plan and Request changes. Either one sends your coding agent back to work with everything your team pinned.
#What happens next
Your coding agent collects the feedback, replies to each comment, and revises the visual plan where the feedback asked for a change. A reply resolves that thread, so the next pass reads only what is new.
It implements once you approve. Each visual plan shows In review, Changes requested, Approved or Implemented, so the list tells you which ones are waiting on your team.
#Finding them again
Visual plans in the sidebar lists every visual plan in the workspace with its repository, its author and its revision number. Open one from there to reach the same page the share link opens.
Visual plans are included with Free. See Plans and billing.