Published Build3 min read
Pixy's wager: the bottleneck is the handoff, not the code
A script tag turns a running site into an editing surface, then hands a coding agent four fields per change: selector, property, old value, new value.
Written for builders.See today for builders
What happened
- Pixy has put a visual editing layer on running websites, giving developers and product teams a way to move, resize, rewrite, restyle and crop page elements before a coding agent implements the changes in source code.
- According to Pixy's product homepage, the record produced by an edit identifies the selector, the property, the previous value and the new value.
- Visual instructions often reach coding agents as prose or annotated screenshots; a request to make a heading smaller or align two components leaves the agent to infer the target and the desired value.
- Users can rewrite text directly in the page's DOM.
- Pixy says edits do not immediately alter deployed source: they remain in the browser and disappear on reload unless an agent pulls them into code.
Compiled by The EngineerSomething wrong?How this is made
Why it matters
Pixy has put a visual editing layer on running websites, letting people move, resize, rewrite, restyle and crop page elements before a coding agent implements the change in source code [1]. The bet inside that design is not that agents need help writing code; it is that the transfer of visual intent into something an agent can act on is where the work leaks.
According to Pixy's product homepage, an edit produces a record identifying the selector, the property, the previous value and the new value [2]. That is a deliberately small format. As the publisher frames the problem, visual instructions usually reach coding agents as prose or annotated screenshots, and a request to make a heading smaller or align two components leaves the agent to infer both the target and the desired value [3]. Four named fields replace the inference with a lookup. Users can also rewrite text directly in the page's DOM [4].
Nothing about this ships by itself. Pixy says edits remain in the browser and disappear on reload unless an agent pulls them into code [5], and that the codebase stays the source of truth with the agent handling implementation [6]. The result is a tool that deliberately does not write anything, which is a narrower claim than most products in this space make and a more testable one.
The argument for editing the live page rather than a mockup is context: dropdowns can stay open, application state can stay active, and responsive behaviour stays visible as the viewport changes [7]. Pixy says it edits the page that actually rendered, without copying or re-rendering it [8].
The company behind it is thin on public detail. Pixy operates through Surfy Ltd, a U.K. company whose public corporate record lists Alexander Yermolenko as sole director and a person with significant control, and Pixy's product materials do not identify him as founder or executive [9]. The workflow is three steps: install the script, edit the page, ask an agent to pull the changes [10]. The homepage advertises a free key with no payment card required [11], and product updates list Manager and Writer roles in preview [12], which suggests seats aimed past frontend engineers.
The category is not empty. Cursor introduced its browser visual editor in December 2025 and later expanded Design Mode with more tools for directing coding agents through visual prompts [13]; Cursor's editor lives inside its coding environment, while Pixy is distributed as a script added to the site [14]. A separate product also called Design Mode markets itself as a visual editor for live websites [15]. Paper announced a $34 million Series A from Accel and ICONIQ on July 22, 2026, bringing reported funding to $38.5 million [16], implying roughly $4.5 million raised before that round [17]. Pixy has disclosed no funding, customer count or revenue in the supplied public materials [18].
The cost of the distribution model is the obvious one. Pixy says the script can run on localhost, staging and production [19], and production use raises the scrutiny bar because the tool sits on the application itself [20]. Supporting non-engineering seats will depend on collaboration and access controls teams can evaluate before installing it on a live application [21].
Worth watching: whether the selector/property/old/new record holds up for changes that are not single-property CSS edits, and what the Manager and Writer previews look like when they leave preview.
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
Pixy has put a visual editing layer on running websites, giving developers and product teams a way to move, resize, rewrite, restyle and crop page elements before a coding agent implements the changes in source code.
ReportedView cited source - [2]
According to Pixy's product homepage, the record produced by an edit identifies the selector, the property, the previous value and the new value.
- [3]
Visual instructions often reach coding agents as prose or annotated screenshots; a request to make a heading smaller or align two components leaves the agent to infer the target and the desired value.
- [5]
Pixy says edits do not immediately alter deployed source: they remain in the browser and disappear on reload unless an agent pulls them into code.
- [6]
Pixy says the codebase remains the source of truth and the agent handles implementation.
Sources & coverage · 1 publisher
The reporting this story was synthesized from, earliest first. Every link goes to the original.
- runtimewire.comRuntimeWire StaffAug 13Pixy turns live websites into editable canvases for coding agents
Cited in this coverage: Pixy product homepage, as reported by runtimewire.com
Cited in this coverage: runtimewire.com analysis
Additional citations
- Pixy

