Publish & Save locally

Two commands — one safe, one a deploy. Rume defaults to the safe one.

Save locally

• Writes the change to source and verifies it landed
• No commit, no push, no deploy
• The default — an accidental production deploy is worse than an extra click

Publish

• Write + verify, then auto-commit and push
• Your host (Vercel, Netlify, etc.) auto-deploys on push
• Host detection is automatic from committed signals (vercel.json / .vercel/, netlify.toml)

Verification gate

Rume never deploys an unverified change. After a write, the panel polls the live computed style to confirm the edit landed as previewed before enabling Publish. If it can't verify, it won't let you ship.

One path to live

There is no separate "commit" button — Publish is the single path to live. It commits, pushes, and your host takes over. Working trees are gitignored for secrets (.env*, .rume/, internal docs), so deploy never ships your keys.