[willeastcott]

What's Changed

• The MCP server popover now accepts only a port from 1 to 65535, and checks it as you type. While the port is invalid, the field shows its error outline, a red "Enter a port from 1 to 65535" hint appears, and Connect is disabled, so a bad port is never stored or tried. An empty field counts as invalid too; previously it silently connected to 52000. The field still starts filled with 52000. Validation listens to the DOM input event rather than PCUI's keyChange (keyup), so paste, autofill and mobile keyboards are covered too. Cancel and Disconnect stay enabled whatever the field holds.
• The error outline stays visible while the field is focused, in both placements: the toolbar's red ring over PCUI's orange focus ring, and the projects page's red border over its orange focus border.
• A bad port stored by an earlier version falls back to the default when the popover auto-reconnects, so editors already caught by this recover on their next load.
• MCPConnection.connect() refuses an invalid port with a logged [MCP] error instead of throwing, whoever calls mcp:connect.
• New parsePort() helper in src/editor/mcp/port.ts, with tests.

Why: new WebSocket() throws a SyntaxError for a port outside 1–65535. The popover read its field with parseInt(value) || 52000, which accepts any integer, so a typo such as 520000 threw out of the Connect click handler. The error landed in error reporting, and the status was left on "Connecting" with no socket behind it. The popover had already stored editor:mcp:connected = true and the bad port before connecting, so the auto-reconnect retried it, and threw again, on every reload until the user noticed.

Testing:

• npm test: the new parsePort tests pass, including 520000, 400000, 65536, 0, -1, empty, 52000abc, 5e4 and 52000.5.
• eslint and stylelint report no errors in the changed files.
• In Chrome, on a standalone page running the real popover.ts, connection.ts and port.ts against the compiled editor.scss, with a stub editor global:
  • Typing 520000 into the toolbar popover turns on the error ring (red even while focused), shows the red hint and disables CONNECT. Clicking CONNECT then stores nothing and doesn't connect.
  • Correcting it to 52001 removes the error and re-enables CONNECT. (Clearing the field now disables CONNECT; that change is covered by the parsePort('') test, not re-run in the browser.)
  • Escape revalidates after PCUI restores the pre-edit value, in both directions. From 52000, appending 0 makes it invalid, and Escape brings back 52000 with the error cleared and CONNECT enabled; before the fix the error and the disabled CONNECT stuck. From a committed 65536, deleting a digit makes it valid (6553), and Escape brings back 65536 with the error back on.
  • In the projects-page popover, 400000 gives the red border, the hint and a disabled Connect.
  • Reloading with editor:mcp:connected = true and editor:mcp:port = 520000 already stored shows 52000 in the field and auto-connects to ws://127.0.0.1:52000.
• Not exercised inside a full editor session.

Checks

• I confirm I have read the contributing guidelines

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
editor	Ready	Preview	Oct 24, 2026 1:43pm UTC