DeepSeek Harness Plugin Hub

Publish and manage complete Harness Profiles. Discover Plugins for your next setup.

Explore

PluginsPresetsDocsNews

Community

Publish a pluginContactReport an issue

Resources

Plugin Hub on GitHubDeepSeek HarnessSystem statusPrivacy notice
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

Independent and unofficial. Not affiliated with, authorized by, or endorsed by DeepSeek.

Pi Ai Auth — DSH Plugin for DeepSeek Harness
DeepSeek Harness Plugin Hub
ProfilesPluginsCategoriesNewsDocsSign inManage Profiles
ProfilesPluginsCategoriesNewsDocsSign in
← Plugins
P

@dingyiliao/dsh-pi-ai-auth

Pi Ai Auth

Provider-card OAuth controls and fallback commands for DeepSeek Harness pi-ai

The plugin will be installed here. Keep web if you are unsure.

npx -y @deepseek-ai/dsh plugin --profile web add github:dingyiliao/dsh-bundle-pi-ai-auth#e4754cfc921ab393257de2f3c0d9fd828754570d
READMECompatibilityVersions

Compatibility and provenance

Pi Ai Auth is published as @dingyiliao/dsh-pi-ai-auth and currently resolves to version 0.3.1. The Hub verifies its manifest and preserves the exact installation source for reproducible installs.

DSH compatibility
*
Runtime surfaces
web
Release source
github
Registry updated
9/19/2026

Versions

0.3.1stable
9/19/2026

Related plugins

Loading related plugins…

Latest
0.3.1
DSH
*
HMR
Process restart
Tree shaking
Safe tree shaking not declared
Unpacked size
Unavailable
Files
Unavailable
Surface
web
License
MIT
Source
github
GitHub
★ 0
Weekly downloads
0
Last push
9/20/2026
View source ↗
README badge

Click the badge to copy Markdown for your README.

Do you maintain this Plugin?Claim benefit · Priority security scan

Verify the GitHub repository declared in package.json to manage this listing. After you claim it, Hub will prioritize a security scan of the current version and publish the result when it passes.

Claim this Plugin →
Report an issue

Related plugins

More verified plugins in security-access.

Doctor@linxin666/dsh-doctorTransactional rescue mode for DSH profiles with a supervised launcher, isolated recovery capsule, deterministic repairs, health monitoring, and a local Web recovery consolePocketdsh-pocketPut DeepSeek Harness in your pocket: one package, one settings page, and scan a QR code on your phone to access DSH on your computer in sync (LAN + public network, real-time screen mirroring).DSCODE@toddzheng024/dscode-bundleA complete DeepSeek coding agent with persistent shell, Ultra collaboration and automatic permission review.Auto Reviewdsh-auto-reviewSecond-model AI auto-review for DeepSeek Harness approval requests: a read-only reviewer subagent decides allow/deny on the approval answerer chain, with fail-closed fallback and full session-log audit.

README

dsh-bundle-pi-ai-auth

简体中文

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.

Models settings UI

For every OAuth-capable pi-ai provider, the Models page shows its authorization state and the relevant action:

  • Sign in starts the provider flow, opens its sign-in URL in the system browser, and displays device codes or follow-up questions in a modal.
  • Sign out deletes the local provider credential while keeping the provider configured.
  • A provider that has not been saved yet shows that OAuth is available, but sign-in remains disabled until the built-in provider form is applied.

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.

State model

OAuth capability, enablement, and login are separate states:

  • OAuth-capable: the current llm-pi-ai/pi-ai installation registered an OAuth flow for the provider.
  • Enabled: llm-pi-ai.providers.<provider> exists, so the provider is a selectable model route.
  • Signed in: a provider-owned credential exists at 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.

Fallback commands

  • /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.

Requirements

  • DeepSeek Harness 0.1.6-alpha.1 or a compatible later 0.1.x release that provides settings.models.provider-card
  • A Web/Desktop composition containing authorization, credentials, settings, llm-pi-ai, the Remote gateway, and the Models settings UI
  • An account entitled to use the selected provider

OAuth 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

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.

Architecture

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.

License

MIT