I created a new workflow with Paper's connected canvas.

Push a branch -> Claude Code read your Paper design via MCP -> boots the dev server -> then runs three diff passes automatically: visual, semantic, and image. The results land directly onto the canvas as a structured review artifact.

No Slack thread. No back-and-forth. The canvas becomes the design review.

I built it with Claude Code and Paper MCP inside Antigravity. The agent uses get_jsx to diff Tailwind classes node by node, analyzes semantic meaning of copy changes, and compares image fills with vision. It caught a hero gap deviation (gap-12 in code, gap-10 in Paper), a subhead measure narrowed from 560px to 520px, and copy drift from the Paper source, all before a single human review.

This is what a canvas connected to your repo, your agent, and your data looks like, and it's a workflow Paper's roadmap hasn't shipped yet!