Package Exports

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (cursor-local-remote) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Cursor Local Remote

Control Cursor from your phone, tablet or any browser on your local network. Great for monitoring and nudging Cursor while in the bathroom, watching a movie or cooking food.

A local web UI that talks to Cursor's CLI agent on your machine. No cloud, accounts or other bs just on your local network. Also added some rudamentary security so that you need a key to access it incase you have many in a Wifi network. Important to only use this on trusted network that are safe, because the security is easy to bruteforce if you are in the same network.

Good to know

This is essentially an easy way to use the Cursor CLI from your phone or any other device on your network.

You can start new sessions from the remote UI and they work fully: the agent runs, edits files, executes commands, everything. However, sessions started remotely won't appear in Cursor's desktop sidebar. This is a Cursor limitation, it stores conversation state in an internal in-memory store that can't be written from outside the process.

The remote UI can see all sessions, both ones started in the IDE and ones started remotely. You can monitor active desktop sessions in real time, browse and resume past sessions, or start fresh ones. Messages sent from the remote won't show up in the IDE's chat view, but the work the agent does (file edits, commands) happens on your machine either way.

Install

npm install -g cursor-local-remote

Then start it:

clr

A QR code pops up in your terminal — scan it from your phone and you're connected.

Features

Send prompts to Cursor's agent from any device on your network
Watch responses stream in — text, tool calls, file edits, shell commands
Pick a model — fetches your available models from Cursor
Switch modes — Agent, Ask, or Plan
Browse sessions — see all past Cursor sessions for the workspace
Live tail — watch an active desktop session update in real time
Resume sessions — continue any past session from the web UI
Stop / retry / copy — cancel a running response, retry, or copy any message

Usage

clr is the short alias for cursor-local-remote.

clr [workspace] [options]

Option	Description
`workspace`	Path to your project folder (defaults to cwd)
`-p, --port`	Port to run on (default: `3100`)
`--no-open`	Don't auto-open the browser
`--no-qr`	Don't show QR code in terminal

clr                          # current folder
clr ~/projects/my-app        # specific project
clr --port 8080              # different port
clr --no-open --no-qr        # headless-friendly

How it works

Phone / tablet / browser  ── LAN ──>  Next.js (0.0.0.0:3100)  ──>  cursor CLI (agent)
                          <─ stream ─

The CLI starts a pre-built Next.js server on your machine. When you send a prompt, the server spawns a headless agent process (agent -p <prompt> --output-format stream-json) and streams the NDJSON output back to the browser over HTTP. Session history comes from reading Cursor's own transcript files in ~/.cursor/projects/, so you see all sessions, not just ones started from this tool.

Authentication

Every launch generates a random token printed in the terminal. Access is granted by:

Scanning the QR code (encodes the network URL with the token)
Visiting the URL with ?token=<token> (sets an httpOnly cookie for 7 days)
Passing Authorization: Bearer <token> for API calls

You can also set a fixed token via the AUTH_TOKEN env var.

API

All endpoints require a valid token (cookie or Bearer header).

Endpoint	Method	Description
`/api/chat`	`POST`	Send a prompt. Returns an NDJSON stream of agent events (`system`, `user`, `assistant`, `tool_call`, `result`). Body: `{ prompt, sessionId?, model?, mode? }`
`/api/models`	`GET`	List available models from `agent models` (cached 5 min)
`/api/sessions/history`	`GET`	Session list or full transcript. `?id=<sessionId>` for messages + tool calls
`/api/sessions/watch`	`GET`	SSE stream for live session updates. `?id=<sessionId>` — pushes `update` events on file change

Environment variables

Variable	Description
`AUTH_TOKEN`	Fixed auth token (otherwise randomly generated each launch)
`CURSOR_WORKSPACE`	Workspace path (set automatically by the CLI)
`CURSOR_TRUST`	Set to `1` to pass `--trust` to the agent (auto-approve all tool calls)
`PORT`	Server port (default: `3100`)

Requirements

Node.js 20+
Cursor with the CLI installed (agent --version should work)
A Cursor subscription (Pro, Team, etc.)

Development

Contributions are welcome. Mainly created this so that I can use cursor when I don't feel like being at my desk. Whole project vibecoded with cursor, obviously.

git clone https://github.com/jon-makinen/cursor-local-remote.git
cd cursor-local-remote
npm install
npm run dev

License

MIT