Docs/Interfaces
Interfaces

Cursor and Continue.dev against your own DGX Spark endpoint

By Samuel Seidel · Updated September 9, 2026 · 5 min read

This page gets Cursor's chat and Continue.dev's IDE panel answering from a model on your own DGX Spark instead of their default cloud backends. You set a base URL, a key and a model name in each editor's settings. For terminal and agent tools (Cline, aider), see the coding agents guide.

You need:

On this page
  1. Start with a running endpoint
  2. Cursor
  3. Continue.dev
  4. Other IDE assistants
  5. Rolling this out across a team
  6. What actually breaks

Start with a running endpoint

Both editors need an OpenAI-compatible /v1 endpoint reachable from your laptop.

  1. Pick the endpoint. With a console model preset, copy the HTTPS endpoint from the instance page (it looks like https://app-<instance-id>.gpuwerk.com) and add /v1; requests need your inference-scope API key. With your own vLLM server on a base image, <spark-host> in the samples is your instance's hostname, <name>.gpuwerk.com.
  2. Protect your own engine. The instance has its own public IPv4 address, assigned by GPUwerk, so a server on 0.0.0.0:8000 is open to the internet. Start vLLM with --api-key, or bind it to 127.0.0.1 and use an SSH tunnel, which needs your own SSH key.
  3. Confirm it answers before you touch either editor:
    curl http://<spark-host>:8000/v1/models
    For a preset, call https://app-<instance-id>.gpuwerk.com/v1/models with -H "Authorization: Bearer $GPUWERK_API_KEY". You should see JSON listing the model ID, for example qwen3-coder-30b.

Cursor

  1. Open Settings, Models in Cursor.
  2. Add a custom OpenAI API endpoint and fill in the base URL, key and model. For a preset, use its HTTPS endpoint plus /v1, your inference-scope key and qwen3-coder-30b:
Base URL: http://<spark-host>:8000/v1
API Key: not-needed-unless-you-put-a-gateway-in-front
Model: Qwen/Qwen3.8-27B-FP8
  1. Select the custom model in a chat and send a test prompt. You should get an answer from your instance.

A custom endpoint usually covers Cursor's chat and edit requests. Its tab completion uses a separate model slot that you may not be able to redirect, and this changes between releases, so check Cursor's current model settings. The model name must match /v1/models exactly; a mismatch fails with an error that looks like an auth problem.

Continue.dev

Continue uses the same config.yaml entry in its VS Code and JetBrains sidebars as in the coding agents guide. Follow those steps, with apiBase pointing at your Spark or your LiteLLM gateway. Sidebar chat, inline edit and autocomplete then all use the model that entry names.

Other IDE assistants

If an assistant's settings have an "API base URL" or "custom provider" field next to the API key, the same pattern works: point it at your Spark's /v1 URL, or at a LiteLLM gateway for per-user keys and usage tracking. Support and menu locations change between releases, so check the tool's current documentation.

JetBrains AI Assistant and several VS Code extensions follow the same shape. Check the scope case by case: some plugins send only their chat panel to a custom endpoint and keep other features, such as commit message generation, on their own built-in model.

Rolling this out across a team

One developer can use the Spark's URL directly. Once several people share the box, put LiteLLM in front. Each developer gets their own virtual key, you can rate-limit a runaway agent loop before it slows everyone else down, and revoking one person's access leaves everyone else's settings alone. In each editor, the base URL changes to the gateway's address and the model name becomes the alias you set in LiteLLM's config.yaml.

What actually breaks

See alsoCoding agents against your own endpoint See alsoPut a gateway in front for keys and budgets
First top-up: pay $20, get $30 in credit

Point your editor at a dedicated Spark.

Deploy a dedicated DGX Spark in Europe, North America or East Asia and point your IDE at it in the time it takes to read this page.

Create account