Paper is positioning its design tool as connective tissue between designers, code repositories, data sources and AI coding agents, with a new desktop workflow that the company says is built on web standards rather than a proprietary handoff swamp.
The company describes Paper as a “connected canvas” for teams building with agents. In practical terms, Paper says the product gives visual design work a shared layer with code, apps and data, so agents can move between a design file and a codebase without forcing teams to translate everything by hand.
Paper is offering access through both a browser app and a downloadable desktop version. Its site includes a Linux download link and a separate link to open Paper in the browser.
What Paper says the desktop app changes
Paper says the desktop app connects visual work to apps, AI agents and repositories through MCP. The company lists developer tools and agent products around the workflow, including Claude, Cody, Copilot, Codex, Cursor, Windsurf, Cline, Continue, VS Code, Zed, Fleet, Nova, iTerm and GitHub.
The claimed mechanism is less mystical than the marketing gloss suggests: Paper says its canvas is based on HTML and CSS, and that designs can export as code. It also says agents can synchronize design tokens, styles and components between the canvas and a codebase, keeping those pieces aligned instead of treating design files as decorative screenshots with opinions.
Paper also says agents can connect to the canvas from an IDE or command-line interface. The company’s pitch is that an agent can read and write against the canvas, update layout variants, check consistency and send edits back into code.
Real content, not placeholder soup
Paper is also selling the tool as a way to design with actual data. The company says teams can bring in content, databases and context from local apps or cloud services, and that agents can pull material from tools, APIs, a CMS or a database into design layers.
Its demo content uses a playlist interface, first shown with placeholder tracks and then populated with real-looking music data, including an “Autumn Vibes” playlist credited to Agu Seguí. The point Paper is making is straightforward: designers can edit copy and content on the canvas, collaborate there, and then ask an agent to push those changes back to the codebase.
That is still Paper’s claim, not independent proof of how well the workflow survives contact with a large codebase, a cranky design system or a production CMS with bad field names. The company has not provided benchmark data or reliability figures in the material it published.
Who Paper says is using it
Paper says the product is used in production by designers at Vercel, Perplexity, Lovable, PostHog, Tailwind, Dub, Replicate, Zed, Attio, Quartr, Every and Daylight.
The company is also pointing users to a public roadmap and a build log. Paper’s “what’s new” entry for June 2026 lists design tokens, a pen tool, vector editing and folders. Separately, Paper says it is hiring for two principal roles: Product Designer and Design Engineer.
For now, Paper is making a familiar but technically specific bet: the design file should become an operational surface for software teams, not a museum of rectangles waiting for an engineer to reinterpret them. The useful question is whether its agent hooks and HTML/CSS foundation make that loop tight enough to matter in production.
This story draws on original reporting from Paper.
