Preface

When handling multiple models and accounts in DeepSeek Harness (DSH), the common practice is to add an extra proxy gateway outside the core or hard-code OAuth, quota reading, and request adaptation from various providers directly into the business code. As the number of accounts grows, login states, model directories, and quota status can easily become siloed, misaligned with DSH’s own commands and model selection.

Dockyard DSH takes a different approach: as a native bundle/plugin for DSH, it connects multiple official OAuths and local sessions to a single account pool and runtime. Commands, model selection, and LLM generation all read from the same state, eliminating the need for an additional gateway or cramming provider logic into DSH’s core. Below, we introduce what it is, what it can do, and how to install and use it.

What Is This

Dockyard DSH (aitabby/dockyard-dsh) is maintained by AITabby and classified as admin-security in the SkillHub community directory. The repository description reads: A native account pool and provider plugin for DeepSeek Harness; package.json labels it as a macOS-only native account-pool and provider plugin, currently at version 0.1.1, licensed under MIT.

It solves the core problem of managing multiple providers’ accounts, real-time model directories, and quota status uniformly within DSH, while initiating calls through provider-native request chains. If the corresponding official client, CLI, or OAuth source is not installed or logged in, Dockyard returns a clear unavailable/degraded state, rather than faking availability with hardcoded accounts, models, or quotas.

Current provider modules (per GitHub README):

  • Codex — Official browser OAuth, CLI fallback, native Responses request chain
  • Antigravity — Google official browser OAuth, local sessions, real-time model directory, quota/credits, native Gemini SSE
  • Grok — xAI official browser OAuth, CLI fallback, real-time model directory, official Build credits cycle, provider-native streaming
  • Claude — Official browser OAuth (supports manual callback with state), CLI fallback, native request adaptation
  • Cursor — Official browser login polling, CLI fallback, native request adaptation

Core Features

Account Pool and Provider Management

Within a running DSH profile, manage accounts and providers via the /dockyard command. Clicking “Login to Add Account” opens the provider’s official browser authorization page, and after selecting an account, it securely imports it into the account pool; when a provider is unavailable, it retains CLI fallback.

Scanning existing official login states on the local machine and adding new accounts are two independent operations; existing accounts are not silently duplicated by the “add” function.

Account Pool Policies and Real-Time Status

Supports manual selection, sticky session, round-robin, and failover account pool policies. Model directories, inference tiers, plans, and quota windows are all read in real-time from the provider; all commands, model selection, and LLM generation go through the same Dockyard runtime, with no second account pool or quota cache maintained.

Platform and Release Status

The README states it is currently in Developer preview. A universal DMG download is available for macOS; the Windows EXE has been built and is being uploaded to the v0.1.1 Release.

macOS full functionality relies on Keychain credential storage, browser OAuth opened via DSH GUI (PKCE, state verification, loopback/manual-code callbacks), and scanning desktop apps or local CLI sessions for Cursor, Antigravity, etc. Non-macOS default credential stores fail closed and do not silently fall back to insecure in-memory storage.

Installation and Enabling

The plugin runs with the current dsh process privileges. Before installation, review the repository source code and MIT license, and read SECURITY.md. Do not submit tokens or sensitive logs in issues.

The DSH CLI must be installed first, and dsh must be available. The upstream requires Node 22.19+ for 22.x, or Node 24+; the current bundle has been verified against @deepseek-ai/dsh@0.1.0-rc.6.

npm install --global @deepseek-ai/dsh
npm install --global pnpm

dsh --version
pnpm --version

web is a complete Web profile provided by DSH; do not create an empty profile with only the Dockyard bundle, as it will not launch the Web GUI.

dsh plugin --profile web add github:AITabby/dockyard-dsh
dsh web

Access at http://127.0.0.1:3080 by default. On first launch, you can check the combined configuration:

dsh web --dump-config

To pin a specific version, pin to a verified commit:

dsh plugin --profile web add github:AITabby/dockyard-dsh#<commit-sha>

Method 2: Standalone DMG for macOS

If you prefer not to manually install Node.js, pnpm, or DSH, download the macOS universal DMG (Apple Silicon and Intel) with a complete runtime included. The DMG bundles Node.js, DSH CLI, the full web profile, and the Dockyard plugin; OAuth authorization pages open in the system’s default browser. Currently, it is a locally ad-hoc signed developer preview.

Download from GitHub Releases.

Method 3: Clone and Local Installation

Use this method when you need to modify the source code:

git clone https://github.com/AITabby/dockyard-dsh.git
cd dockyard-dsh
npm install
npm test                 # Optional
npm run build            # Required if source or bundle is outdated

dsh plugin --profile web add .
dsh web

For isolated testing without affecting the default DSH home:

DSH_HOME=/tmp/dockyard-dsh-home dsh plugin --profile web add .
DSH_HOME=/tmp/dockyard-dsh-home dsh web

Typical Usage

Commands within DSH

In a running DSH profile:

/dockyard status
/dockyard scan [provider]
/dockyard add [provider] [candidateId]
/dockyard login <provider>
/dockyard refresh [provider]
/dockyard models <provider>
/dockyard policy <provider> <manual|sticky_session|round_robin|failover> [accountId]
/dockyard use <provider> <accountId>
/dockyard remove <provider> <accountId>

Adding and Importing Accounts

To add via browser OAuth: run /dockyard login <provider> and complete login on the official authorization page. To import existing local login states, first run /dockyard scan <provider>, then /dockyard add <provider>, and finally verify real-time status with /dockyard status and /dockyard models <provider>.

For Codex, Antigravity, Grok, Claude, and Cursor, “Login to Add Account” defaults to opening the official browser authorization page via DSH, without requiring the CLI to be installed locally; the CLI is only for compatibility fallback. Antigravity’s Google OAuth requires setting DOCKYARD_ANTIGRAVITY_CLIENT_ID and DOCKYARD_ANTIGRAVITY_CLIENT_SECRET in the shell launching DSH, as credentials are not bundled in the repository.

Use Cases and Considerations

Who is it for: Developers who are using or planning to use DSH for agents/web conversations and need to manage multiple official accounts and models from providers like Codex, Antigravity, Grok, Claude, and Cursor within a single interface. It is especially suitable for macOS users: Keychain, browser OAuth, and desktop session scanning are prerequisites for a complete experience.

Security boundaries: Original OAuth/tokens are not written to Git, account pool snapshots, or page states; refresh tokens are persisted in secure credential storage, and providers supporting refresh automatically refresh short-lived access tokens upon restart. Quotas, models, and plans remain unknown/null when providers do not return them.

Known limitations:

  • DSH is still in developer preview; upstream may introduce breaking changes
  • Provider CLI paths, OAuth fields, and quota interfaces may change; Dockyard retains unknown for missing fields
  • Until the Windows EXE upload and verification are complete, it is not recommended for production use on Windows
  • Antigravity browser authorization requires self-configuration of official OAuth client information

The SkillHub community directory has no official affiliation with DeepSeek or High-Flyer; it is an independent collection site within DSH’s “everything is a plugin” ecosystem.

Conclusion

Dockyard DSH consolidates multiple providers’ official OAuths, local sessions, and native requests into a single account pool and runtime within DSH, using /dockyard for login, scanning, policy, and model viewing, eliminating the need to maintain a separate proxy or redundant cache. macOS users can integrate directly via DMG or dsh plugin --profile web add; before use, refer to the README to verify platform and release status.