ApexSpriteAI supports two deployment modes depending on where your GPU server lives. In local-only mode, everything runs on a single machine and no special networking is required. In remote GPU mode, Claude Code on your Mac communicates with an LM Studio server running on a separate machine over Tailscale, a secure peer-to-peer VPN. This page walks you through both modes and shows you how to verify that each layer of the network is working correctly before you run your first query.Documentation Index
Fetch the complete documentation index at: https://docs-apexspriteai.reliatrack.org/llms.txt
Use this file to discover all available pages before exploring further.
Deployment modes
Local-only mode
When LM Studio and Claude Code run on the same machine, all traffic stays on localhost. No VPN or firewall changes are needed. Claude Code sends requests to:ANTHROPIC_BASE_URL to this address in your ~/.claude/config.json and you are done. See Environment setup for the full config file example.
Remote GPU over Tailscale
When your LM Studio backend runs on a separate machine — such as a dedicated GPU server — you route API traffic through Tailscale so that the server is never exposed to the public internet. Tailscale assigns each device a stable private IP in the100.x.x.x range. Your Mac connects to the Spark server using that address — for example, 100.82.56.40 — as if both machines were on the same LAN.
Claude Code sends requests to:
Replace
100.82.56.40 with your own Tailscale IP. Run tailscale ip -4 on your GPU server to find it.Tailscale setup
Install Tailscale on both machines
Download and install the Tailscale client on your Mac and on the GPU server. Sign in with the same Tailscale account on both devices so they join the same tailnet.
Confirm both devices appear in the admin console
Open https://login.tailscale.com/admin/machines and verify that both your Mac and the GPU server show a green connected status.
Note your GPU server's Tailscale IP
On the GPU server, run:The output is the IP address you use in
ANTHROPIC_BASE_URL.Bind LM Studio to all interfaces
In LM Studio on the GPU server, open Local Server settings and set the bind address to
0.0.0.0. This tells LM Studio to accept connections on every network interface, including the Tailscale interface. If LM Studio binds only to 127.0.0.1, remote requests are silently dropped even when Tailscale is working correctly.Verifying connectivity
Once Tailscale is running and LM Studio is bound to0.0.0.0, confirm the port is reachable before configuring Claude Code.
Test port reachability with netcat
Run this from your Mac, substituting your Tailscale IP:Check active routes
100.x.x.x range is routed through the Tailscale interface (utun on macOS).
Inspect firewall rules
Check that no packet filter rules are blocking port 1234:DNS troubleshooting
If you use a hostname instead of a raw IP address to reach the Spark server, stale DNS entries can cause connection failures after a network change. Flush the macOS DNS cache with:nc connectivity test.
LM Studio bind address
LM Studio defaults to binding on127.0.0.1, which means it only accepts connections from the same machine. For any remote access — whether over Tailscale or a local LAN — you must change this to 0.0.0.0.
| Bind address | Accepts local traffic | Accepts remote traffic |
|---|---|---|
127.0.0.1 | Yes | No |
0.0.0.0 | Yes | Yes |