SSetu

Point at it. Say what to change.

Pick any element on your localhost app, describe the change in plain language, and send it straight to your coding agent. No copy-pasting prompts, no explaining where the element is.

The metaphor is a designer pointing at a screen and telling the engineer sitting next to them exactly what to change. Setu is the pointing finger. Your coding agent is the engineer.

How it works

  1. Pick an element — click the crosshair, hover to highlight, click to capture.
  2. Describe the change — plain language, or a structured edit type for precision.
  3. Queue as many as you like, then send them together.
  4. Your agent reads them through 8 MCP tools and makes the edits.
  5. Review — approve, or reject with a correction that your agent sees on its next attempt.

Connecting your agent

Setu talks to your coding agent through a small relay that runs on your own machine. There is nothing to install — add this to your agent's MCP config:

{
  "mcpServers": {
    "setu": {
      "command": "npx",
      "args": ["-y", "setu-relay@3", "--mcp", "--http"]
    }
  }
}

Needs Node.js 18+ and an MCP-capable agent such as Claude Code. The relay is published as setu-relay.

Your code never leaves your computer. Picks travel between the extension and your agent over a server on your own machine. Setu only activates on localhost, 127.0.0.1, and local HTML files — never on public websites. Read the privacy policy.