142 ·GitHub
What is this?
Qoder Workflow is an unofficial toolkit built around Qoder (an AI coding assistant) that patches machine identity, harvests Personal Access Tokens, decrypts local session credentials, and exposes the resulting access through an OpenAI-compatible gateway serving 15 upstream models (Claude, Qwen, Kimi, GLM, DeepSeek, MiniMax, and more).
Is this an official Qoder client?
No, it is a 5-module unofficial toolkit: a machine-identity patcher, a Personal Access Token harvester, a session-token decryptor, a quota/activity claim engine, and an OpenAI/Anthropic-compatible proxy gateway that sits on top of Qoder's backend.
How do I get the gateway running?
Launch the gateway module to spin up the REST server exposing /v1/chat/completions and /v1/models, send a test request via cURL to check model routing, and use the separate CLI to run the verification and state patcher.
What do I need before running the harvester and decryptor?
It's pure Python with no listed external packages, but the decryptor needs a working local Qoder CLI installation to run in its sandbox and extract the auth tokens.
What's the catch with using this?
This is not an officially sanctioned Qoder integration: it patches machine/account identifiers, auto-generates Personal Access Tokens, and decrypts Qoder's local auth storage to pull out live session tokens, so it can break or get an account flagged whenever Qoder changes its internals or anti-abuse checks.
What kind of credentials does this handle?
It generates and extracts real 64-character Personal Access Tokens and session tokens tied to an actual Qoder account, plus hardware machine-binding codes used for quota checks, so these outputs should be treated as sensitive secrets.
What models can I reach through the gateway?
The catalog covers 15 models, including Claude Opus/Sonnet/Haiku 4.x, Qwen3.7/3.8-Max, Kimi K2.7/K3, GLM-5.2, DeepSeek V4 Pro/Flash, and MiniMax M3, selectable via IDs like qd/ultimate or qd/performance.
What does the COSY claim engine actually do?
It manages hardware machine binding (Cosy-MachineToken, Cosy-MachineCode) and computes MD5 date-signatures to inspect quota and scan for activity-based eligibility on the harvested account.
Why does it patch machine IDs and MAC addresses?
Resetting machine IDs, MAC addresses and app state lets a device re-trigger Qoder's account provisioning flow, including Google Workspace SSO handshakes and mail verification, effectively creating a fresh-looking identity.
Does the gateway support streaming responses?
Yes, it supports SSE streaming as well as fallback routing across the configured upstream models.
What are similar projects?
casbin-gateway, openclaw-zero-token, OmniRoute, Baize, SteamDaddy-Backup, GenP, magpie, ollama
Which topics is it in?
activation-tools, crack, cracking, sse, bypass, glm, kimi, api-gateway, hacking-tool, qwen, http, openai-compatible