portless

Map dev servers to stable .localhost URLs with TLS and proxy rules.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Portless eliminates the friction of port conflicts by mapping dev servers to stable, named .localhost URLs, reducing cross-project contention and misrouting during local development.

Core Features & Use Cases

  • Zero-config proxying: routes a package's dev server to https://<name>.localhost automatically.
  • TLS and LAN support: creates a local CA, offers TLS, and resolves .local domains across a LAN or workgroup.
  • Multi-app and worktree friendly: detects git worktrees and assigns unique URLs per branch or package, ideal for monorepos and complex setups.

Quick Start

Run portless in your project to start the proxy and open a stable .localhost URL for your app.

Frequently Asked Questions about portless

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

FAQPage Schema
How do I prevent port conflicts when running multiple local dev servers?

To prevent port conflicts during local development, you can map dev servers to stable named .localhost URLs. This eliminates cross-project contention and misrouting by routing each package to a unique address automatically.

How do I set up local TLS certificates for my localhost development environment?

Setting up local TLS for localhost development involves auto-generating a local CA, keys, and certificates. This creates trusted HTTPS endpoints for your named local domains without manual certificate configuration.

Can I route multiple git worktrees to unique local URLs in a monorepo?

Yes, managing git worktrees in a monorepo supports detecting branches and assigning unique .localhost URLs per worktree or package. This multi-app routing is ideal for complex local development setups.

Does local development proxying work across a LAN or with custom TLDs?

Local development proxying works across a LAN by resolving .local domains over a workgroup, and supports custom TLDs. You can configure host mappings and routing rules through the CLI.

What is the best way to handle local proxy routing for tailscale or funnel setups?

Handling local proxy routing for tailscale or funnel setups is done by configuring host mappings and proxy rules through the CLI. It supports these options alongside TLS and custom TLDs to expose local development servers securely.