Keep your workflow
Same CLI, same session. cerver swaps the harness underneath — you don't relearn anything.
For developers
Run the same task on Claude and Codex in one session, keep whichever did it better, and never babysit a model that quietly fell behind. cerver keeps your workflow always on the best.
01 — The trap
Switching costs feel high, so you don't — and you quietly pay for it on every task. The fix isn't loyalty to one model; it's a workflow that checks, every time, and stays on whatever's winning right now.
02 — Compare in one command
One session, one prompt, a real diff — not vibes. The comparison runs itself; you just stay on the winner.
$ cerver run --compare claude codex "add idempotency to the webhook"
claude / sonnet passes · retries on 5xx
codex / gpt-5 passes · cleaner backoff ← better
→ you're now on codex for this task.
03 — Switch without losing the thread
Same CLI, same session. cerver swaps the harness underneath — you don't relearn anything.
Transcript, tools, and identity travel with the session across every swap.
Your machine, Vercel, or E2B — move compute mid-task without dropping a beat.
04 — Install
curl -fsSL https://cerver.ai/install.sh | bash
Bring your own compute. cerver charges nothing — your bill is whatever your provider charges, usually $0 at hobby scale.