Conversation-first pair programming

AI that commits from your laptop.

Evor turns chat into approved diffs, runs your Claude or Codex CLI under your auth, and opens the pull request from your own machine — under your git identity, with your teammates in the loop.

Get started Install the CLI
Evor · Chat
Add a footer with the current year
I'll create src/Footer.tsx and import it into the app layout.
src/Footer.tsxdiff
+ export function Footer() {
+   return (
+     <footer className="py-6 text-center text-xs text-zinc-500">
+       © {new Date().getFullYear()} Evor
+     </footer>
+   );
+ }
zsh — evor
$ evor login
→ opening browser to approve this machine…
✓ Authorized — token saved
✓ Started (pid 3519)

$ evor status
  status:   running
  backend:  wss://b.evor.live/agent
  claude:   /usr/local/bin/claude
  token:    set
How it works

Chat. Approve. Land real commits.

No magic. Every step is reviewable. Every change is a real commit by you, on a real branch, in a real pull request.

  1. 01
    Connect a repo

    Sign in with GitHub and import a repository. No access goes anywhere until you pick one.

  2. 02
    Pair your laptop

    evor login opens your browser, one click approves — the agent runs on your machine.

  3. 03
    Chat about changes

    Describe outcomes in plain language. Evor plans, proposes diffs, waits for you.

  4. 04
    Approve → PR

    Approved diffs get committed locally under your identity and pushed as a pull request.

Local-first

Your code, your keys, your commits.

Evor doesn't ship your code to a shared cloud worker. Every AI action runs in a daemon on your machine, reads your local checkout, and commits through your own git identity. Nothing you haven't approved ever lands in a repo.

  • Claude Code or OpenAI Codex CLIs run under your own subscription — your keychain auth never leaves.
  • Diffs land on disk first. Your editor and dev server see each change live, before you approve.
  • Git commits are authored by you, not an Evor service account. `git log` looks like you were there.
  • Per-user agent tokens — nobody else's sessions run on your machine.
~/evor-workspaces/acme/web
$ git log --oneline -3
a7f3c91 add footer with current year
bd2019f fix(auth): use github noreply email
3f0ac8e feat: pair programming loop

$ git config user.email
you@yourcompany.com   # your identity, not a bot

$ ls src/Footer.tsx
src/Footer.tsx        # landed on disk on approval
Team

Ship together without stepping on each other.

Per-repo memberships from your GitHub collaborators. Teammates see who's working on what, a summary of pushed diffs, and can start their own private review session — your chat never leaks.

GitHub-native team

Invite from your GitHub collaborators list. Members land on the same repo with roles (owner / editor / viewer).

Private sessions

Your chat is yours. Teammates see a summary of what landed — files touched, diffs pushed — never the transcript.

Review with your own agent

Open a teammate's task and spin up a private review session. Your local agent reads the branch, flags risks, proposes counters.

Install

Two commands. Thirty seconds.

Install the evor CLI, then evor login. Your browser opens, you click Approve, the daemon starts in the background.

Install
$ npm install -g @evorlive/evor
Pair this laptop
$ evor login
Status
$ evor status