Breakdance 3.0 and Skyelight: website feedback your AI agent fixes in the builder

Breakdance 3.0 shipped on October 26, 2026, and its headline feature is an AI agent that works directly inside the builder. Connect Claude Code, Codex or Cursor over MCP, and the agent can read your site's selectors and variables, edit pages, templates and Global Blocks, and preview its own work.

That covers building. Feedback is still the slow part: a client sends a screenshot, you work out which section they mean, then you explain it to the agent. Pair Breakdance with Skyelight and that step disappears. Reviewers pin comments on the live page, and the same agent reads them and makes the change in Breakdance.

We tried it the week 3.0 shipped. Here's the setup.

What you need

• Breakdance 3.0 with the Agent Connector. It needs WordPress 7.0 and PHP 8.1.
• A coding agent with MCP, such as Claude Code, Codex or Cursor.
• A Skyelight account and the Chrome extension. The free plan is enough to try it.

1. Connect Breakdance to your agent

In WordPress, open Breakdance › Settings › Agents & MCP and install the Agent Connector. A four-step wizard (Welcome, Install, Connect, Build) walks you through connecting your agent, and its last step has example prompts to try. If you skip it, the Run Setup Wizard button on the same screen brings it back.

2. Connect Skyelight to the same agent

Add the Skyelight MCP server to the same agent. In a terminal, run:

npx @skyelight/mcp init

It finds Claude Code, Codex or Cursor and shows the change before it writes anything. Restart the agent, and the first time it calls Skyelight, sign in once in the browser. Your agent now has two sets of tools: Breakdance's to change the site, and Skyelight's to read and answer feedback.

3. Pin feedback on the live page

Open the site in Chrome with the Skyelight extension's side panel open. Press C, click the heading, button or section you mean, and write the comment. Pin on the page itself, not inside the Breakdance editor, so the thread points at what visitors see.

Each comment becomes a thread pinned to that element. It records the page, the element, a redacted snapshot of the markup around it, the browser and window size, and any requests that failed just before the pin. That's what the agent will work from. Because the extension runs in your browser, it works on a staging site you're signed in to, with nothing added to WordPress.

4. Ask the agent to work through the threads

Give the agent one instruction that covers both sides:

Work through the open Skyelight threads on this site. For each one, find the element in Breakdance, make the change, preview it, and reply on the thread with what you changed. Ask me before changing a global selector.

For each thread, the agent:

1. Reads it from Skyelight with list_items and get_item: the comment, the page and the element.
2. Finds that page and element in Breakdance, and checks the site's selectors and variables so the change fits the design system.
3. Makes the change with Breakdance's tools, such as edit-post, and checks it with preview-element or preview-post.
4. Replies on the thread with post_update. The reply shows your name with a mark for the agent, so the reviewer sees what changed, on the element they pinned.

5. Check the fix and resolve

Open the page and look at each change yourself. When it's right, resolve the thread in Skyelight, or ask the agent to with set_status. Leave a thread open if it needs another pass: the next reply goes on the same thread, so the history stays with the element.

Why it works so well

Breakdance 3.0 lets agents work the way they already do on the web: they write HTML and CSS, and Breakdance turns it into elements and selectors. Skyelight hands them feedback in the same terms, the element and the markup around it, instead of a screenshot. The agent goes from the comment to the element to the change without anyone translating in between.

Tips

• One change per thread. “Make the hero heading shorter” and “the button colour is off” are two threads. The agent fixes and answers each one cleanly.
• Say how far a change should go. Breakdance turns CSS classes into global selectors, so a fix to one button can change every button that shares its selector. Say whether you mean this one or all of them.
• Work on staging. Point the agent at a staging copy of the site, review there, then publish.
• Keep a person in the loop. Resolve threads only after someone has looked at the change.

For more on connecting agents to feedback, see how to send website feedback to Claude Code, Cursor and Codex.

Frequently asked questions