@dingyiliao/dsh-pi-ai-auth
DeepSeek Harness pi-ai 的提供商卡片 OAuth 控制和备用命令
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:dingyiliao/dsh-bundle-pi-ai-auth#e4754cfc921ab393257de2f3c0d9fd828754570dPi Ai Auth 以 @dingyiliao/dsh-pi-ai-auth 发布，当前版本为 0.3.1。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Provider-card OAuth controls for DeepSeek Harness pi-ai, with /auth-* commands retained as a fallback.
The bundle does not implement provider OAuth protocols or store and refresh tokens itself. @deepseek-ai/dsh-llm-pi-ai registers the provider-owned authorization flows and credential records. This bundle adds the generic interaction surfaces around those flows.
For every OAuth-capable pi-ai provider, the Models page shows its authorization state and the relevant action:
The browser extension uses the official settings.models.provider-card slot. Its Host RPC controller is also owned by this package, so installing it requires no OAuth-specific edits to the DSH repository.
OAuth capability, enablement, and login are separate states:
llm-pi-ai/pi-ai installation registered an OAuth flow for the provider.llm-pi-ai.providers.<provider> exists, so the provider is a selectable model route.records.llm-pi-ai/<provider>.Installing this bundle does not automatically enable any provider. The user first adds a provider in Models settings (or with /auth-add), then signs in.
/auth-list: list OAuth-capable providers with enablement and login state./auth-add [provider] [method]: add and sign in; omitting the provider opens a selection question./auth-login [provider] [method]: sign in to an enabled provider./auth-status [provider]: inspect one provider; without a provider it behaves like /auth-list./auth-logout [provider]: remove the local credential while keeping the provider enabled./auth-remove [provider]: remove a user-added provider and its local credential.method defaults to oauth. A provider enabled by another bundle's base configuration cannot be removed with /auth-remove; update the owning bundle instead.
0.1.6-alpha.1 or a compatible later 0.1.x release that provides settings.models.provider-cardauthorization, credentials, settings, llm-pi-ai, the Remote gateway, and the Models settings UIOAuth itself works with the upstream 0.1.6-alpha.2 UI. That release can still
show the generic API-key editor for an OAuth-only provider because it does not
yet expose the adapter's apiKeyConfigurable capability. A DSH build carrying
that generic capability hides the inapplicable API-key/Edit controls. This
bundle deliberately does not patch or hide core UI with provider-specific CSS.
Install the current GitHub version into a Web profile:
dsh plugin --profile web add github:dingyiliao/dsh-bundle-pi-ai-auth
The same package spec can be entered in Desktop's plugin manager. Restart the corresponding DSH app after installation, add an OAuth-capable provider under Settings → Models, and use the sign-in action on that provider card.
After an npm release is available, the registry form is:
dsh plugin --profile web add @dingyiliao/dsh-pi-ai-auth
The repository includes its built Host and Client entry files, so Git installs do not need to run a package build script.
Models provider card
-> bundle browser extension (settings.models.provider-card)
-> bundle-owned piAiAuthorization Remote controller
-> ctx.authorization.begin(llm-pi-ai/<provider>)
-> provider-owned flow from llm-pi-ai / pi-ai
-> browser, device-code, or follow-up prompt interaction
-> provider-owned credential record
-> llm-pi-ai reads and refreshes that record for requests
No temporary token environment variable is created. Logout removes the local record; it does not claim to revoke the grant at the remote provider.
MIT