Replace port numbers with stable, named .localhost URLs for local development. For humans and agents.
- "dev": "next dev" # http://localhost:3000
+ "dev": "portless run next dev" # https://myapp.localhostportless runs a local reverse proxy and gives each dev server a name. Your app listens on a free port that portless assigns, and you open https://<name>.localhost instead of remembering which port it took. The URL stays the same across restarts, so bookmarks, cookies, OAuth redirects, and an agent's test script keep pointing at the right app.
npm install -g portlessTo pin the version per project, install it as a dev dependency with npm install -D portless. portless is pre-1.0, so contributors may run different versions, and a change to the state directory format between releases can require running portless trust again.
From a project with a "dev" script in package.json:
portless
# -> runs "dev", https://<project>.localhostPass arguments to the script after --, so portless -- --inspect runs dev with --inspect. Forwarding arguments into a script with shell operators or a comment exits 2; run the command directly or make the script a single command. In Turbo mode only the root script is checked, and Turbo passes the arguments to each package script unchanged.
The name comes from package.json, the git root, or the directory. Pass a name and a command to choose both:
portless myapp next dev
# -> https://myapp.localhost- The proxy starts on the first run. It serves HTTPS with HTTP/2 on port 443, so the first run creates a local certificate authority, adds it to the system trust store, and may ask for
sudo. Use--no-tlsfor plain HTTP, or--unprivilegedto skipsudo(Unprivileged mode). portless run <cmd>infers the name and detects git worktrees. In a linked worktree, the last/segment of the branch becomes a subdomain, sofix-ui.myapp.localhostandmyapp.localhostrun side by side. Use--prefixorPORTLESS_PREFIXto set the label, or configure the label style and hostname template.- A name with dots is a subdomain:
portless api.myapp pnpm startserveshttps://api.myapp.localhost. PORTLESS=0 pnpm devruns the command directly, without the proxy. Commands such asportless getandportless liststill run normally.
The full walkthrough is in Getting started.
Each app gets a random port from 4000 to 4999 through the PORT environment variable, and registers a route from its hostname to that port. The proxy forwards https://<name>.localhost to the route. Most frameworks read PORT. For those that don't, such as Vite, Astro, Angular, Expo, and Wrangler, portless adds the matching port and host flags to the command (Port assignment).
Outside LAN mode, the proxy listens only on 127.0.0.1 and ::1. It keeps /etc/hosts in sync for route hostnames, which custom TLDs such as .test need. If a route hostname will not resolve, the command that registered it warns and points you to portless hosts sync.
To reach an app from another device or share it, use LAN mode for phones on the same network, or Tailscale, ngrok, or a Cloudflare quick tunnel with --tailscale, --ngrok, or --cloudflare.
portless writes its own status lines to stderr, so stdout carries only your app's output. A non-empty NO_COLOR disables color, while FORCE_COLOR=0 disables it and FORCE_COLOR=1 forces it.
Use --upstream to route an alias to an HTTP or HTTPS service listening on loopback:
portless alias api 8080 --upstream https
portless alias api 8080 --upstream https://api.internal
portless alias api 8080 --upstream http://api.internalThe positional port always dials loopback. https enables TLS and preserves the incoming
Host header. An https:// authority enables TLS and overrides Host with the full
authority, including its optional port. SNI uses a DNS hostname without the port;
IP addresses are not sent as SNI. An
http:// authority overrides Host without TLS. This setting does not
change client-facing proxy TLS. Authorities accept only a hostname or IP address with an
optional port, without credentials, paths, queries, fragments, or whitespace.
portless list --json includes each route's upstream object when one is set, with the
same tls and host values.
Upstream TLS connects only to an HTTP/1.1 backend on loopback. Portless disables certificate verification, so TLS does not authenticate backend identity, even through an SSH tunnel. Restart the proxy daemon after upgrading portless.
An optional portless.json sets the name and script. In a monorepo, one file at the root covers every workspace package, and portless from the root starts all of them:
{
"apps": {
"apps/web": { "name": "myapp" },
"apps/api": { "name": "api.myapp" }
}
}A "portless" key in package.json works too. Fields, precedence, Turborepo setup, and environment variables are in Configuration.
Install the portless skill into an agent harness from skills.sh:
npx skills add vercel-labs/portlessFor MCP clients, portless mcp starts an MCP server over stdio. The default core profile lists routes, looks up URLs, and manages static aliases. --tools all adds proxy control and diagnostics:
{ "mcpServers": { "portless": { "command": "portless", "args": ["mcp"] } } }The server does not start dev servers. Agents run portless run <cmd> in a shell. See MCP server.
Run portless --help for the command list and common app options. Use portless proxy --help for proxy options, or portless <command> --help for command details. --help and -h print help and never run the command. After run <cmd>, compose <subcommand>, or --, they belong to the wrapped command, so portless run next dev --help passes --help to Next.js. Usage errors, such as an unknown flag, a missing argument, or a command that needs --yes without a terminal, exit with code 2; other failures exit with 1. Wrapped commands (run, named apps, and compose) keep their own exit code. Value flags for run, named apps, and service install accept either --flag value or --flag=value. Use portless list --json or portless get <name> --json for JSON output.
| Group | Commands | Docs |
|---|---|---|
| Run apps | portless, run, <name> <cmd>, get |
Run an app, Get a service URL |
| Static routes | alias, compose up, compose down |
Alias, Docker Compose |
| Proxy | proxy start, proxy stop, service install, service status, service uninstall |
Proxy control, OS startup service |
| HTTPS and DNS | trust, hosts sync, hosts clean |
HTTPS, Hosts |
| Inspect and clean up | list, doctor, prune, clean |
Doctor, Prune orphans, Clean up |
| Agents | mcp |
MCP server |
portless prune removes stale routes and shares without killing unrelated port holders. A recorded process group that still has a live member keeps its route and shares even after it closes its port; prune records the member that survived and stops it on a retry with portless prune --force. A group prune cannot verify is kept and reported, never signaled. A port holder that cannot be proven part of the recorded group is kept and reported, never killed. Prune and clean stop recorded ngrok and cloudflared tunnels only when their executable names match, including on Windows.
Run portless doctor first when a URL does not load. It checks the proxy, routes, DNS, and CA trust without changing anything, and prints suggested fixes. Use portless doctor --json to print the report as JSON.
portless clean previews its cleanup and asks for confirmation. Use portless clean --yes (or -y) in CI or without a terminal. On macOS and Linux, a failed CA, state-file, or hosts step is retried with sudo for the same allowlisted targets. If the proxy cannot be confirmed stopped, its PID, port, runtime marker files, and CA files are kept and the CA stays trusted. Service, CA, state-file, and hosts cleanup failures produce a nonzero exit code.
On macOS and Linux, portless trust, portless proxy stop, portless prune, portless hosts sync, portless service install, and portless clean act on a state directory only when no other user can change it. The directory and each of its parent directories must be owned by you or root and must not be writable by group or others. A parent with the sticky bit set, such as /tmp, is allowed. A symlink on the path counts only when you or root own it and it sits in a directory that passes the same check. portless trust, portless proxy stop, portless prune, portless hosts sync, and portless service install exit with the reason when the directory fails this check. Nothing is signaled and the hosts file is not changed. The proxy does not start from such a directory, and commands that register a route, such as portless run and portless alias, exit with the same reason. A proxy that is already running keeps the routes it has loaded and stops reloading them. portless never changes the permissions or owner of a state directory that fails it. Run chmod go-w <dir> on the directory it names, or point PORTLESS_STATE_DIR at a directory only you can write to. portless clean leaves such a directory alone, prints the reason, and exits nonzero. It skips a /tmp/portless directory that fails the check without an error. portless proxy stop and portless clean signal the recorded proxy PID only when nothing shows it is a different process from the one answering on the proxy port.
portless runs on macOS, Linux, and Windows with Node.js 24 or later. --tailscale and --funnel need the Tailscale CLI, --ngrok needs the ngrok CLI, and --cloudflare needs cloudflared.
This repo is a pnpm workspace with Turborepo. The published package is packages/portless/, and the docs site is apps/docs/. Use Node.js 24 or later and pnpm 11:
pnpm install
pnpm build
pnpm test
pnpm lint
pnpm type-check
pnpm formatAGENTS.md lists the files to update with each change and the release process.
- portless.sh: getting started, commands, HTTPS, and configuration
- Why portless: the problems named URLs solve
- Changelog
Apache-2.0