Point Cline and your browser at a machine running vLLM + OpenClaw — without knowing anything about either.
Companion repos: dgx-spark-wizard provisions the server itself; this repo is the client side: your editor and your browser.
powershell -ExecutionPolicy Bypass -File SparkConnect.ps1
Four buttons, run in order:
| Button | What it does |
|---|---|
| 1. Pair SSH | Generates a key and installs it on the server. You type the server password exactly once, ever. |
| 2. Check server | Reads http://server:port/v1/models — learns the model id and its real context window. |
| 3. Configure Cline | Backs up and rewrites your local Cline config (~/.cline/data/settings/models.json + globalState.json) to match the server exactly. |
| 4. Dashboard link | Fetches a working OpenClaw dashboard URL (gateway port + auth token discovered on the server at runtime) and puts it on your clipboard. |
No passwords are stored anywhere; SSH uses a dedicated key at
~/.ssh/id_ed25519_sparkconnect.
- PROMPT.md — one safe message you paste into the Spark's own OpenClaw chat. The agent verifies the model server is up, registers it, validates the config, and prints the four values you need. It cannot install, restart, or delete anything.
- docs/Connect-Cline-or-opencode-to-your-Spark.pdf — the plain-language guide built around that prompt: Part 1 gets the four values, Part 2 types them into Cline or opencode. Written for non-coders.
Everything the GUI does, as copy-paste steps with explanations: docs/manual-setup.md.
- Dashboard loads, never replies → your origin isn't allow-listed on the
gateway. On the server:
bash /tmp/openclaw-url.sh --fix-origin, thenopenclaw gateway restart. - Dashboard stuck on a pairing screen → device approval. On the server:
openclaw devices list, thenopenclaw devices approve <id>. - Cline errors on every single request → reasoning effort is set to
lowand the checkpoint rejects it. Set it tononeorhigh. - Long tasks die halfway → that's the server-side harness, not the client. See fix-openclaw.
MIT.