Run DeepSeek V4.1 Flash Uncensored with Strata

Choose the matching API address

127.0.0.1 means the computer running the client. A remote RunPod server’s loopback address cannot be used directly from a laptop. Choose one of these routes; OpenAI-compatible clients use a Base URL ending in /v1. Only a client requesting a full Chat Completions URL needs /chat/completions appended.

Local model and tool on the same computer

Leave the launch on --access local. Tools on the same Windows PC, Mac or Linux machine use http://127.0.0.1:8080/v1. The command below is for Bash on Mac/Linux; on Windows use the separate PowerShell check and change its port from 18080 to 8080.

curl -fsS http://127.0.0.1:8080/v1/models

Tool on another computer: tunnel to your GPU machine

On the computer running the tool, use an existing SSH login to the Windows, Mac or Linux model server. The server must already have SSH access enabled and be reachable. Replace model-user@model-server with that login, retaining any required SSH port/key options. Keep the SSH window open and set the tool Base URL to http://127.0.0.1:18080/v1. Strata remains on --access local. On a Mac this uses an existing Remote Login connection; on Windows it needs an existing OpenSSH Server setup.

ssh -N -L 18080:127.0.0.1:8080 model-user@model-server

Cloud GPU: open a full SSH tunnel from your computer

In RunPod Connect, copy the full SSH-over-TCP/public-IP command with the Pod’s actual port, host and identity-file options. On your own Windows PowerShell, macOS or Linux terminal, add -N -L 18080:127.0.0.1:8080 to that command, then run it. Keep the tunnel open. Use http://127.0.0.1:18080/v1 in your tool. The basic SSH gateway and Jupyter browser URL are not substitutes for this route.

• RunPod full SSH ↗

Test a tunneled connection from macOS or Linux

Run this on the computer running the tool, while the SSH tunnel is open. Expect JSON with the served model ID. If Strata requires a key, include an Authorization: Bearer header containing that key. A connection failure here should be fixed before changing the tool settings.

curl -fsS http://127.0.0.1:18080/v1/models

Test a tunneled connection from Windows PowerShell

Run this in PowerShell on the computer running the tool, while the SSH window remains open. Expect the model list. For a same-machine server, change 18080 to 8080. Authentication requires the configured Strata key if enabled.

Invoke-RestMethod http://127.0.0.1:18080/v1/models | ConvertTo-Json -Depth 6

Find the configured Strata key

Run this privately in PowerShell on the Windows server or Terminal on the Mac/Linux server when a key is configured. Enter that Strata key into the tool’s API Key field. A RunPod account key or Hugging Face token is a different credential and will not authenticate this model server. Do not publish the server key.

strata launch --show-key

• Strata access and connection settings ↗

Enter the provider settings in Cline

Install VS Code and the official Cline extension on the computer where you want files edited. Open Cline Settings, select OpenAI Compatible and enter the matching address above. Keep the server and any tunnel running. These are settings to enter in the app, not terminal commands.

API provider

OpenAI Compatible (Chat Completions)

Base URL

http://127.0.0.1:8080/v1 for same machine; http://127.0.0.1:18080/v1 through SSH; authenticated HTTPS Base URL for a hosted client

API key

Your configured Strata key; a non-secret placeholder only for an unkeyed private loopback route if required by Cline

Model ID

Copy the exact id from /v1/models on the reachable server

Context window / max output tokens

8,192 context to match this server; start with 1,024 max output tokens within that budget

Images / reasoning / approvals

Images off; reasoning none/low for the first check if available; file and terminal approvals manual

• Official Cline extension ↗
• Cline provider configuration ↗

Ask the tool to make a small, reviewable change

Open an empty disposable folder in VS Code. Ask Cline: “Create hello.txt containing Hello from Strata. Ask before editing files or running commands. After saving, read it back and report its contents.” Approve only the intended file operation. Confirm the file exists in that folder and that Cline actually invoked its tools. This example checks the client’s tool behavior; it does not claim AtomicChat has already passed it.

Check another supported app with Strata’s connector

On the server, this command prints the OpenCode connection configuration for the running model. Use the printed model/key/context settings in the client. If the client is elsewhere, replace a server-local URL with your tunnel or HTTPS address. This prints configuration; it does not install OpenCode or prove tool calls work. Other adapters are listed by strata connect.

strata connect opencode

• Strata tool adapters ↗

Run the connector’s prompt and tool-call check

With the model serving, this separate command sends a prompt and tool call in OpenCode’s format. Inspect both outcomes; a failed check is a real compatibility issue. The check runs from the server and does not verify a remote client’s SSH tunnel or HTTPS path. This 8K DeepSeek setup can be too small for some agents; do not assume 32K connector examples or Hermes’ larger-context defaults fit it.

strata connect opencode --check --output json

For scripts: send one API request

In a Bash terminal on the server, replace copy-model-id-here with the exact ID obtained above, then run this single request. Expect generated text in choices[0].message.content. For a tunneled client replace 8080 with 18080. For a keyed endpoint, also add -H "Authorization: Bearer YOUR_STRATA_KEY" using your actual key privately. PowerShell users should use their tool’s provider UI or an equivalent Invoke-RestMethod request.

curl --fail-with-body http://127.0.0.1:8080/v1/chat/completions -H 'Content-Type: application/json' --data '{"model":"copy-model-id-here","messages":[{"role":"user","content":"Reply with one short sentence."}],"max_tokens":128,"reasoning_effort":"none","stream":false}'

Already running? Keep the existing SSH route

Use the SSH-over-TCP instructions above without restarting Strata. An independently authenticated gateway can forward an exposed HTTP port to the loopback listener if one is already configured. A direct RunPod HTTP proxy cannot reach a loopback-only listener on its own.

For a new Pod: expose the HTTP port first

In the RunPod template, expose the HTTP service port before deploying. Use 8080 only when it is exposed and available; if the template exposes 6080, use 6080 only if another service does not occupy it. The Strata listen port, exposed service port and HTTPS URL port must agree. Editing an existing Pod can erase container-disk files: preserve them first.

• RunPod HTTP service ports ↗

Set the actual exposed service port

Run this on the Pod before launch, after checking the template and port availability. Replace 8080 with the exposed free service port, such as 6080, when needed. Keep STRATA_WORK set to the verified model-data folder from the selected RunPod tab.

export STRATA_PORT=8080

Initial HTTPS launch: network access and a new key

Use this instead of the local launch on a new Pod. It preserves the selected AtomicChat model path, data directory and inference settings, and changes access, port and key options. There is no need to start local first and force a second restart. Keep public endpoint authentication enabled.

strata launch  --model-path "$STRATA_WORK/ds-unc/DeepSeek-V4.1-Flash-1017-GSQ-RCO-IQ2_XXS-00001-of-00004.gguf"  --data-dir "$STRATA_WORK/strata-atomic"  --context 8192 --vision off --speed full --access lan --port "$STRATA_PORT" --new-key --yes --no-tui

Read the Strata key privately

Run this on the Pod after startup and enter that key in your client. If an existing gateway authenticates requests, use its configured key instead. Neither is your RunPod account API key.

strata launch --show-key

Check the HTTPS network route

Replace POD_ID and PORT with the actual Pod ID and exposed service port. A 401 means the network route is reachable and authentication is required. A 502 generally means RunPod cannot reach a listener on that port. An authenticated request should return JSON listing the served model ID.

curl -i https://POD_ID-PORT.proxy.runpod.net/v1/models

Authenticate your tool and test a short generation

Set the tool’s Base URL to https://POD_ID-PORT.proxy.runpod.net/v1 and enter the actual Strata/gateway key locally. Discover the model ID, then test a short /v1/chat/completions request before a large agent prompt. RunPod documents an approximately 100-second HTTP proxy timeout: slow prompts may exceed it, so a direct SSH tunnel is usually better for long generations. Avoid exposing an unauthenticated public Strata endpoint.

Strata stock-model throughput

Strata’s README attributes these stock ISTA 2.00 bpw DeepSeek results to Strata 0.2.5: RTX 5070 12 GB + 64 GB RAM: 4–6 output tokens/s; RTX 3060 12 GB + 46 GB RAM: 9–11; Radeon AI PRO R9700 + 251 GB RAM: 21–25. CPU, NVMe, prompt, context, drafting and expert settings vary. These do not predict uncensored RTX 4090 performance.

• Published Strata results ↗

AtomicChat quality scores

AtomicChat reports IQ2_XXS at reasoning effort 50 on Strata: GPQA-Diamond 83.3% for stock and edited models; AIME25 76.7% stock and 80.0% edited. AIME25 has only 30 questions; the difference is within noise. These author-reported quality scores are not throughput measurements or evidence of a general improvement.

• AtomicChat evaluation ↗

Measure your own setup

Record model repository revisions, Strata version, exact GPU/CPU, allocated RAM, NVMe, context, expert/drafting settings, prompt/output lengths, cold first-token wait, warm output tokens/s, total time and peak memory. Repeat the same prompt three times after warming. No uncensored-model 4090 throughput or successful Pod run has been independently established here. A successful /v1/models response proves the API is reachable, not that inference or tool calling works. Test a short /v1/chat/completions request first. Large coding-agent system prompts can consume most of an 8K context window. Published throughput for other models or hardware is not a guaranteed benchmark for this community-modified model.

Record the Strata version

Run this on the model server and include the version with your timing results.

strata --version

Record the GPU and driver

Use this on a supported NVIDIA Windows/Linux host. On a Mac record the Apple chip and unified memory from About This Mac instead; nvidia-smi does not apply to Metal.

nvidia-smi

Record system RAM

Use this command on Linux. On a Mac repeat sysctl -n hw.memsize; on Windows repeat the PowerShell memory check from setup. Do not use free on macOS or Windows.

free -h

Record available model storage

Use Bash on Mac/Linux with STRATA_WORK set. On Windows, repeat the PowerShell free-drive-space check from setup.

df -h "$STRATA_WORK"

Stop the model server

Run this on the machine serving the model when no client needs it. This stops inference; it keeps the downloaded files for reuse.

strata launch --stop

Restart the same model later

In a new shell, repeat your selected route’s working-folder setting first: PowerShell on Windows or Bash on Mac/Linux/RunPod. Rerun that route’s Launch the model command and check status/health. Reopen any SSH tunnel. For the public cloud HTTPS route, use its keyed launch instead.