Support Qoder CN (#4)
* feat(qoder-cn): add region endpoints and model catalog * feat(qoder-cn): add separate provider auth and streaming * docs: document Qoder CN provider
This commit is contained in:
@@ -1,10 +1,14 @@
|
||||
# pi-provider-qoder
|
||||
|
||||
A [pi](https://shittycodingagent.ai/) provider extension that connects pi to the **Qoder API**, exposing Qoder models through one provider surface.
|
||||
A [pi](https://shittycodingagent.ai/) provider extension that connects pi to the **Qoder API**, exposing Qoder Global and Qoder China models through provider surfaces.
|
||||
|
||||
## Features
|
||||
|
||||
- **Interactive Login**: Standard OAuth browser device-code flow or Personal Access Token (PAT) login.
|
||||
- **Two provider entries**:
|
||||
- `qoder` — Global / international Qoder.
|
||||
- `qoder-cn` — Qoder China, forced to CN endpoints and independent of `QODER_REGION`.
|
||||
- **Interactive Login**: Global Qoder supports browser device-code flow or Personal Access Token (PAT) login.
|
||||
- **Qoder CN PAT Login**: China edition uses a separate PAT login entry (`/login qoder-cn`) and CN token exchange endpoints.
|
||||
- **WAF Bypass**: Built-in WAF obfuscation and body encoding (`Encode=1`).
|
||||
- **COSY Signing**: Full COSY signature header generation (RSA/AES-CBC/MD5).
|
||||
- **Dynamic Model Catalog**: Dynamically fetches model limits, effort configurations, and options from the `/algo/api/v2/model/list` endpoint.
|
||||
@@ -24,69 +28,132 @@ Or install it globally with npm:
|
||||
npm install -g pi-provider-qoder
|
||||
```
|
||||
|
||||
Then log in from pi:
|
||||
Then log in from pi.
|
||||
|
||||
Global / international edition:
|
||||
|
||||
```text
|
||||
/login qoder
|
||||
```
|
||||
|
||||
The login menu offers two methods:
|
||||
China edition:
|
||||
|
||||
- **Browser Login** — OAuth device-code flow; complete authorization in your browser.
|
||||
- **Use API Key (PAT)** — paste a Qoder Personal Access Token (`pt-...`).
|
||||
```text
|
||||
/login qoder-cn
|
||||
```
|
||||
|
||||
### Personal Access Token (PAT)
|
||||
|
||||
A Qoder PAT (`pt-...`) cannot authenticate API calls directly — the provider
|
||||
exchanges it for a short-lived job token (mirroring the official `qodercli`
|
||||
flow) and resolves your account identity automatically. You can supply a PAT in
|
||||
two ways:
|
||||
exchanges it for a short-lived job token (mirroring the official `qodercli` /
|
||||
`qoderclicn` flow) and resolves your account identity automatically.
|
||||
|
||||
Global Qoder:
|
||||
|
||||
- Run `/login qoder` and choose **Use API Key (PAT)**, then paste the token.
|
||||
- Set the `QODER_PERSONAL_ACCESS_TOKEN` (or `QODER_PAT`) environment variable,
|
||||
then run `/login qoder` — the PAT is picked up automatically and exchanged
|
||||
without further prompts. This is the recommended path for headless/CI setups.
|
||||
- Or set `QODER_PERSONAL_ACCESS_TOKEN` (or `QODER_PAT`) before starting pi.
|
||||
|
||||
Qoder China:
|
||||
|
||||
- Run `/login qoder-cn`, then paste the CN PAT.
|
||||
- Or set `QODERCN_PERSONAL_ACCESS_TOKEN` (or `QODERCN_PAT`) before starting pi.
|
||||
|
||||
> The exchanged job token is short-lived; the provider transparently re-exchanges
|
||||
> the stored PAT when it expires.
|
||||
|
||||
### Region environment variables
|
||||
|
||||
The provider also understands these optional variables:
|
||||
|
||||
```bash
|
||||
export QODER_REGION=cn # or QODER_BACKEND=cn / QODER_MODE=cn
|
||||
```
|
||||
|
||||
Setting a CN PAT without a global PAT also auto-selects CN mode for the `qoder`
|
||||
entry, but the recommended explicit China entry is still `/login qoder-cn` and
|
||||
`--provider qoder-cn`.
|
||||
|
||||
## Endpoints
|
||||
|
||||
Global:
|
||||
|
||||
- PAT exchange: `https://openapi.qoder.sh/api/v1/jobToken/exchange`
|
||||
- User info: `https://openapi.qoder.sh/api/v1/userinfo`
|
||||
- Usage: `https://openapi.qoder.sh/api/v2/quota/usage`
|
||||
- Model / chat gateway: `https://api3.qoder.sh/algo/api/v2/...`
|
||||
|
||||
China:
|
||||
|
||||
- PAT exchange: `https://openapi.qoder.com.cn/api/v1/jobToken/exchange`
|
||||
- User info: `https://openapi.qoder.com.cn/api/v1/userinfo`
|
||||
- Usage: `https://openapi.qoder.com.cn/api/v2/quota/usage`
|
||||
- Model / chat gateway: `https://gateway.qoder.com.cn/algo/api/v2/...`
|
||||
|
||||
## Models
|
||||
|
||||
Exposes the following backing models:
|
||||
### Global `qoder`
|
||||
|
||||
- **Tier Tiers**: `auto`, `ultimate`, `performance`, `efficient`, `lite`
|
||||
Exposes the backing model keys returned by Qoder, including:
|
||||
|
||||
- **Tier Models**: `auto`, `ultimate`, `performance`, `efficient`, `lite`
|
||||
- **Frontier Models**:
|
||||
- `qmodel` (Qwen3.7 Plus)
|
||||
- `qmodel_latest` (Qwen3.7 Max)
|
||||
- `dmodel` (DeepSeek V4 Pro)
|
||||
- `dfmodel` (DeepSeek V4 Flash)
|
||||
- `gm51model` (GLM 5.1)
|
||||
- `kmodel` (Kimi K2.6)
|
||||
- `mmodel` (MiniMax M3)
|
||||
- `gm51model` (GLM)
|
||||
- `kmodel` (Kimi)
|
||||
- `mmodel` (MiniMax)
|
||||
|
||||
### China `qoder-cn`
|
||||
|
||||
The China provider exposes friendly model IDs and maps them back to Qoder CN's
|
||||
internal keys at request time:
|
||||
|
||||
| Friendly ID | Qoder CN key | Context | Images | Reasoning |
|
||||
| --- | --- | ---: | :---: | :---: |
|
||||
| `auto` | `auto` | 180K | ✅ | ✅ |
|
||||
| `qwen3.7-max` | `qmodel_latest` | 1M | ✅ | ✅ |
|
||||
| `qwen3.7-plus` | `qmodel` | 1M | ❌ | ✅ |
|
||||
| `qwen3.6-flash` | `q36fmodel` | 1M | ❌ | ✅ |
|
||||
| `deepseek-v4-pro` | `dmodel` | 1M | ❌ | ✅ |
|
||||
| `deepseek-v4-flash` | `dfmodel` | 1M | ❌ | ❌ |
|
||||
| `glm-5.2` | `gm51model` | 200K | ✅ | ✅ |
|
||||
| `kimi-k2.6` | `kmodel` | 256K | ✅ | ✅ |
|
||||
| `minimax-m2.7` | `mmodel` | 200K | ❌ | ❌ |
|
||||
|
||||
Compatibility aliases are also accepted for request mapping, such as
|
||||
`qwen3.6-plus` → `qmodel`, `glm-5.1` → `gm51model`, and `minimax-m3` → `mmodel`.
|
||||
|
||||
## Usage
|
||||
|
||||
Once logged in, select any Qoder model in pi:
|
||||
|
||||
```text
|
||||
/model ultimate
|
||||
/model qwen3.7-plus
|
||||
```
|
||||
|
||||
Or let Qoder select automatically:
|
||||
Or start directly:
|
||||
|
||||
```text
|
||||
/model auto
|
||||
```bash
|
||||
pi --provider qoder-cn --model qwen3.7-plus
|
||||
```
|
||||
|
||||
Global example:
|
||||
|
||||
```bash
|
||||
pi --provider qoder --model auto
|
||||
```
|
||||
|
||||
## Architecture
|
||||
|
||||
```
|
||||
```text
|
||||
src/
|
||||
├── index.ts # Extension registration
|
||||
├── cosy.ts # COSY Signature and Machine ID resolver
|
||||
├── login.ts # OAuth Device Flow + PAT login sequence
|
||||
├── cosy.ts # COSY signature, machine ID, region/endpoints, CN model aliases
|
||||
├── login.ts # OAuth device flow + PAT login sequence
|
||||
├── pat.ts # PAT → job-token exchange + identity resolution
|
||||
├── models.ts # Model definitions and Dynamic Config Cache
|
||||
├── models.ts # Model definitions and dynamic config cache
|
||||
├── oauth.ts # PAT / OAuth callback orchestrator
|
||||
├── stream.ts # Main streaming response handler
|
||||
├── transform.ts # Message conversions (OpenAI schema mapping)
|
||||
|
||||
Reference in New Issue
Block a user