# Pixy turns live websites into editable canvases for coding agents > Source: > Published: 2026-08-13 20:00:16+00:00 [Pixy](https://pixydesignapp.com/?ref=runtimewire) 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. Pixy operates through Surfy Ltd, a U.K. company whose [public corporate record](https://clarity-project.co.uk/company/15026168?ref=runtimewire) lists Alexander Yermolenko as sole director and a person with significant control. [Pixy's public product materials](https://pixydesignapp.com/?ref=runtimewire) do not identify him as its founder or executive. Pixy positions the running website as the editing surface rather than asking teams to recreate an interface in a separate design file. Customers add a script tag to the site, edit the rendered page and have their coding agent pull a structured record of the changes. Pixy says the codebase remains the source of truth and the agent handles implementation. ### A visual handoff instead of another code generator Pixy's advertised workflow has three steps: install the script, edit the running page and ask an agent to pull the changes. According to the [product homepage](https://pixydesignapp.com/?ref=runtimewire), the resulting record identifies the selector, property, previous value and new value for an edit. Users can also rewrite text directly in the page's DOM. The distinction matters because 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 desired value. Pixy lets the user make the adjustment on the page first, then gives the agent a scoped record to implement in the codebase. Edits do not immediately alter the deployed source. Pixy says they remain in the browser and disappear on reload unless an agent pulls them into code. That leaves a human decision between visual experimentation and permanent implementation while giving Pixy a defined role between the person reviewing an interface and the agent changing its source. ### The live page becomes the workspace Pixy's central product claim is that a running interface already contains context that disappears when work moves into a mockup. Dropdowns can remain open, application state can stay active and the site's responsive behavior remains visible as the viewport changes. Pixy says it edits the page that actually rendered without copying or re-rendering it. The approach could also extend visual changes beyond frontend engineers. Pixy's product updates list Manager and Writer roles in preview, an indication that the company is testing seats for people involved in review, copy and other non-engineering work. The [homepage](https://pixydesignapp.com/?ref=runtimewire) also advertises a free key with no payment card required. That creates a broader commercial path for the product. Pixy can begin as a developer utility and potentially become a shared surface where product managers, designers, writers and engineers specify changes on the product itself. Its ability to support that workflow will depend on collaboration and access controls that teams can evaluate before putting it on a live application. ### A crowded race to capture visual intent Pixy is entering a category that coding platforms and funded design startups are already pursuing. [Cursor introduced its browser visual editor](https://cursor.com/blog/browser-visual-editor?ref=runtimewire) in December 2025 and later expanded [Design Mode](https://cursor.com/blog/design-mode?ref=runtimewire) with additional tools for directing coding agents through visual prompts. Cursor's editor is part of its coding environment, while Pixy is distributed as a script added to the website. [Design Mode](https://www.designmode.app/?ref=runtimewire), a separate product with the same generic name as Cursor's feature, markets itself as a visual editor for live websites. Its presence shows that Pixy's basic premise is already attracting direct competition outside integrated coding environments. Paper brings substantially more capital to the design-and-code category. On July 22, 2026, [Paper announced a $34 million Series A](https://paper.design/blog/series-a?ref=runtimewire) from Accel and ICONIQ, bringing its reported funding to $38.5 million. Pixy has disclosed no funding, customer count or revenue in the supplied public materials. Pixy's adoption case rests on the installation flow it advertises: paste a script into a site, edit the running interface and let an agent retrieve the changes. That removes the need to transfer visual instructions from a separate canvas, but it also asks teams to add third-party code to the application being edited. ### Production access raises the bar Pixy says its script can run on localhost, staging and production sites. Production use brings a different standard of scrutiny because the tool sits on the application itself. The reviewed public materials do not establish Pixy's Content Security Policy requirements, network architecture, browser credential model or rollback behavior. Pixy has started adding agent-specific access controls. In an August 12 product update, Pixy said [each connected AI agent receives its own project key](https://pixydesignapp.com/news/manage-and-revoke-ai-agents-individually?ref=runtimewire), allowing a team to review or revoke one agent without affecting the others. The announcement does not establish the broader production security controls teams may require. Pixy also said in an August 13 update that it uses an IP address only long enough to determine a city for connection records, then discards the address. That is [Pixy's stated data-handling practice](https://pixydesignapp.com/news/pixy-stores-your-city-not-your-ip-address?ref=runtimewire), rather than an independently tested finding. Pixy's early appeal comes from its narrow place in the development process. It translates changes made on a running interface into a record that an agent can implement while leaving the codebase in control. Its opportunity depends on whether that workflow remains simple as customers demand stronger collaboration, access management and production safeguards.