Skip to main content

How to use dockyard-dsh

Integrate OAuth for Codex, Antigravity, Grok, Claude, and Cursor into DSH with unified account pooling and real-time quota management.

This article is auto-derived from indexed fields (wiki / faq / compatibility_json), not freshly AI-generated.

This article is derived from the plugin's already-indexed fields (wiki / faq / compatibility_json / readme), not freshly generated by AI. Source field is noted at the end of each section.

Quick start

dockyard-dsh

— source: plugin_wiki.wiki_content

Install & verify

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

Run the command above in your DSH Web Profile. Then enable the plugin in the plugin list.

— source: plugins.install

Key points

  • Codex — 官方浏览器 OAuth、CLI fallback 和原生 Responses 请求链路。
  • Antigravity — Google 官方浏览器 OAuth、官方本机会话、实时模型目录、额度/credits 和原生 Gemini SSE 请求链路。
  • Grok — xAI 官方浏览器 OAuth、CLI fallback、实时模型目录、官方 Build credits 周期和 provider-native streaming 请求。额度读取使用官方 /billing?format=credits(转发 GetGrokCreditsConfig);若上游只返回周期,剩余值保持未知。
  • Claude — Claude 官方浏览器 OAuth(支持带 state 的手动回调地址/授权码)、CLI fallback 与原生请求适配。
  • Cursor — Cursor 官方浏览器登录轮询、CLI fallback 与原生请求适配。

— source: plugin_wiki.readme_en (fallback readme_raw)

FAQ

Does dockyard-dsh add new model APIs to DSH or add account pools to DSH?

Add account pool. It connects multiple official OAuth client sessions to the same shared runtime, requests according to account selection strategy within DSH, and will not replace the core that DSH comes with.

Which DSH profile do I install to have GUI?

Install to DSH's built-in web profile to see the account/quota interface provided by Dockyard; creating a new empty profile won't start the Web GUI.

Why does Antigravity browser authorization report missing client information?

Antigravity uses Google loopback OAuth, requiring DOCKYARD_ANTIGRAVITY_CLIENT_ID and DOCKYARD_ANTIGRAVITY_CLIENT_SECRET. These two variables are not in the repository and need to be set in the shell that starts DSH.

Can it be used on platforms other than macOS?

DSH itself is a web host and cross-platform; but credentials are stored in macOS Keychain by default. On non-macOS platforms, the default credential storage will fail closed, requiring the host DSH Credentials service to take over, otherwise tokens cannot be persisted.

Where is data saved, and is uninstallation clean?

Account strategy and account metadata are written to ~/.dockyard-dsh/state.json; OAuth tokens are written to macOS Keychain or host DSH Credentials. After uninstallation, delete state.json and the com.dockyard-dsh.credentials service in Keychain.

— source: plugin_wiki.faq_json

Compatibility

  • DSH: 0.1.0-rc.6+
  • Node: >=22.19.0 (22.x) || >=24.0.0
  • Platforms: macOS, Windows(未验证), Linux(受限,需宿主凭据服务)
  • Native modules: macOS Keychain Swift helper(/usr/bin/swift), Python3 pty 模块(Antigravity CLI fallback)

— source: plugin_wiki.compatibility_json

Pitfalls

Review the upstream repo before installing. This guide is auto-derived from indexed fields and may lag the latest release. If anything contradicts the official docs, treat the upstream source as authoritative.

— source: general rule