Yaak Logo
Yaak
Feedback/MCP server doesn't start after relaunch: orphaned plugin runtime keeps port 64343

MCP server doesn't start after relaunch: orphaned plugin runtime keeps port 64343

Purushoth DL·Nov 17, 2026 12:43:05 UTC·YK-1181
Pending ReleaseBug

After quitting Yaak, the plugin runtime (yaaknode .../plugin-runtime/index.cjs) is sometimes left running with its parent reassigned to launchd (PID 1). It keeps the MCP server’s port (64343) bound. The next launch then fails with:

Creating MCP server on port 64343 Uncaught Exception: Error: listen EADDRINUSE: address already in use 127.0.0.1:64343

so the “MCP Server running” notification never appears, and MCP clients hang against the old process. For the quit that leaves the orphan, the log has no “Exiting plugin runtime due to app exit” lines.

Workaround: kill the stale yaaknode process, then relaunch.

Proposed fix: make the runtime exit when its websocket to the app closes (it never reconnects, so it can’t do anything after that). I tried this once on my install: before the change the orphan survived a quit; after it, nothing was left running and the port was free.

PR: https://github.com/mountain-loop/yaak/pull/845

macOS2026.9.0

Comments (0)

Sign in to leave a comment.

Type to search feedback...