Point at the bug. Your agent fixes it.

A small bug button on every page of a local project you switch it on for — on your phone over Wi-Fi, or in any browser on your Mac, where ⌥⇧L works too. Tap the thing that's broken, say what's wrong in a few words, and the report lands on your Mac with a screenshot, the requests that failed and the console errors around them, ready to hand to your coding agent.

No SDK, no package, no code change. With Tap to Fix on, Localdock adds one script tag to the project's HTML pages as they pass through on their way to the browser; switch it off and the pages are exactly what your server sent. If a page's Content-Security-Policy wouldn't allow the script, Localdock leaves that page alone and says so on the project, rather than rewriting your policy.

Claude Code and Codex. Hand over writes the report into the project's .localdock folder as a task and starts your agent in Terminal or iTerm, in that project. You pick the agent per project; a repo can suggest one in .localdock/config, but only you set the command that runs. Separately, the built-in MCP server — list_ports, get_free_port, cleanup — works with any MCP client, Cursor included. More: Localdock for AI coding agents.

Only when there is something to watch. If the report caught a failing request, Localdock marks it fixed when that same request comes back 2xx from the same project after you handed it over. A layout bug has no failing request, so you mark that one fixed with a click.

A picture of the page with your element marked, the element itself, the requests that failed, the recent console lines and your note — no cookies, no form values, no passwords. You see that list on the phone before you send it. Reports stay on your Mac for 30 days and never go to us; one reaches an agent only when you press Hand over, and then it goes to the agent you chose.

Anyone who can open a project you've shared, while Tap to Fix is on for it — that's the point when it's a client or a teammate. So reports are treated as untrusted: when you hand one over, what the sender wrote is fenced off, and your agent is told to read it as evidence to examine, never as instructions to follow.

Share the project on your Wi-Fi and it answers at dashboard.local on any device on the same network — click the QR button next to it in the menu bar and point your camera. It's off by default and switched on one project at a time; everything you didn't share is refused without revealing that it exists. Nothing to install on the phone.

Yes — move the project to "Internet" and you get a temporary HTTPS link anyone can open: a client, a colleague in another city, or a webhook provider like Stripe. Nothing to install, and they don't need an account or your Wi-Fi. The link carries a secret key, so anyone who reaches the address without it sees a page that names nothing. It expires after an hour and dies the moment you switch it off or quit. Tap to Fix works over it too.

No. The tunnel runs between your Mac and Cloudflare's network, so Cloudflare carries the traffic and terminates the TLS — we never see it. Our server's only involvement is handing your Mac a permanent address the first time you ever share, which needs your licence key and nothing else. It never learns your project names, your ports, or when a link is used.

For showing someone your own dev server from a Mac — yes, with a different shape: ngrok exposes a port, Localdock shares a project that already has a name, behind a key-gated link that expires in an hour, with nothing for the recipient to install — and they can tap a bug and send it to you. It's not a replacement for production ingress or always-on tunnels. The honest version, both directions: Localdock vs ngrok.

No setup at all. Any *.localhost name already resolves to your own machine — that's a web standard, handled by macOS and every browser. Localdock listens on port 80, reads the name you asked for, and forwards you to whatever port that project's server is on. No hosts file, no dnsmasq, no admin password.

From your project folders and container names, so most things are named correctly before you touch anything. Renaming is one click on the project's page in the Localdock window. A name another project already uses gets refused with a reason instead of silently stealing the address.

Yes. Localdock adds an address, it never takes one away. Your server keeps its port and keeps answering on it, so nothing in your setup has to change — and if Localdock isn't running, you simply lose the pretty name.

Yes. WebSockets, HMR, server-sent events and streaming pass through untouched. Localdock forwards raw TCP after reading the name; the one exception is Tap to Fix, which, while it's on for a project, adds its script tag to that project's HTML page loads and leaves everything else as your server sent it.

Then Localdock steps aside and serves on 7777 instead — your URLs become dashboard.localhost:7777, and settings tells you which port is live. Nothing breaks, and you can pick any port you like.

Nothing about your projects is ever sent to us — not names, ports, paths, reports or logs. The only call carrying anything about you is the licence check: licence key, an instance ID, your device name, nothing else. A project you share becomes reachable from your own network or through Cloudflare, which is the point; a report reaches a coding agent only when you hand it over.

The moment your payment clears you land on a download page with your licence key on it, and the same key is emailed to the address you paid with. Paste it into Localdock and you're done — no account, no waiting.

No subscription — $19 once, single device, every Localdock 2 update included, no account. The app is macOS 14 and later; the phones and browsers you test on can be anything.