CurxorCurxor
Sign in

Quickstart

Five minutes to your first change: pick an element in the browser, describe it, and let the AI edit the code.

Before you start

  • Your project runs locally with vite / next dev
  • The extension badge shows ON
  • The CLI is running: curxor status shows ● running and Local: http://127.0.0.1:51999
It has to be dev mode. Production builds carry no source paths, so curxor cannot locate the element's source.

Your first change

  1. Open your dev page

  2. Select an element and describe the change

  3. Send it — where the two routes split

    MCP routeClick Create task; a code (CX-XXXXXX) is copied to your clipboard — paste it into your editor's AI chat.
    Agent routePick an agent (Claude Code / Cursor / Pi) from the select-agent menu and let it take over.

  4. The AI edits, hot reload shows it

    The AI reads that element's context — source location plus screenshot — and edits the code. Hot reload shows the result right away.

Link your project

macOS / Linux auto-detect running dev projects. On Windows you have to link it manually, otherwise curxor doesn't know which project to resolve source from:

curxor attach http://localhost:5173
Omitting the origin makes curxor scan common ports, but writing it out is more reliable.
Previous
Installation
Next
MCP setup

For AI agents: llms.txt · llms-full.txt