pi-provider-qoder-cn 0.1.0

package/LICENSE

@@ -0,0 +1,22 @@
+MIT License
+
+Copyright (c) 2025 simonsmh (pi-provider-qoder, https://github.com/simonsmh/pi-provider-qoder)
+Copyright (c) 2025 divingyu (pi-provider-qoder-cn, https://github.com/divingyu/pi-provider-qoder-cn)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,234 @@
+# pi-provider-qoder-cn
+
+A [pi](https://shittycodingagent.ai/) provider extension for **Qoder CN** (`qoder.com.cn`),
+with a quota command and enterprise (VPC) endpoint support.
+
+This is a focused fork of [`pi-provider-qoder`](https://github.com/simonsmh/pi-provider-qoder)
+(MIT). It registers **only** the CN provider, so it can be installed alongside the
+upstream package without a provider-id collision.
+
+```bash
+pi install npm:pi-provider-qoder-cn
+```
+
+## What this fork adds
+
+| Feature | Upstream | This fork |
+|---|---|---|
+| Qoder CN provider (`qoder-cn`) | ✅ | ✅ |
+| Qoder Global provider (`qoder`) | ✅ | ➖ not registered (see below) |
+| `/qoder-cn.usage` quota command | ❌ | ✅ |
+| `/qoder-endpoint` enterprise (VPC) switching | ❌ | ✅ |
+| Current CN model catalog (`qwen3.8-max` / `qwen3.8-flash`, …) | ❌ | ✅ |
+| Stable CN model ids for `enabledModels` | ❌ | ✅ |
+
+> **Why CN only?** Both packages would register a provider named `qoder-cn`, and
+> pi identifies providers by id. Registering only `qoder-cn` here means this
+> package and the upstream one can coexist. If both are installed, whichever is
+> listed last in `settings.json` wins for `qoder-cn` — so put this package last
+> to get the friendly ids and the quota command. Note that the upstream package
+> registers the global `qoder` provider too, but it only appears in
+> `--list-models` once global credentials exist.
+>
+> If you migrated from the upstream package, also remove the old local extension
+> directory if you have one, since a directory at
+> `~/.pi/agent/extensions/pi-provider-qoder/` registers `qoder-cn` as well.
+> Check with `pi list` and inspect `~/.pi/agent/extensions/`.
+>
+> **Migrating from the upstream package:** model ids change from
+> `Qwen3.8-Flash` to `qwen3.8-flash`. Update `enabledModels` entries in
+> `settings.json` and any session pins accordingly. The old ids keep resolving
+> internally, so only the configured names need updating.
+
+## Install
+
+```bash
+pi install npm:pi-provider-qoder-cn
+```
+
+Then authenticate once:
+
+```text
+/login qoder-cn
+```
+
+CN supports a Personal Access Token rather than browser OAuth. Create one at
+<https://qoder.com.cn/account/integrations> and paste it when prompted, or export
+it before starting pi:
+
+```bash
+export QODERCN_PERSONAL_ACCESS_TOKEN="<your PAT>"
+```
+
+## Commands
+
+### `/qoder-cn.usage`
+
+Shows the plan allowance and any purchased add-on credits.
+
+```text
+Qoder CN Plan (personal_standard)
+[--------------------] 0% used
+  [--------------------] Add-on quota: 0 credits / 700 credits used (0%) · 700 credits left
+Resets: never
+Manage: https://qoder.com.cn/account/usage
+```
+
+Append `json` to print the untouched API payload — useful when a field you need
+is not in the formatted view:
+
+```text
+/qoder-cn.usage json
+```
+
+Notes:
+
+- The plan allowance (`Plan quota`) and top-up credits (`Add-on quota`) are
+  independent buckets with independent expiry, so both are listed when present.
+- `Resets: never` means the API reported the year-9999 sentinel, i.e. the
+  allowance does not reset on a schedule.
+- `(plan quota is prorated)` appears after a mid-cycle plan change.
+- The command uses the same stored token as chat requests, refreshing it first,
+  so it reports the same quota the model is actually billed against.
+
+### `/qoder-endpoint`
+
+Show or set the CN gateway. Enterprises on a private (VPC) deployment use a
+per-tenant host instead of the public one.
+
+```text
+/qoder-endpoint                      # show the active endpoint
+/qoder-endpoint acme                 # enterprise instance "acme"
+/qoder-endpoint acme-gateway.vpc.qoder.com.cn
+/qoder-endpoint https://qoder.internal.example.com
+/qoder-endpoint default              # back to the public gateway
+```
+
+A bare instance label `acme` expands to the standard enterprise hostnames:
+
+| Role | Host |
+|---|---|
+| Gateway (chat) | `acme-gateway.vpc.qoder.com.cn` |
+| OpenAPI (auth, quota) | `acme-openapi.vpc.qoder.com.cn` |
+| Console | `acme.vpc.qoder.com.cn` |
+
+Any other domain is treated as a custom deployment and serves every role from
+that one origin.
+
+Setting the endpoint also refreshes the model catalog, because an enterprise
+instance may expose a different model set than the public gateway.
+
+The choice is persisted to `~/.pi/agent/qoder-cn-settings.json`. Resolution order
+at startup is:
+
+1. `QODER_VPC_ENDPOINT` / `QODERCN_VPC_ENDPOINT`
+2. `~/.pi/agent/qoder-cn-settings.json`
+3. `~/.pi/agent/auth.json` (the `qoder-cn` entry)
+4. `~/.qoder-cn/settings.json` (the Qoder IDE's own file)
+
+> The token and the endpoint must belong to the same instance. Pointing an
+> enterprise endpoint at a public-gateway token fails authentication.
+
+## Models
+
+| Model | id | Context | Thinking effort |
+|---|---|---|---|
+| Auto | `auto` | 200K | — |
+| Qwen 3.8-Max | `qwen3.8-max` | 1M | ✅ |
+| Qwen 3.8-Flash | `qwen3.8-flash` | 1M | ✅ |
+| Qwen 3.7-Max | `qwen3.7-max` | 1M | — |
+| Qwen 3.7-Plus | `qwen3.7-plus` | 1M | — |
+| Qwen 3.7-Flash | `qwen3.7-flash` | 1M | — |
+| DeepSeek V4 Pro | `deepseek-v4-pro` | 1M | ✅ |
+| DeepSeek V4 Flash | `deepseek-v4-flash` | 1M | ✅ |
+| GLM-5.3 | `glm-5.3` | 1M | ✅ |
+| GLM-5.3-Flash | `glm-5.3-flash` | 1M | ✅ |
+| GLM 5.2 | `glm-5.2` | 1M | ✅ |
+| Kimi-K3 | `kimi-k3` | 1M | ✅ |
+| Kimi-K2.7-Code | `kimi-k2.7-code` | 256K | — |
+| MiniMax M2.7 | `minimax-m2.7` | 200K | — |
+
+```bash
+pi --provider qoder-cn --model qwen3.8-flash
+```
+
+```text
+/model qwen3.8-flash
+```
+
+The live catalog is fetched from Qoder and cached for an hour; the table above is
+the offline fallback and the source of model ids.
+
+**Ids are stable.** This fork uses lowercase slugs (`qwen3.8-flash`) rather than
+the whitespace-stripped display name, so `enabledModels` entries such as
+`qoder-cn/qwen3.8-flash` keep working across upgrades.
+
+## Development
+
+```bash
+npm install
+npm run check      # tsc --noEmit
+npm run lint       # biome
+npm test           # vitest
+npm run build      # esbuild -> dist/index.js
+```
+
+`src/` is TypeScript; `dist/index.js` is the build artifact that
+`pi.extensions` points at. **`dist/` is committed on purpose.**
+
+`pi install git:...` runs `npm install --omit=dev`, so devDependencies (esbuild)
+are absent during install and an install-time `prepare` build would fail. The
+committed bundle avoids that; `prepublishOnly` still rebuilds before every npm
+publish, so the published bundle is always current. Run `npm run build` and
+commit `dist/` whenever you change `src/`.
+
+## Publishing
+
+The tarball ships `dist/`, `LICENSE`, `README.md` and `package.json` only, as
+controlled by the `files` field.
+
+```bash
+npm login                     # once, if not already authenticated
+npm run check && npm run lint && npm test && npm run build
+npm publish --access public
+```
+
+`prepublishOnly` re-runs check, lint, test and build, so a broken build cannot
+be published. Verify the tarball before pushing:
+
+```bash
+npm pack --dry-run            # confirm exactly 4 files
+```
+
+The `pi-package` keyword makes the package eligible for the
+[Pi package gallery](https://pi.dev/packages); no separate submission is needed.
+
+### Verify an install
+
+```bash
+pi install npm:pi-provider-qoder-cn
+pi --list-models | grep qoder-cn    # expect 14 models, including auto
+```
+
+Then in a session, `/qoder-cn.usage` should print the quota, and a prompt that
+needs a tool (for example "run `echo hi` with bash") must execute it rather than
+reply with a `<tool_call>` code block.
+
+## Compatibility
+
+Requires pi >= 0.86. Pi hands providers a normalized transcript: the system
+prompt and tool declarations live in transcript system messages and must be read
+with `getCurrentSystemPrompt()` / `getCurrentTools()`. Reading the legacy
+top-level `context.systemPrompt` / `context.tools` yields empty values, which
+sends a request with no tools and makes the model emit tool calls as plain text
+that never execute.
+
+## Credits
+
+Forked from [`pi-provider-qoder`](https://github.com/simonsmh/pi-provider-qoder) by
+[simonsmh](https://github.com/simonsmh), MIT licensed. The COSY request signing,
+Qoder wire protocol, and provider scaffolding come from that project.
+
+## License
+
+[MIT](./LICENSE)