portless

Configure a global CLI to expose local dev servers under stable .localhost URLs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/andreasasprou/polaris --skill portless-andreasasprou
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: portless
Source: https://github.com/andreasasprou/polaris/tree/main/.agents/skills/portless
Command: npx skills add https://github.com/andreasasprou/polaris --skill portless-andreasasprou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Port conflicts and flaky local URLs slow down development. portless provides a global CLI tool to replace hard-coded localhost ports with stable, named .localhost URLs for local development, simplifying multi-project work and proxy setups.

Core Features & Use Cases

  • Global CLI tool that assigns portless routes to local dev servers and proxies, enabling consistent URLs like http://myapp.localhost.
  • Automatically starts the proxy when you run an app and supports explicit portless proxy startup for manual control.
  • Works across worktrees and multi-app setups, keeping names and subdomains aligned with project structure.

Quick Start

Install portless globally and run portless proxy start, then run your app with portless run to obtain a .localhost URL.

Frequently Asked Questions about portless

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get stable localhost URLs for local dev servers instead of hard-coded ports?

Use a global CLI proxy to assign named .localhost routes to local dev servers, replacing hard-coded ports with predictable URLs like http://myapp.localhost for conflict-free development.

What is the best way to manage port conflicts in a multi-project monorepo?

Managing port conflicts in a multi-project monorepo is done by assigning stable .localhost URLs to each app. This keeps names and subdomains aligned with the project structure across worktrees without port collisions.

How does a local dev proxy work with worktrees and multi-app setups?

A local dev proxy works by routing traffic from named .localhost URLs to your local dev servers. It automatically starts the proxy when you run an app and keeps names aligned with project structure across worktrees.

How do I start a local dev proxy and run my app with a named URL?

To start a local dev proxy, install the CLI globally and run the proxy start command. Then execute your app using the run command to obtain a stable .localhost URL for local development.

Do I need to manually start the proxy every time I run an app?

You do not need to manually start the proxy every time. The proxy automatically starts when you run an app, but you can also use an explicit proxy startup command for manual control over your local dev environment.