Skip to content

About

QwenWork (千问办公) as a magpie / OpenCode provider — sign in with QwenWork's own device flow, use its models.

Topics

Resources

Stars

4 stars

Watchers

0 watching

Forks

Repository files navigation

opencode-qwenwork-auth — QwenWork (千问办公) for magpie / OpenCode

中文说明 / Chinese

Platform Platform

Your QwenWork subscription as an OpenCode provider: signs in through QwenWork's own device flow and serves its models over QwenWork's own agent endpoint, with the host agent's tools riding along.

Unofficial. Not reviewed by magpie. Read the code before installing. Verified end to end on macOS against the QwenWork 1.2.5 desktop app.

Provider id Service Models
qwenwork 千问办公 (gateway.qwenwork.cn) the account's own qwork catalog

The package exports QwenWorkAuthPlugin.

Install

From this GitHub repository (recommended):

magpie plugin add github:harwinvoid/magpie-plugin-qwenwork
magpie plugin login qwenwork

magpie plugin add accepts any spec bun does: an npm package, a github:owner/repo repository, or a local folder. This repository is meant to be installed by its github: spec — that is what follows the code here and picks up updates.

The plugin has no runtime dependencies of its own. Pick qwenwork/<model> for an agent, e.g. magpie claude qwenwork/flash.

  • Already installed from a local folder? Add the github: spec and remove the folder one, so magpie tracks the repository instead:
    magpie plugin add github:harwinvoid/magpie-plugin-qwenwork
    magpie plugin rm /path/to/your/local/magpie-plugin-qwenwork
    The sign-in carries over.
  • Finding it in the app. The repository is tagged magpie-plugin, so magpie lists it under Plugins → Discover → Unofficial (community plugins, not reviewed by magpie). Install it there, or with the command above.

How it works

Sign-in uses the same PKCE device flow the QwenWork desktop app uses, then keeps the access token refreshed with its own refresh token. The account is shown by name, falling back to its id.

Chat is rewritten as QwenWork's own agent_chat_generation request — the same request shape the desktop app's engine and the Qoder client speak:

  • The host agent's tools ride along in the request, so an OpenCode session keeps its full tool loop (read, edit, bash, …) on a qwenwork model.
  • Tool calls come back structured, either as the gateway's native tool_calls or lifted out of inline <tool_call> text — never as markup in the answer.
  • The host's system messages ride along under a short QwenWork preamble, and reasoning, usage and credits map back the way the client shows them.

Verified configuration, read from the desktop app's own bundle:

clientId      e883ade2-e6e3-4d6d-adf7-f92ceff5fdcb
web / openapi / api   https://gateway.qwenwork.cn
redirect_uri  qwenwork-cn://
device flow   /device/selectAccounts -> /api/v1/deviceToken/poll
refresh       /api/v1/deviceToken/refresh   (target: "c")
chat          /algo/api/v2/service/pro/sse/agent_chat_generation
models        the "qwork" scene

Every value, plus the COSY RSA key, can be overridden through QWENWORK_* environment variables and defaults.json.

Usage

Magpie shows the account's credits beside the provider. They come from the same account-context the sign-in already reads, so no extra request is made:

Shown From
plan name plan.name
reset time plan.next_refresh_date, else plan.next_due_date
credits used quota.used / quota.total, as a percentage and used / total credits

A refused read (401/403) marks the sign-in lapsed; any other error is reported without a token. See qwenworkUsage() in index.mjs. magpie quota qwenwork prints it in the terminal:

qwenwork · Your Plan · until Nov 1 · you@example.com  subscription  Credits 1% (17.94 / 2000 credits)

Notes

  • Only the chat completions endpoint is served. A lapsed sign-in is reported as such, and an upstream failure is trimmed and token-redacted before it reaches the caller.
  • The provider's icon is the QwenWork app icon, used to identify the product.
  • MIT.

Verify

node check.mjs     # offline, mocked upstream
./live-e2e.sh      # live: models, chat, streaming through the gateway

Files

  • index.mjs — the provider: configuration, device sign-in, usage.
  • vendor/qoder.mjs — the adapter shared with the Qoder plugin: sign-in, the agent_chat_generation codec, tool-call lifting, usage.
  • defaults.json — verified desktop configuration.
  • icon.png — the provider's picture, the QwenWork app icon.
  • check.mjs, live-e2e.sh — the offline and live checks.

About

QwenWork (千问办公) as a magpie / OpenCode provider — sign in with QwenWork's own device flow, use its models.

Topics

Resources

Stars

4 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages