Portless v0.11 adds myapp.localhost and parallel worktrees

• ctatedev's launch post says Portless v0.11 replaces the usual :3000 shuffle with stable names like myapp.localhost.
• According to the launch post, the new naming scheme is meant to let agents run dev servers from parallel worktrees without colliding on ports.
• ctatedev's terminal screenshot shows one command generating multiple local hostnames, while the linked GitHub repo frames the tool as zero-config.
• Installation now splits by audience: ctatedev's follow-up gives npm install -g portless for humans and npx skills add vercel-labs/portless for agents.

You can inspect the GitHub repo, see ctatedev's launch demo, and the whole pitch is unusually narrow: fix the local dev naming mess so multi-agent worktrees stop stepping on each other.

Portless is targeting a very specific annoyance, the habit of every local app fighting for :3000. In ctatedev's launch post, the headline feature is stable names like myapp.localhost, not another proxy layer with setup steps.

The screenshot in that post maps separate services to fixed hostnames, including admin.acme.localhost, docs.acme.localhost, and acme.localhost. That makes the tool feel closer to naming infrastructure than port forwarding.

The more interesting claim in ctatedev's launch post is that agents can use worktrees in parallel without stepping on each other. That ties the release to the current coding-agent workflow, where several branches may each need their own live dev server.

The post does not describe deeper routing internals, but it does make the intended use case explicit: one command, no code changes, and separate local identities for concurrent worktrees.

Portless now has two entry points. In the follow-up, the commands are split cleanly:

• Humans: npm install -g portless
• Agents: npx skills add vercel-labs/portless

That second path matters because it turns Portless into a tool an agent can add to its own environment, not just a CLI a developer runs manually. Addy Osmani's reply is only a brief reaction, but it shows the release already landing with at least some developer audience outside the original thread.