When will DSH support ChatGPT, Claude, and Grok consumer subscriptions (login, not API keys)?

[telemetrya2018-dotcom]

The current Models page already accepts API keys for OpenAI and Anthropic, plus Codex OAuth. That is not what I need.

I already pay for the main consumer subscriptions:

• OpenAI / ChatGPT (Plus or Pro)
• Anthropic / Claude (Pro or Max)
• xAI / Grok

I want to sign in with those accounts and use the included quota inside DeepSeek Harness, the same way Codex already uses OAuth. I do not want a second pay-per-token bill.

Questions:

1. Is first-class login for ChatGPT, Claude, and Grok subscriptions on the official roadmap?
2. If yes, what is the expected order and any public timeline?
3. If no or not soon, is the official answer “API keys / custom endpoint only”?

I am not asking for unofficial wrappers. I want the official product position.

[weijiafu14]

The ChatGPT/Codex subscription part is usable now through pi2dsh, as a native DSH model route rather than a Codex subagent.

dsh plugin --profile web add pi2dsh
# restart dsh, then run:
/login

Choose OpenAI (ChatGPT Plus/Pro). The OAuth flow is shown through the DSH question dialog, the rotating token is published into the DSH credentials service, and the account gets its own group in the normal model picker.

I ran the full path on a real DSH Web session: browser login → 7 Codex models appeared → selected GPT-5.6 Sol → the model answered the turn. Reproduction details and screenshots are under examples/subscription-login.

This does not answer the official roadmap question, but it solves the ChatGPT subscription use case today.

[weijiafu14]

Follow-up: the same ChatGPT Plus/Pro /login route now covers image generation and editing as well as normal Codex model turns.

dsh plugin --profile web add pi2dsh
dsh plugin --profile web add @crazygit/pi-codex-image-gen
# restart, then in the composer:
/login openai-codex

After login, a Codex model can call codex_generate_image; the Pi package reuses that OAuth account to call gpt-image-2, and the returned PNG is persisted through DSH attachments and rendered inline in the Web tool card. Local reference-image edits go through a DSH confirmation dialog before upload.

No separate image API key is required. Reproduction: https://github.com/weijiafu14/pi2dsh/tree/main/examples/codex-image-gen

[iimaguest]

Does this work for Supergrok? The oauth part, not the image gen part

[weijiafu14]

@iimaguest Yes — SuperGrok OAuth is now supported through the original stnly/pi-grok provider package running unmodified on DSH via pi2dsh.

dsh plugin --profile web add pi2dsh
dsh plugin --profile web add github:stnly/pi-grok

Restart DSH, then run:

/login xai-oauth

The package’s xAI device-code login is shown in DSH’s question panel, and its package-owned transport is registered as a normal DSH model route. We verified the published package in a clean DSH profile through real xAI OIDC discovery, device-code issuance/display, and cancellation.

If your SuperGrok account hits an account-specific authorization or model-call error, please paste it in the pi2dsh issues and we’ll follow it through.