pi-qoder-account-provider

Use Qoder account models, including Qwen3.8-Max, as a Pi provider through the official Qoder Agent SDK.

Packages

Package details

extension

Install pi-qoder-account-provider from npm and Pi will load the resources declared by the package manifest.

$ pi install npm:pi-qoder-account-provider
Package
pi-qoder-account-provider
Version
0.1.1
Published
Sep 14, 2026
Downloads
188/mo · 168/wk
Author
nyn5255
License
MIT
Types
extension
Size
24.5 KB
Dependencies
2 dependencies · 2 peers
Pi manifest JSON
{
  "extensions": [
    "./extensions/usage-entry.ts"
  ]
}

Security note

Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.

README

pi-qoder-account-provider

Use Qoder account models in Pi, including Qwen3.8-Max, through Qoder's official Agent SDK and CLI login.

This package does not use CPA, reverse-engineered browser sessions, COSY signatures, or WAF bypasses.

Install

Requirements:

  • Node.js 20+
  • Pi
  • Qoder CLI 1.1.40 or newer
  • Qoder account or Personal Access Token
npm install -g @qoder-ai/qodercli
qodercli login
pi install npm:pi-qoder-account-provider

Restart Pi or run /reload, then:

/login qoder

Choose Reuse qodercli login. Alternatively, choose Personal Access Token or set QODER_PERSONAL_ACCESS_TOKEN.

Select model:

/model

Choose qoder/Qwen3.8-Max.

Models

The package registers the current Qoder account catalog observed during release, including:

  • Qwen3.8-Max, Qwen3.8-Flash, Qwen3.7-Max, Qwen3.7-Plus
  • Kimi-K3, Kimi-K2.7-Code
  • GLM-5.3, GLM-5.3-Flash
  • DeepSeek-V4-Pro, DeepSeek-V4-Flash
  • MiniMax-M3
  • Auto, Ultimate, Performance, Efficient, Lite, Cantus

Qoder updates model availability server-side. Use qodercli --list-models as account-specific truth.

How it works

Qoder publishes an Agent SDK rather than a standard OpenAI-compatible endpoint. This extension adapts each Pi provider request into one ephemeral Qoder SDK query.

Qoder runtime tools are disabled. Pi remains responsible for tool execution and approval. When Qoder needs a tool, the extension asks it to emit a strict <pi_tool_call> envelope, converts that envelope into a Pi tool call, then sends the Pi tool result back on the next turn.

Security

Prompt text, conversation history, tool schemas, and necessary tool results are sent to Qoder's model service. Do not use this provider for data that must not leave your environment.

Qoder built-in file, shell, web, subagent, and skill tools are disabled by this bridge. Qoder queries use dontAsk, maxTurns: 1, and persistSession: false.

PATs are entered through Pi secret input or read from QODER_PERSONAL_ACCESS_TOKEN. Never commit tokens.

Limitations

  • Tool calling uses a model-followed envelope, not provider-native structured tool calls.
  • One Pi tool loop starts multiple Qoder queries. It can be slower and consume more Credits than one text response.
  • Input is currently text-only. Qoder vision models are listed, but Pi image blocks are not bridged yet.
  • Qoder Credits do not map cleanly to Pi per-million-token pricing. Static model prices remain zero; SDK request cost is preserved when available.

Verify

npm test
npm run typecheck
npm pack --dry-run

After login:

pi --provider qoder --model Qwen3.8-Max --thinking off -p \
  'Reply with exactly: QODER_PI_OK'

Uninstall

pi remove npm:pi-qoder-account-provider

Sources and terms

Extension source is MIT licensed. Qoder CLI and Agent SDK remain governed by Qoder's terms.