Introduction

DeepSeek Harness (DSH) uses a pluggable architecture, and its ecosystem is maintained by the community. When using subscription plans such as Claude Pro, ChatGPT Plus, and GitHub Copilot, many services do not directly provide API keys. Users typically need to complete authorization manually in a browser or work around official limitations. The dsh-vendor-login plugin integrates the login workflows for these services directly into the DSH Web UI settings page, allowing users to use the quotas included with their subscriptions instead of token-based billing.

Plugin Overview

dsh-vendor-login is a DSH plugin maintained by developer MochiNek0. It supports four vendors: Anthropic, OpenAI, GitHub Copilot, and xAI. Its core value is enabling users to log in to these services with their own subscription accounts and directly use the included quotas in the DSH Web UI rather than paying per token.

Core Features

  • Multi-vendor support: Supports Anthropic Pro/Max/Team (via OAuth, requiring local port 53692), OpenAI ChatGPT Plus/Pro (via OAuth, using port 1455), GitHub Copilot (via device-code login), and xAI SuperGrok/X Premium+ (via device-code login).
  • UI integration: The login entry point is located directly on the DSH Web UI settings page. Users can click the card button to complete authorization in a browser.
  • Configuration control: The plugin uses the vendors list in the profile settings file to control which vendors display a login entry point.
  • Quota priority: Prefers the quotas included with the vendor subscription over token-based billing.

Installation and Activation

Before installation, ensure that DSH 0.1.2-rc.1 or later is installed and that pnpm is available in the system PATH. The installation steps are as follows:

  1. Install the plugin using the following command:
    dsh plugin --profile web add dsh-vendor-login
  1. After installation, restart the dsh web service to activate the plugin.

Typical Usage

  1. In the DSH Web UI, open Settings → Models.
  2. Find the provider card for the corresponding vendor. A sign-in button appears at the bottom.
  3. Click the button and complete the authorization flow in the browser window that opens.
  4. If the flow requires pasting a returned code or selecting an account, complete it directly in the current card.
  5. After successful authorization, the vendor’s models immediately appear in the model selector.
  6. Control the displayed vendor list: edit the profile settings file and configure the vendors list under the vendor-login namespace (for example: vendors: [anthropic, openai-codex]).

Notes and Limitations

  • Security mechanisms: The /plugin/vendor-login/* route does not have an independent authentication mechanism. It relies on browser cross-site request checks (Sec-Fetch-Site/Origin) and Content-Type: application/json. If webServer is bound to a non-localhost address, the plugin issues a warning at startup.
  • Login limitations: For a given vendor, only one login attempt can be in flight at a time (ALREADY_IN_FLIGHT); refreshing the page during login interrupts and restarts the flow.
  • xAI limitations: xAI may restrict OAuth endpoints based on plan tiers. Some standard SuperGrok accounts may receive HTTP 403 responses during inference after successful login.
  • Permissions and compliance: Logout only deletes locally stored credentials; it does not revoke the vendor-side session. Reusing tokens in a third-party harness is a gray area and may violate terms of service (ToS), with risks of throttling or account suspension.
  • Compatibility: Only vendors without API keys are supported. Vendors that provide API keys (such as the official OpenAI API) are not covered and should use apiKeyEnv configuration.

Summary

With dsh-vendor-login, the DeepSeek Harness plugin ecosystem further completes support for mainstream AI subscription services. It enables developers to directly use the included quotas from subscriptions such as Claude Pro and ChatGPT Plus within the DSH environment, simplifying multi-environment collaboration workflows. For more details and source code, refer to the plugin directory or GitHub repository.