Figma Make edits your product and opens a PR
New beta: connect a local codebase, prompt on a frame, and the agent makes the code edits, commits, and opens a pull request — no terminal.
Source: Figma release notesDesign tools learned to commit. This week Figma Make started editing your live product and opening a PR with no terminal, v0 shipped a Git panel, and Cursor ran agents in the cloud — links below.
New beta: connect a local codebase, prompt on a frame, and the agent makes the code edits, commits, and opens a pull request — no terminal.
Source: Figma release notesThe rebuilt v0 opens a branch per chat, raises a PR against main, and deploys on merge, so anyone on a team can ship through review.
Source: Vercel blogAgents now work in cloud VMs with terminal and browser access and report back to the editor — generation moves off your machine.
Source: Cursor changelogWhen a tool writes straight into your file or repo, the useful question is what changed, not what was made. A diff scopes the answer to the lines that moved — which is also why Figma's Design Agent leans on writing to the canvas with your real design system, so edits stay inspectable.
It builds and edits with your existing components and variables, so the change is reviewable in place rather than a fresh wall of output.
Source: Figma blogMake the agent state the change, the surfaces it touches, and what it is leaving alone.
ScopeRequire the change as a diff or editable frames, with screenshots or tests to inspect it.
DiffKeep merge a human action: review the hunks, comment, approve only what is right.
GateHand this to an AI design or build tool — Figma Make, v0, Cursor, or Claude — to get a page in today's Pull Request Review idiom instead of a generic dashboard.
Design a web page using a Pull Request Review art direction. Lay it out like a code-review "files changed" view: a full-width PR header, then a sticky left "files changed" index rail beside a right-hand feed of entries. Do not use a big hero image. Translate the references into real web components: - A masthead styled as a PR header, with an Open status pill and a branch ref (canvas to main). - A left rail listing each section as a file row with a monospace path and a +N stat, anchored to the feed. - Each feed section as a changed-file card: a file path, a kind tag, and a +N -N diff stat. - News items shown as green addition rows: a linked headline, one sentence, a source link. - A green merge box for the closing takeaway, with a visible Merge button. Use a cool light review-paper background, near-black ink, merge green, deletion red, and a quiet plum for the merged state. Pair a clean product sans for display with a readable serif for body, and a monospace for paths, line numbers, and labels. Keep it readable: body text at least 18px, generous line height, no justified prose, strong contrast, no text against borders. Avoid fake readable code in images (use abstract bars), AI-glow, neon gradients, and decorative marks that hurt scanning.
Why it works: it names a real web archetype and a specific layout, then translates the idiom into components, palette, type, and accessibility rules a tool can build — so you get this issue's look back, not a vague "make it look like a code review."
Generation is cheap and constant now; the scarce, designed moment is the one where a person says yes. See also Claude Opus 4.8 and Claude Design.
A field experiment from the team behind Beaver Builder.