local.vibe is a macOS Go binary that assigns .vibe hostnames to local services, eliminating port-number juggling across dev projects.
Key Takeaways
Drop a vibe.json with a name and command into any project; vibe start proxies it to https://name.vibe with auto-assigned $PORT.
A local CA cert is trusted in Keychain so HTTPS works immediately; no external accounts or telemetry.
Dashboard at https://local.vibe shows all running services with start/stop controls, emoji icons, grid/list views, and bookmarks.
Supports non-localhost targets: tailscale.vibe and hass.vibe can redirect to Tailscale machines or Home Assistant.
curl http://localhost:7999/setup.md returns a setup guide readable by Claude Code or Cursor, letting agents register routes and control apps via HTTP API.
Hacker News Comment Review
Commenters pointed to at least two prior-art tools (outport.dev for worktree port orchestration, sonar on GitHub) suggesting this space has multiple active solutions.
One commenter noted the core abstraction is simply “metadata + a $PORT-aware command = handled”, which is accurate but raises the question of scope: what happens when you need two instances of the same service.
Skepticism surfaced about novelty: /etc/services already maps names to ports, implying the gap local.vibe fills is UX and automation glue rather than a missing protocol primitive.
Notable Comments
@zdw: “It’s like someone should make a file… maybe in /etc… and put short names for services in it” – flags that named service resolution is not new, questioning the problem framing.
@yunruse: Raises the edge case of running the same service twice and notes ports still lack any textual resolver at the protocol level.
