Skip to content

XM-Serve Connect

XM-Serve Connect is a beta connector that puts XM-Serve behind a VS Code extension: paste an API key once, pick an agent and model, and it opens a Claude Code or Codex (beta) terminal session wired up to XM-Serve. No copying environment variables into terminal tabs by hand.

What You'll Need

  • VS Code 1.95.0 or later, on macOS or Linux.
  • Claude Code or Codex installed and on your PATH.
  • An active XM-Serve API key from the XM-Serve Console.
  • A project folder open in VS Code.

Step 1: Install the Extension

  1. On the Console's Coding Agents page, select a model and tier, then choose VS Code. The page offers Download for VS Code; choose your coding agent inside the extension.
  2. In VS Code, open the Extensions view.
  3. Select the ... menu, then Install from VSIX....
  4. Select the downloaded netpreme-connect-vscode.vsix and reload VS Code if prompted.

Step 2: Connect to XM-Serve

  1. Open the XM-Serve icon in the VS Code Activity Bar.
  2. Select Connect to XM-Serve, then open the Console to create a key or choose I Have an API Key.
  3. Paste your XM-Serve API key into the protected input.
  4. Choose Claude Code or Codex, follow any missing-agent setup instructions, and select a model.
  5. XM-Serve Connect validates the route and opens a new terminal session for the selected agent in the current workspace.

That new session never replaces or migrates an existing conversation.

The API key is stored only in VS Code Secret Storage on the local device. It's never written to ~/.claude/settings.json, Codex configuration files, a shell profile, the workspace, or source control. The extension leaves the workspace's own setup untouched: same files, Git state, and project instructions it already had open.

Step 3: Everyday Use

Once connected, the XM-Serve panel adds a few more entries:

Command What it does
Start Default Session Open a new session with the saved agent and model.
Switch Agent or Model Open a separate session with temporary settings, preserving the defaults.
Manage Connection Change defaults, replace the key, check prerequisites, open the Console, or disconnect.
Send Feedback Open the Console and copy a safe diagnostic tag for a bug or feedback report.

In Manage Connection, Make Terminal + Start Default Session makes the Terminal + button launch your saved XM-Serve session. Turn Off Terminal + XM-Serve Sessions restores the previous terminal profile. Disconnecting also restores it unless you changed the profile yourself.

Run Check Connection from Manage Connection any time something feels off. A missing agent install, an expired key, or an unavailable model each show up as their own message with a next step, not a generic failure.

Disconnect & Remove Key only removes the saved key for future sessions. It does not close sessions that are already open, and does not touch existing conversation history, project files, or your normal agent settings. To stop a session that's already running, close its terminal. To invalidate the key immediately instead of just removing it locally, revoke it in the Console.

Feedback

Select Send Feedback to open the XM-Serve Console and copy a diagnostic tag containing the extension version, selected model, and Gateway status. Paste it into the Console Feedback or Bug sidebar along with a description. The tag never includes an API key, prompt, source code, or workspace path.

More coding agents, coming next XM-Serve Connect currently supports Claude Code and Codex (beta) in VS Code. Tell us which agent you use most, such as Cursor, Windsurf, Cline, or another tool. We are actively working to bring support for additional agents.

Request an agent or share feedback

FAQ

Does this replace the manual environment-variable setup on the Harness Integration page? No. [Harness Integration](coding-agents.md) still applies for terminal workflows and other agents such as pi and Hermes. XM-Serve Connect targets Claude Code and Codex inside VS Code.

See Also