Skip to content
PouncePounce Docs

Getting started

Two minutes, three steps.

1. Get the app on your phone

Section titled “1. Get the app on your phone”

2. Start Pounce on your computer

Section titled “2. Start Pounce on your computer”

Pick whichever feels most like you — they all do the same thing: start the Bridge on that machine and show a pairing QR.

Terminal window
npx use-pounce

That’s the fastest path, and it works in any terminal — even over SSH to a server on the other side of the world.

To make it permanent rather than one-off, run npx use-pounce configure: it detects what this machine is and offers you the desktop app or a Bridge that starts at login, then installs whichever you pick.

Prefer an app? On a Mac, download the desktop app (Pounce.dmg) — the Bridge is built in and the QR appears in the window. On Windows or Linux, grab the headless Bridge bundle from the same page. See Install for details on each.

3. Scan the QR

Section titled “3. Scan the QR”

Open Pounce on your phone, tap Sync a device, and point the camera at the code. (The built-in camera app works too — it opens Pounce straight to pairing.)

That’s it. Your machine’s agent sessions sync instantly, and the phone keeps a private, per-machine token so only you can connect. Pairing once is enough — when you’re away from home, Pounce reaches the same machine over its own secure tunnel automatically. No VPN, no port-forwarding, nothing else to set up.

What you’ll see

Section titled “What you’ll see”
  • Home — every agent, on every machine you’ve paired, with the threads that need your input floated to the top. Get a notification the moment one starts waiting on you.
  • A live session — reasoning, tool calls, and diffs streaming in real time. Reply, redirect, or answer prompts right there; hold to talk if your hands are full.
  • Changes — the diff for any session. Commit, push, or open a PR from your phone.
  • Spaces — your work grouped by project, with worktrees filed under the project they came from.
  • Search — every session you’ve ever run, across all four agents and every machine.
  • Activity — what you’ve built, what it cost, and which agent did it.

Next steps

Section titled “Next steps”
  • Pair more machines the same way — they all show up in one fleet.
  • Spaces — how Pounce organises projects, worktrees and machines.
  • Supported agents — what works with Claude Code, Codex, Cursor, and opencode.
  • Away from home — how remote access works, and how to pair a machine you only reach over SSH.
  • Agent instructions — reading the CLAUDE.md steering a project.
  • CLI reference — everything npx use-pounce can do.