Repository navigation
v5.0.1
PortPilot 5.0.1: the window opens, and PortPilot never stops itself
A fix release for 5.0.0. If 5.0.0 started and showed nothing, this is the build to install.
Fixed
- The installer opens a window again. 5.0.0 was packaged without the interface bundle, so the app threw at launch and showed nothing. The release build now builds it, and the packaged check fails without it.
- PortPilot no longer mistakes itself for an app. Its own MCP server's command line contains "portpilot", so the "PortPilot" app entry showed as running on 8788: Open opened the MCP endpoint and Stop killed the tools under every Claude session. Own servers are skipped in the app, the MCP server and the VS Code extension, and an app's folder matches only at a path boundary, so a parent app no longer claims its worktree's server.
- PortPilot never kills itself. Stop, Kill on the Ports table, Free port in the palette and the MCP
kill_portandstop_apptools refuse a pid PortPilot runs in. - The MCP server comes back. If the shared MCP server exits, PortPilot restarts it with backoff and raises a notification after five quick deaths in a row.
- Folder buttons open the folder. They opened nothing behind a success toast.
- An app's name is matched word by word. "AzurePrep" now matches a server whose command names
azure; a sibling worktree folder no longer matches the parent on name alone. - Open on a stopped app no longer opens a dead URL. The drawer and the palette open an app only when it is running.
- A stale
agent.jsonis dropped. A force-terminated web agent left its record behind; readers now check the pid and delete the file when it is dead.
VS Code extension 4.2.5
- Kill on a port held by two processes (an IPv4 and an IPv6 listener) now frees it: every holder is killed.
- The scanner no longer mistakes PortPilot's own server for an app.
Full list: CHANGELOG.md.