Skip to contentSkip to footer

Changelog

  • Polypane 32 Latest

    Polypane 32 adds a whole new way of accessing Polypane through Automation, a WebMCP panel, deeper metadata insights, and improvements across many panels and workflows.

  • Polypane 31

    Polypane 31 has a new Canvas layout, many improvements to the elements panel, new iPhone presets and Chromium 155.

  • Polypane 30.1

    Polypane 30.1 adds selector specificity highlighting to the elements panel, a new server-sent HTML view in the sources panel, passkey support in Linux and a bunch of improvements and fixes

Full Changelog
Start Free Trial
Introducing

Automation

Your agents work alongside you in Polypane. They see every pane, every check and every panel, and get the same feedback you get.

claude — ~/my-project

Polypane is being controlled by Claude CodeControlled by Claude CodeWaiting for instructions

Switch the bare-bones webview your agent has for all of Polypane.

Agents check their work in one hidden viewport with no accessibility checks and no real idea of what they're looking at. With Automation, they use the same Polypane you do.

Connect in one click

Claude Code, Cursor, Codex, VS Code, Zed and more. Polypane installs its MCP server and an agent skill for you.

Every pane, every check

Get reports from all of Polypane's checks, across all your panes.

Fix “this”

Point Polypane at an element and ask your agent to fix “this”. It gets all the info it needs to make the fix.

See every action

The automation bar shows which tools control Polypane and what they're doing. Open the activity log to see everything that happened.

Polypane notices, so your agent does too

Overflow, console errors, web vitals and resource use come with every response. Change the tab yourself and the agent hears about that too.

You are in control

Logging in, a CAPTCHA, a choice only you can make: Agents wait until you're ready.

Work with your agents

Polypane doesn’t bring its own AI. It plugs into the agent you already use, with your codebase, your instructions, your skills and your way of working. Polypane sets itself up in these tools with one click or a few steps, and installs its agent skill along with it.

  • Claude Code
  • Claude Desktop
  • Cursor
  • Codex
  • VS Code (GitHub Copilot)
  • JetBrains IDEs
  • Zed
  • Gemini CLI
  • Antigravity
  • Cline / Roo Code
  • OpenCode
  • Devin Desktop
  • Oh my pi
  • + any MCP client

You stay in control while your agent joins you.

You and the agent both work on the same thing, instead of the agent working in a hidden webview. Most actions just run, so working together stays smooth.

All actions are tracked. Risky actions require your permission, and secrets stay hidden from your agent.

Allow Claude Code to do something risky?

Run generated JS in the Desktop pane. The script can read and change anything on the page. Remembering "Allow" allows every script from now on, not just this one.

Show the script
document.querySelectorAll('img:not([alt])').length

Local only

Runs on your device over stdio. No network port is opened.

No passwords

Agents never fill in password or one-time-code fields. You log in yourself.

Secrets stay hidden

Auth headers, httpOnly cookies and passwords are kept from agents.

Dialogs are yours

Anything that asks for confirmation is left for you to answer.

Just ask

Ask for one thing at a time or hand over a multi-step task. Polypane's agent skill teaches your agent to check every pane, read the notices and fix what it finds. The work happens in Polypane, so it's as token-efficient as possible.

Quick things

  • Open localhost:3000 with an iPhone, an Android and a desktop pane
  • What is the heading structure on this page?
  • Check the social media previews of this page
  • Get a screenshot of every pane

Whole tasks

  • Open localhost:3000 in Polypane and fix any accessibility issues the report finds.
  • The header overlaps the content on small screens. Find out why in Polypane and fix it.
  • Compare the local pricing page to production.
  • Create a new project for my website and switch to it. The production url is example.com and staging is staging.example.com.

Not just for agents.
Script it.

Every tool is also available from the command line with polypane --mcp, and from Node with the MCP SDK.

Hook Polypane's checks into your own scripts and pipelines, deterministic and repeatable.

Terminal
$ polypane --mcp help run_report
$ polypane --mcp call run_report '{"checks": ["a11y", "headings"]}'
check.js
import { Client } from '@modelcontextprotocol/sdk/client/index.js';
import { StdioClientTransport } from '@modelcontextprotocol/sdk/client/stdio.js';

// connect to Polypane over stdio
const client = new Client({ name: 'my-script', version: '1.0.0' });
await client.connect(new StdioClientTransport({ command: 'polypane', args: ['--mcp'] }));

const report = await client.callTool({ name: 'run_report', arguments: { checks: ['a11y'] } });
console.log(report.structuredContent.result.summary);

Automation is included with Polypane and available for all users.

Windows, macOS and Linux

Install Polypane on your favorite operating system (and architecture).