Edityy

Edityy puts a visual editor on the site you already run. You change the page in the browser, and your coding agent makes the change in the code.

What it does

The launcher sits in the bottom-right corner of your site. Click it, and the page answers to you.

• Point at an element and click it. The page selects it.
• Change the type, the colour, the spacing, the fill, the border and the shadow.
• Type new words into the text that is already there.
• Ask your agent for style variations of one element.
• Hand the edits over as a prompt, a file, or a message over MCP.

Every edit is one inline style on the live page. Edityy writes nothing to your source code. You keep the codebase as the source of truth, and the agent changes it.

your codebase → your dev server → edityy middleware → the page, with a launcher

How the launcher gets there

The middleware serves /__edityy/edityy.js and injects a relative script tag into the HTML your dev server already returns. A relative URL follows whatever port your server runs on, so there is nothing to configure.

The launcher mounts a host element that is fixed to the viewport and ignores pointer events. It renders inside an open shadow root, so your CSS cannot restyle it and it cannot leak styles back out.

Where the edits go

There are three ways to hand the edits over. Each one suits a different habit.

• Copy for an agent copies the edits as Markdown. You paste them into your agent yourself.
• Save to project writes the edits to .edityy/changes.json in your project.
• MCP lets the agent read that same file, with no copy and no paste.

Next

• Install puts the launcher on your site. One line of config.
• The editing mode explains the dock and the keyboard.
• API lists the options, the exports and the events.