Send your edits to Claude Code and let it implement them in your codebase.
Comments
Pixy team1 August 2026
Claude Code already understands your project. It knows your files, your conventions, and how your code is organized. What it doesn't know is what you changed visually. Explaining a design change in text leaves room for interpretation, even when the change is something as simple as moving a button or adjusting the spacing.
Pixy removes that translation step. Every edit you make on the page is sent to Claude Code as structured data: which element changed, which property changed, the new value, and where it applies. Claude Code turns those edits into real code and reports back what it changed and anything that still needs attention.
The connection works in both directions. You can also ask Claude Code to make a change that starts with an idea instead of an edit, like making a section work better on mobile or matching the spacing from another page. The result appears on the page you're already looking at, ready to review before it becomes part of your codebase.
Pixy team11 August 2026
Moving this to In Progress.
Completed: · Editor changes are captured as structured records. · The agent can pull batches, apply changes, and report each action as built, declined, or postponed.
In progress: · Connecting a project to the current page with a single command. · Moving the conversation directly into the editor instead of a terminal.
We're already using it internally on Pixy while finishing the integration. It'll ship once the full flow is in place.