Vortex

Release notes

MCP that runs on the SSH host, and AI review that actually starts

0.2.0-beta.61 · September 19, 2026

MCP now resolves on the machine that owns the workspace. Open a remote (SSH) workspace and the host keeps its own ~/.vortex/mcp.json, spawns stdio servers there, and sends HTTP requests from its own network — so a server wrapping a database on the host finally works. Settings → Integrations follows the workspace instead of refusing every server with "Remote MCP execution is not available yet". Run AI Review now gets the cloud key, keeps running if you switch tabs, and shows Fetching / Reviewing progress you can Cancel.

Fixed

  • "Set up <server> MCP" in a remote workspace wrote a plan instead of configuring anything. The two MCP config tools now work against the host.
  • The Connect button did nothing in a remote workspace. It read the server's URL and credential key from your Mac's config. Both now come from the host; the browser flow and the token still stay on your Mac.
  • A connected server could still fail with 401 because the token was stored under one key and read under another. Both sides now derive the key from one shared rule.
  • In a remote workspace, the "Global defaults" tab listed your Mac's servers while the caption said it was showing the host's.
  • "Test connection" failed on a server you had just signed in to. The token is now sent for the test too.
  • An mcp_* tool call in a remote workspace silently executed on your Mac. It now routes to the host, or fails loudly naming the host.
  • Settings → Integrations marked every server "Runs locally only" whenever the workspace was remote, leaving the panel unusable there.
  • A host running an older vortex-server now says so explicitly and tells you to redeploy, instead of quietly running the call on your Mac.
  • Run AI Review invoked with a blank key because the editor pane never forwarded the cloud model, so every click failed with "Code review needs a cloud API key."
  • Switching tabs or workspaces mid-review made it look idle (and offered a second concurrent run). Progress, Cancel, and the completion toast now outlive the tab.

New

  • MCP servers run on the remote host: its config, its stdio processes, its network. Per-workspace overrides work there too.
  • configure_mcp_server and inspect_mcp_servers read and write the host's config in a remote workspace, and the approval card names the machine it is writing to.
  • The Integrations panel names the exact file it edits (<host>:~/.vortex/mcp.json) and says where each server runs.
  • OAuth sign-in still happens on your Mac, and the token is sent per call — no OAuth token is ever written to the host.
  • Docs: an "In a remote workspace" section in MCP integrations, including the reverse-tunnel recipe for a server that must stay on your Mac.
  • AI review shows "Fetching the diff…" then "Reviewing the diff…" with an elapsed clock, and you can Cancel. A completion toast can take you back to the PR tab.

All Vortex releases