Analysis updated 2026-05-18
Fix the 'unsupported parameter extra_body' error when using ZCode with NVIDIA NIM chat models.
Run one shared NVIDIA API key across multiple ZCode provider configurations.
Run separate NVIDIA API keys per ZCode provider through the same local proxy.
Use NVIDIA NIM chat models like GLM 5.2 inside ZCode without editing ZCode itself.
| levent-dogan/zcode-nvidia-nim-fix | 0marildo/imago | 100/geotwitter | |
|---|---|---|---|
| Stars | 3 | 3 | 3 |
| Language | Python | Python | Python |
| Last pushed | — | — | 2015-09-10 |
| Maintenance | — | — | Dormant |
| Setup difficulty | moderate | easy | moderate |
| Complexity | 3/5 | 2/5 | 3/5 |
| Audience | developer | general | general |
Figures from each repo's GitHub metadata at analysis time.
Requires Windows, Python 3.10+, and at least one NVIDIA NIM API key.
This project is a small local fix for a specific compatibility problem between a code editor tool called ZCode and NVIDIA NIM, which is NVIDIA's service for running chat AI models through an OpenAI style API. Normally you would connect ZCode straight to NVIDIA NIM, but ZCode sends an extra field called extra_body that NVIDIA NIM does not accept, so requests fail with an error about an unsupported parameter. The fix works by running a small local proxy program on your own Windows computer. Instead of ZCode talking to NVIDIA directly, it talks to this proxy at a local web address, and the proxy strips out the fields NVIDIA does not support before forwarding a clean, compatible request on to NVIDIA NIM's real servers. Standard fields like the chosen model, the conversation messages, and streaming settings are kept and passed through untouched. The proxy supports two ways of handling API keys. In one mode, a single NVIDIA API key is set once and shared across every ZCode provider you configure. In the other mode, each ZCode provider can carry its own separate NVIDIA API key, and the proxy simply forwards whichever key ZCode sends, which is useful if you want to spread requests across several different NVIDIA accounts. The tool is not limited to one specific AI model, since it forwards whatever model name ZCode requests, as long as that model is available through your NVIDIA NIM account. Setup requires Windows 10 or 11, PowerShell, and Python 3.10 or newer. There is no extra Python package to install, since the proxy relies only on Python's built in libraries. Configuration is done through a provided launcher script, and the project includes a health check address and example requests for confirming everything is working correctly. The README is explicit that no NVIDIA API keys are stored in the repository itself, and the proxy avoids printing keys or full message content to its logs.
A local Windows proxy that fixes a request error between the ZCode editor and NVIDIA NIM's chat AI service by stripping an unsupported field before forwarding requests.
Mainly Python. The stack also includes Python, PowerShell, NVIDIA NIM.
The README does not state a license, so terms of use are unclear.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.