GigaCode Proxy for editors: Cline, Roo Code, Continue
GigacodeOpenaiProxy
A dependency-free proxy connects GigaCode to Cline, Roo Code, Continue and Open WebUI, repairs tool call cuts and signs in with SberID
- 0 ★ on the repository
- Last commit
Broad access
Why this level
- The proxy signs in under your SberID account and caches the token on disk, and a token leak gives access to your account
- The agent in the editor edits files from the model replies, and a cut write can leave a file corrupted
Install
- Works in
- Services
Manual install
npm startClone the repository, copy `env.example` to `env.txt` and put your SberID login in `GIGACODE_USERNAME`; the editor address is `http://127.0.0.1:8000/v1`.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The proxy signs in under your SberID account and caches the token on disk, and a token leak gives access to your account
- The agent in the editor edits files from the model replies, and a cut write can leave a file corrupted
This is third-party code. Review the repository files before installing.
What it does
A Node.js proxy (one file, no dependencies) serves GigaCode as an OpenAI-compatible service at `http://127.0.0.1:8000/v1`: the `/v1/chat/completions`, `/v1/completions`, `/v1/responses`, `/v1/models` and `/health` routes, with and without streaming. Cline, Zcode, Roo Code, Continue or Open WebUI need the base URL, any non-empty API key and the model `CodeChat`. Tool calls are validated against the editor schema, and cut-off calls are detected by the proxy, which asks the editor to retry instead of passing a corrupted one on. Sign-in goes through SberID: the login is set in `GIGACODE_USERNAME` in the `env.txt` file, a browser opens on first launch and the token is cached afterwards. The proxy imposes no generation parameters. The `docs/` folder has sections on the API, streaming, tool calling and known defects.
Who it is for. Developers writing code in Cline, Roo Code or Continue who want to use the GigaCode model in them from a Russian network.
Good fit when
- The editor needs GigaCode instead of OpenAI and accepts only an OpenAI-compatible address
- An agent in Cline often cuts off large file writes and you need a proxy that detects it
- You must watch where context volume goes: the proxy warns about history bloat
- You need SberID sign-in with token caching, without pasting keys by hand
Not a fit when
- You need access from a phone or another computer: the proxy listens only on the local address `127.0.0.1`
- You need whole-file edits of 10 KB and more in one call: the server often cuts such writes off
- You need an official public API: the proxy works through SberID sign-in with your account
Example request
In Cline set the base URL `http://127.0.0.1:8000/v1`, key `sk-local`, model `CodeChat` and ask to fix a test in one fileLimitations
GigaCode is reachable only from Russian networks: with a VPN on, calls fail with `fetch failed`. Large file edits get cut off on the server side: writes of about 12 KB per call are often lost, 3-5 KB edits pass reliably, and the proxy only detects the cut and asks the editor to retry. Context grows fast and timeouts start after about 150 KB, and a new chat helps. A SberID account, a browser on first sign-in and Node.js 18 or newer are required. Zero stars, last commit in September 2026, MIT license.
How to disable. Stop the proxy process, delete its folder and the `env.txt` file, and remove the `http://127.0.0.1:8000/v1` address from the editor settings.
FAQ
Which editors does it work with?
With Cline, Zcode, Roo Code, Continue, Open WebUI and any client speaking the OpenAI API; details in `docs/editors.md`.
Which model should I set?
`CodeChat`; any non-empty API key works, for example `sk-local`.
How do I check the proxy signed in?
With `curl http://127.0.0.1:8000/health`: the `authenticated` field in the response shows `true`.
Why do large edits get cut off?
The cause is the GigaCode server. The proxy detects the cut and asks to retry, while 3-5 KB edits pass reliably.
Is a browser needed on first launch?
Yes: a SberID sign-in window opens, then the token is cached and the browser is not needed.
Discussion
No questions or reviews yet.
Related
All GigaChat toolsA single Node.js file turns the installed GigaCode CLI into a local OpenAI server with streaming and a shared dialogue history
A local proxy exposing GigaChat through OpenAI- and Anthropic-compatible APIs so it can drive Claude Code, aider and other agents
An ai-forever proxy that serves GigaChat through OpenAI, Anthropic and Gemini APIs so Claude Code, Codex and Gemini CLI can run on it
GigaCode project flows with hooks, gates and OpenSpec
gigacodeAgents
A monorepo of flows for the GigaCode CLI: development with stages and hard gates, a work progress observer and reverse analysis of code into a spec
GigaCode Bridge MCP
Gigacode-bridge-mcp
MCP server that delegates isolated code edits to GigaCode CLI in temporary Git worktrees and returns a patch for independent review
GigaChat plugin for DeepSeek Harness: an OAuth2 proxy
dsh-llm-gigachat
A DeepSeek Harness plugin that adds Sber GigaChat models to the regular model picker with a built-in OAuth2 proxy and automatic provider setup
README in short
The README lists features (OpenAI routes, tool calls, SberID sign-in), a quick start, an editor connection table and the `health` check, a document list and key caveats: access from Russia only, cut-off large edits and context growth.