Stop prompting your way to a 4px change.
Rume runs next to your dev server and lets you click any element on your real page, change it, and hand the rest to your own agent. Spacing, type, and color are written straight to your source — no tokens, no round trip.
npm i -D rume · works with Next.js 14–16 · your code never leaves your machine
Two kinds of change. Only one costs you tokens.
Dragging spacing is arithmetic. Swapping a font is a token change. Rume writes those itself. The agent is saved for the things that actually need judgment.
Click the real element
Rume runs beside your dev server and knows which line of source every element on screen came from. Click it and the panel becomes that element.
source resolved — 0 tokensChange it and watch it move
Type, spacing, size, color, radius. Values snap to your own design tokens, so nothing lands off-system. Changes stack up until you're happy.
written to source — 0 tokensSend the rest to your agent
"This section feels cramped" goes to your agent as one precise task — exact file, exact line, the surrounding code, your tokens. It lands on the first try.
one task, not five promptsRume doesn't ship an agent. You already have one.
Point it at whatever you run — Claude Code, OpenClaw, Hermes, a local CLI, an HTTP endpoint. Rume writes the task, a watcher wakes your agent, your agent edits your repo. Nothing about your setup changes.
- Requirementyour agent needs to be able to edit files on its own
- Not requiredan account, a cloud sandbox, or our model
- Your keysyou pay your provider directly — we never touch inference
{ // point at your dev server "devUrl": "http://localhost:3000", "agent": { "triggerType": "shell", "shellCommand": "claude -p'read .rume/tasks and apply it, then delete the file'" } } # or point it at anything that listens # "triggerType": "http" # "httpEndpoint": "http://localhost:8080/run"
Your code never leaves your machine.
Rume isn't a hosted editor with a copy of your repo. It's a process on your laptop, bound to loopback, writing to the folder you're already working in.
- Loopbackbinds to 127.0.0.1 — never your network
- Token-gatedevery request carries a per-session token
- Sandboxedwrites can't escape your project root
- No secrets.env and keys are never read or sent
- Your deploywe edit source; you ship it however you already do
The editor is free. Always.
If it runs on your machine, you don't pay for it. The paid tier is the part that needs a server to exist — history you can roll back, and a link you can send someone.
The whole local editor. No account.
- Click-to-edit on your real pages
- Direct source edits, unlimited
- Comments → your agent
- Gated commit
For solo builders and freelancers.
- Everything in Free
- Change history + rollback
- Shareable preview links
- Sync across machines
When more than one person edits.
- Everything in Pro
- Shared history
- Review + comment threads
- Roles and permissions