Remote Access

Kick off a long agent run at your desk, then keep an eye on it from the couch. Remote Access serves the chat to your phone over your local network — you can watch it work, send prompts, approve permissions, and switch modes, all from the browser on your phone.

EnableLakshX: Enable Remote AccessStatus bar$(radio-tower) Remote: <port>

Turning it on

Run LakshX: Enable Remote Access from the command palette (it’s off by default).
Confirm the warning — this grants view and control, not just viewing.
Scan the QR code that appears with your phone’s camera.

The status bar shows Remote: <port> while it’s on; click it to bring the QR back. Run LakshX: Disable Remote Access to stop the server.

View AND control

Anyone who scans the QR can send prompts, approve permission requests, and switch modes — exactly as if they were sitting at your keyboard. Only share the QR with people (and on networks) you trust, and disable it when you’re done.

How it works

LakshX starts a small HTTP server on your local network.
Pairing is protected by a random token generated per session, held in memory only — nothing is written to disk.
The QR encodes the pairing URL with that token; control actions are token-gated with timing-safe checks.

Permission sync

Permission prompts stay in sync across every surface. If a prompt is waiting and you approve it on your phone, it resolves on the desktop too (and vice-versa) — you’ll never have the same request hanging in two places.

Built for mobile

The phone view is a real mobile composer — it auto-grows, keeps the input above the keyboard, and escalates reconnects — so steering a run from your phone actually feels usable, not like a shrunken desktop page.