Changelog

Pounce 1.5.1 — the same app on every platform.

macOS (14+, Apple Silicon) — Pounce.dmg Signed and notarized. Open it, drag Pounce to Applications, launch. Updates itself from here on.

Windows (x64) — Pounce-1.5.1-Windows-x64.zip Extract it, then run Pounce-Setup.exe from the extracted folder — it needs the .installer folder beside it. Unsigned for now, so if SmartScreen appears choose More info → Run anyway. Updates itself.

Ubuntu / Debian (x64, arm64) — Pounce-1.5.1-Linux-<arch>.deb sudo apt install ./Pounce-1.5.1-Linux-<arch>.deb, then launch Pounce from your applications menu. Installs to root-owned /opt, which the in-place updater can't write to — update by installing a newer .deb.

Other Linux (x64, arm64) — Pounce-1.5.1-Linux-<arch>.tar.gz Extract and run ./installer. Installs under ~/.local/share, adds a desktop entry, and self-updates.

Any machine, including one you only reach over SSH — no download needed:

npx use-pounce configure

Headless / server — pounce-bridge.zip Unzip, then install.sh (Linux/macOS) or install.ps1 (Windows). Needs Node.js on the host. No GUI; pair from the phone app.

The phone apps ship separately on the App Store and Google Play.

appcast.xml is the macOS update feed, not a download.

Download the Bridge for your computer, run it, and scan the QR with the Pounce app.

• macOS (Apple Silicon): Pounce.dmg — open, drag Pounce to Applications, launch. Signed + notarized.
• Windows (x64): Pounce-Setup-Windows.exe — run it. Unsigned for now: if SmartScreen appears, choose More info → Run anyway.
• Ubuntu / Debian (x64 / arm64): Pounce-Linux-<arch>.deb — sudo apt install ./Pounce-Linux-<arch>.deb, then launch Pounce from your applications menu.
• Other Linux (x64 / arm64): Pounce-Setup-Linux-<arch>.tar.gz — extract, run ./installer (installs to ~/.local/share and adds a desktop entry).

Once running, Pounce sits in the tray: it shows today's usage and your plan quota, and "Show pairing window" brings up the QR to scan.

The stable-* files are auto-update artifacts — installed apps pick them up from the rolling bridge-latest release automatically. The .deb is the exception: it installs to root-owned /opt, which the in-place updater can't write to, so update it by installing a newer .deb. The .tar.gz install self-updates.

Two fixes from the 1.2.0 work land on the Mac:

• Screenshots from other machines render. An image an agent drops into a reply names a file on the machine the thread ran on; viewing that thread from anywhere else used to draw a broken image. It now loads through the host’s bridge.
• Switching light/dark no longer wipes the sidebar. The sidebar’s backdrop froze its color from the previous theme, which could leave the whole panel illegible until a restart.

Existing installs update themselves automatically.

Until today, installing Pounce on Linux or Windows got you a small tray app whose one window showed a pairing QR — the real interface lived on your phone.

1.2.0 opens the full Pounce UI on the desktop: the sidebar of every machine and session, tabs across live conversations, streaming transcripts with images you can zoom, activity and spend dashboards, theme and appearance switching. It’s the same interface the macOS app has had — the same code, in fact — now everywhere Pounce runs.

A few things that make this more than a window dressing:

• Zero-config on its own machine. The app pairs itself with the bridge it ships — open it and your sessions are just there.
• Your browser is a client now too. The bridge serves the same UI over the LAN, so any machine on your network can open Pounce at this machine’s address and pair with one link — no install.
• Port collisions no longer kill the app. If something else holds Pounce’s port, a second Pounce attaches to the first, and a foreign program triggers a clean fallback to the next free port.
• Images across machines. Screenshots an agent drops into a reply now load from the machine the thread ran on — on desktop, web, and your phone, where they used to render as broken images for any remote thread.

The pairing QR hasn’t gone anywhere — it moved to the tray menu.

On macOS the native desktop app remains the Pounce experience, and the tray app stays a tray. Existing installs on every platform update themselves automatically.

Desktop app 1.0.45. Auto-updates via Sparkle; requires macOS 14+.

• macOS: Pounce.dmg — signed + notarized. Open, drag Pounce to Applications, launch.
• Windows / Linux (headless bridge): pounce-bridge.zip — unzip, then install.sh (Linux/macOS) or install.ps1 (Windows). Needs Node.js on the host; pair from the mobile app on the same Wi‑Fi.

Download the Bridge for your computer, run it, and scan the QR with the Pounce app.

• macOS (Apple Silicon): Pounce.dmg — open, drag Pounce to Applications, launch. Signed + notarized.
• Windows (x64): Pounce-Setup-Windows.exe — run it. Unsigned for now: if SmartScreen appears, choose More info → Run anyway.
• Ubuntu / Debian (x64 / arm64): Pounce-Linux-<arch>.deb — sudo apt install ./Pounce-Linux-<arch>.deb, then launch Pounce from your applications menu.
• Other Linux (x64 / arm64): Pounce-Setup-Linux-<arch>.tar.gz — extract, run ./installer (installs to ~/.local/share and adds a desktop entry).

Once running, Pounce sits in the tray: it shows today's usage and your plan quota, and "Show pairing window" brings up the QR to scan.

The stable-* files are auto-update artifacts — installed apps pick them up from the rolling bridge-latest release automatically. The .deb is the exception: it installs to root-owned /opt, which the in-place updater can't write to, so update it by installing a newer .deb. The .tar.gz install self-updates.

Desktop app 1.0.43. Auto-updates via Sparkle; requires macOS 14+.

• macOS: Pounce.dmg — signed + notarized. Open, drag Pounce to Applications, launch.
• Windows / Linux (headless bridge): pounce-bridge.zip — unzip, then install.sh (Linux/macOS) or install.ps1 (Windows). Needs Node.js on the host; pair from the mobile app on the same Wi‑Fi.

The sidebar, tab strip, and window shell used to re-render on every sync tick, even when nothing about them had changed. Each now subscribes to just the state it draws, so a busy fleet no longer costs you a redraw of the whole window.

Existing installs update themselves automatically.

• The app stops re-rendering itself. Every tab used to redraw on each sync tick, whether or not anything had changed. State now lives where it is read, so scrolling and streaming stay smooth while the fleet syncs behind you.
• The attention shelf no longer overstates things. A thread you can pick back up is now marked as exactly that, and a run that failed can be dismissed instead of sitting in the shelf forever.
• Machines added over SSH keep the name you dialled. The address you typed is the name you see, and a machine added over SSH is shown for what it is rather than guessed at from its hostname.
• See what each agent’s plan has left. Usage is metered per agent, a project lists the skills it has available, and worktree disk can be reclaimed from the app.
• Fixes: the paste-a-code header is actually tappable, a disclosure that can’t animate no longer tries to, and the Changes sheet renders correctly on device.

Android ships the same release as version code 21.

Desktop app 1.0.42. Auto-updates via Sparkle; requires macOS 14+.

• macOS: Pounce.dmg — signed + notarized. Open, drag Pounce to Applications, launch.
• Windows / Linux (headless bridge): pounce-bridge.zip — unzip, then install.sh (Linux/macOS) or install.ps1 (Windows). Needs Node.js on the host; pair from the mobile app on the same Wi‑Fi.

Desktop app 1.0.41. Auto-updates via Sparkle; requires macOS 14+.

• macOS: Pounce.dmg — signed + notarized. Open, drag Pounce to Applications, launch.
• Windows / Linux (headless bridge): pounce-bridge.zip — unzip, then install.sh (Linux/macOS) or install.ps1 (Windows). Needs Node.js on the host; pair from the mobile app on the same Wi‑Fi.

Iroh p2p tunnel binaries for off-LAN Pounce pairing. Downloaded automatically by npx use-pounce; or drop the binary for your platform into ~/.pounce/bin/.

Desktop app 1.0.40. Auto-updates via Sparkle; requires macOS 14+.

• macOS: Pounce.dmg — signed + notarized. Open, drag Pounce to Applications, launch.
• Windows / Linux (headless bridge): pounce-bridge.zip — unzip, then install.sh (Linux/macOS) or install.ps1 (Windows). Needs Node.js on the host; pair from the mobile app on the same Wi‑Fi.

Desktop app 1.0.39. Auto-updates via Sparkle; requires macOS 14+.

• macOS: Pounce.dmg — signed + notarized. Open, drag Pounce to Applications, launch.
• Windows / Linux (headless bridge): pounce-bridge.zip — unzip, then install.sh (Linux/macOS) or install.ps1 (Windows). Needs Node.js on the host; pair from the mobile app on the same Wi‑Fi.

Until now a machine’s agent history was yours alone. That’s the right default and a bad ceiling: the person debugging beside you can’t see what you already tried, and neither can your own laptop when the work happened on the build box.

Machines running Pounce now find each other on the network, and one can ask another for access. The owner decides what and for how long. The answer is always read-only — browse threads, messages, diffs and search, but never send a turn, run a command, or read the machine’s setup.

You can’t tick a project you’ve never seen, so asking happens twice. First a short preview, good for nothing but a catalog: project names with counts and dates, and a search over thread names. No messages, no paths, no branches, and it lapses in five minutes. You pick from that, then ask for read access to what you picked. Both steps stop at a person — nothing is ever granted automatically. Each request shows the same six-digit code on both screens, so the one approving can tell a colleague’s laptop from a stranger on the café wifi.

Scope is a real boundary, not a filter. A grant reaches an allowlist of read-only routes, so anything added to Pounce later is closed to it by default. Ask for a thread outside your scope and you get “not found” rather than “forbidden”, because the difference would map what else is on the machine. Threads started later in a project you shared do appear — the project is what was agreed to, not a snapshot of that moment.

And it ends. An hour, eight hours, a day, a week, or never. When it lapses or you revoke it, the other machine is told exactly that, so the threads leave its sidebar instead of lingering as “offline”. Off-network access rides its own peer-to-peer tunnel per grant, which is closed at the same moment.

Your computer stays hidden until you make it visible. Others would see its name, and a computer’s name is usually a person’s, so Pounce keeps quiet on the networks you join until you say otherwise — from the app, the page, or pounce peers --visible on. Staying hidden doesn’t shut you out: a computer that knows your address can still ask, and you can still ask it.

All of it lives in the Bridge, which means it works everywhere the Bridge does. The Mac app has it in the sidebar; on Windows, Linux, or a server you’ve SSH’d into, open http://127.0.0.1:8099/peers in a browser, or stay in the terminal:

pounce peers                       # who's nearby, who's asking, who has access
pounce ask work-laptop --spaces api
pounce approve 418207 --hours 8
pounce revoke e1f71ab0

How sharing works →

Two things that should have been one thing were showing up as several.

Worktrees now live with their project. If you cut worktrees off a repository — by hand or through a tool that makes them for you — they group under that project instead of scattering into rows of their own. Pounce works this out by asking git rather than reading the path, so it holds for whatever made the worktree, and keeps holding for branches you merged and deleted long ago. On one machine here that turned 53 entries into 36.

And a machine you’ve already paired stays one device. Identity now comes from the machine itself rather than the address your phone reached it at — so pairing the same computer at home, on a café’s wifi, and after your router hands out a new lease no longer files it three times. Where duplicates already existed, their sessions move onto the device you kept rather than being dropped.

Both fixes live in the Bridge, so they arrive with the desktop app or with npx use-pounce — nothing to configure.

Every coding agent starts from scratch. It can’t see what you tried in a different tool yesterday, or which approach you already ruled out.

pounce mcp fixes that. One line and Claude Code — or Cursor, or anything else that speaks MCP — can search your whole history across Claude Code, Codex, opencode and Cursor:

claude mcp add pounce -- npx use-pounce mcp

Five tools: search everything, list sessions, read a session, read the messages you flagged as important, and see what’s been worked on lately. It’s read-only and entirely local — nothing leaves your machine, and no Pounce server is involved.

The desktop app is now Apple Silicon only. Intel Macs are no longer supported — if you’re on one, run npx use-pounce and drive that Mac from your phone instead.

Also in this release: modals all have a visible way out, project context is verified on the desktop, and cost is reported straight from the agent rather than estimated. Existing Apple Silicon installs update themselves automatically.

npx use-pounce now shows a single pairing QR the moment it starts — and if remote access comes up a beat later, the same code is upgraded silently behind the scenes. No second QR, no re-scan; just a friendly status line when the machine becomes reachable from anywhere.

Cursor joins the desktop app too: cursor-agent sessions stream live in the two-pane layout with the rest of your fleet. Existing installs update themselves automatically.

• Search everywhere. Search across every machine, project, and conversation in your fleet — or within a single thread — and jump straight to the matching message.
• Cursor support. Sessions from the Cursor CLI (cursor-agent) now show up alongside Claude Code, Codex, and opencode — with full history.
• Assorted streaming and scrolling fixes for long, busy sessions.

First standalone release of pounce-tunnel, the peer-to-peer engine behind “works from anywhere”. The CLI downloads the right binary for your platform automatically on first run; you can also drop one into ~/.pounce/bin/ yourself.

The new use-pounce CLI is on npm. One command starts the Bridge in the background, prints a pairing QR right in your terminal, and waits for your scan.

• Works over SSH — the QR carries the machine’s tunnel identity, so you can pair a remote server your phone shares no network with. No VPN, no port-forwarding.
• Random per-machine pairing token, kept in ~/.pounce.
• pounce status, pounce logs, pounce stop, pounce qr subcommands, plus --lan for Wi-Fi-only pairing.

The Android app is in internal testing on Google Play — same remote, same fleet, same one-scan pairing as the iPhone app. Public release soon; it will be announced here the day it’s out.

The Bridge now hosts the Cursor CLI (cursor-agent) with the same depth as Claude Code, Codex, and opencode: full session history from disk, live streaming while it works, and replies from your phone.

Pounce moved to the pounce-ai GitHub org and this site moved to use-pounce.com, with a full redesign — and every screenshot on it is now a real capture of the current app.

Agents ask questions — permission dialogs, plan approvals, “which option?” pickers. Pounce now detects any interactive CLI prompt, whatever its shape, and lets you answer it from your phone. Nothing stalls at your desk waiting for a keypress again.

A rapid first week for the desktop app:

• 1.0.2 — automatic updates. From here on, the app keeps itself current.
• 1.0.3 — pairing fix plus a Diagnostics panel.
• 1.0.4 — sidebar filters and Codex fixes.

The Bridge now brings up Pounce’s own secure peer-to-peer tunnel automatically, and the pairing QR carries everything the phone needs to reach that machine from any network. Pair once on Wi-Fi, then steer your agents from the gym, the train, anywhere — no VPN, no port-forwarding, no third-party relay account.

The first Pounce desktop app for macOS: the whole Pounce experience — fleet, live sessions, filters, diffs — in a native window, with the Bridge built in. Signed and notarized; macOS 14+.

The debut release. Claude Code, Codex, and opencode across every machine you own — live streaming, voice input, “needs you” triage, diff review, and one-tap shipping, from your iPhone.