FireCursorBack to product

Security

A narrow, local-first control plane.

FireCursor connects Android and browser control surfaces to the agents on your computer without hosting or mirroring your workspace.

Updated October 9, 2026

Connection model

The Cursor extension or the Windows app starts a local WebSocket server and opens a temporary Cloudflare tunnel. The Android app and browsers connect through the tunnel's TLS connection.

The host also accepts unencrypted ws:// connections from your local network, which only development builds of the Android app use; the released app and browsers refuse cleartext. Every connection requires the same bearer token.

Pairing and access

A random high-entropy token is encoded in the pairing QR code. The Android app normally encrypts pairing details with AES-256 through Android Keystore. If encrypted storage cannot recover, credentials remain process-local and are not persisted; the user signs in or pairs again after restart. The desktop side uses Cursor or VS Code secret storage.

Current releases require both the pairing token and a signed-in FireCursor account. Android and the web Command Center each obtain a five-minute, single-use extension capability from Supabase over HTTPS, identifying the computer only by a SHA-256 hash of its pairing token. The desktop host redeems the capability over HTTPS and never receives the user's Supabase session token.

Treat the QR code, pairing link, and pairing token like a password. Account checks reduce unauthorized reuse but do not make a shared pairing code safe. If one was exposed and your desktop host offers Reset pairing (FireCursor: Reset Pairing in Cursor), use it: the token rotates and every paired phone and browser is signed out at once.

Browser access

The web Command Center at firecursor.com/app/ connects your browser directly to your computer's tunnel. FireCursor's servers deliver the page and issue the account check; they do not relay prompts, source code, or agent output.

Pairing links carry the token in the URL fragment, which browsers never send to a server, and the page removes it from the address bar as soon as it is read. Desktop hosts with browser support receive the token in a WebSocket subprotocol header rather than the connection address and refuse browser connections that come from other websites. Older hosts receive it in the connection address over the TLS tunnel, and the Command Center labels them for update.

Saved pairings stay in that browser's local storage, separated by account, and are removed when you forget a computer or sign out. While you are signed in, anyone using that browser profile can control your paired computers, so use a profile you trust.

Workspace boundaries

  • Remote file and git operations are real-path checked and confined to the open workspace and supported Cursor worktrees.
  • Files under .git are denied to the remote file browser.
  • Prompts are passed through the selected provider's supported local interface without shell command reconstruction by FireCursor.
  • Uploads are limited to 10 MB and stored inside .firecursor/attachments in the workspace.

Agent-provider processing

FireCursor keeps workspace operations on your computer. Cursor, OpenAI Codex, or Anthropic Claude may still process prompts, source context, tool results, and model output under the account, plan, and privacy settings you use with that provider. FireCursor does not change those service boundaries.

Codex authentication remains owned by the official app-server and its managed ChatGPT browser flow. Claude subscription authentication remains owned by Claude Code; FireCursor strips API and cloud-provider overrides from subscription Channel sessions and never receives the subscription credential.

Claude Code and Cowork require Claude Pro, Max, or an eligible organization plan. The optional Anthropic API fallback is billed separately. Claude Desktop handoffs open separate, user-reviewed sessions that are not mirrored into FireCursor.

Review and recovery

Each FireCursor session starts with a git-tree checkpoint, including untracked files without modifying your real index. Diff review and Undo All compare against that checkpoint. Undo creates a safety snapshot first, but it is not a substitute for your own backups or version control.

Report a concern

Send a concise reproduction and affected version to hello@firecursor.com. Do not include pairing tokens, credentials, private source code, or unredacted workspace paths.