Back to directory

dsh-llm-github-copilot

In a curated listMaintenance: Active

lujianjun19/dsh-llm-github-copilot

Sign in to GitHub Copilot from DSH and use subscription models through its built-in provider.

View on GitHub
$ dsh plugin --profile web add @lujianjun19/dsh-llm-github-copilot -w

15

stars

7

forks

JavaScript

Language

MIT

License

2026-08-17

Created

2026-11-11

Last push

MIT-licensed native DSH plugin that signs you in to GitHub Copilot with the device flow and hands the credential to the Harness's built-in `github-copilot` provider.

DSH integration

Native runtime

Author-claimed

Safety audit

Unaudited

Last verified

2026-11-21

License

MIT

01What can it help you accomplish?

  • Sign in to a GitHub Copilot subscription from inside DeepSeek Harness and chat with its models

    A stored Copilot credential that the built-in `github-copilot` provider consumes, so chat requests run against the subscription with no pasted API key or custom endpoint

    DSH users who already pay for GitHub Copilot and want those models in the Harness model selector

  • Inspect or reset the Copilot credential without leaving the DSH chat box

    `/copilot-login`, `/copilot-status` and `/copilot-logout` commands that start sign-in, report whether a token is stored, and drop the local grant plus the writable token reference

    Developers who would rather check or reset a Copilot sign-in from the chat prompt than from the settings UI

  • Reuse an existing long-lived GitHub OAuth token instead of walking through the device flow

    The plugin reads the token from the environment variable named by `oauthTokenEnv`, with the existing grant taking precedence and no extra account or provider created

    Teams that provision GitHub credentials from CI or an external secret store and cannot run an interactive browser sign-in

02How to install into DeepSeek Harness

Prerequisites

  • DeepSeek Harness `0.2.2-rc.1` — the current development baseline; the user guide has a compatibility section for older supported releases
  • A GitHub account with Copilot access, plus Node.js ≥ 24 and pnpm ≥ 9 on `PATH`
  • The default Web profile, or a custom composition that includes `@deepseek-ai/dsh-llm-pi-ai` and `dsh-credentials-local`

Installation steps

  1. 01

    Install from npm into the Web profile: `dsh plugin --profile web add @lujianjun19/dsh-llm-github-copilot -w` (to update an existing install: `dsh plugin --profile web update @lujianjun19/dsh-llm-github-copilot --latest -w`)

    $ dsh plugin --profile web add @lujianjun19/dsh-llm-github-copilot -w

  2. 02

    Restart `dsh web` and hard-refresh the browser, then confirm the version at the bottom of Settings → GitHub Copilot

    $ dsh web

  3. 03

    Open Settings → GitHub Copilot → Sign in, open the displayed GitHub URL, enter the device code, and authorize the GitHub App (VS Code) — the plugin saves the token automatically

  4. 04

    In Settings → Models, add the built-in `github-copilot` provider if it is absent, save, choose a model in the chat model selector and send a request

Verify the integration

  • Confirm the plugin version at the bottom of Settings → GitHub Copilot after the restart
  • Run `/copilot-status` in chat to check whether a token is stored — it does not prove that a live request succeeds

03DSH integration and capability boundaries

DSH integrationNative runtime

Native DSH plugin installed with `dsh plugin --profile web add`: it adds a device-flow GitHub Copilot sign-in page plus the `/copilot-login` / `/copilot-status` / `/copilot-logout` chat commands, and hands the resulting credential to the Harness's built-in `github-copilot` provider

  • Device-flow GitHub Copilot sign-in

    a GitHub account with Copilot access and the device code shown in Settings → GitHub Copilot→the Copilot OAuth token saved into DSH's local credential store

    opens a GitHub authorization page in the browserwrites the Copilot grant into DSH's local credential store
  • Credential-only wiring for the built-in `github-copilot` provider

    the stored Copilot grant→the built-in `github-copilot` provider in Settings → Models can serve chat requests with no custom endpoint or pasted API key

  • Copilot credential chat commands

    `/copilot-login`, `/copilot-status` or `/copilot-logout` typed into the DSH chat→sign-in started, token presence reported, or the local grant removed

    `/copilot-logout` deletes the local grant and the writable token reference
  • `oauthTokenEnv` credential reference override

    a `cordis.patch.yml` override of the installed `llm-github-copilot` entry naming another environment variable→the plugin reads the Copilot token from that variable; the consuming grant stays at `llm-pi-ai/github-copilot` and no extra account or provider is created

    reads the Copilot token from the environment variable you name

04Who is it for? When not to use it?

Good for

  • DSH users who already pay for GitHub Copilot and want those models in the Harness model selector
  • Developers who would rather check or reset a Copilot sign-in from the chat prompt than from the settings UI
  • Teams that provision GitHub credentials from CI or an external secret store and cannot run an interactive browser sign-in

Not for

  • Built against Harness `0.2.2-rc.1`, the current development baseline; older supported releases are documented in the user guide's compatibility section rather than guaranteed to work unchanged.
  • Requires Node.js ≥ 24 and pnpm ≥ 9 on `PATH`, plus either the default Web profile or a custom composition that includes `@deepseek-ai/dsh-llm-pi-ai` and `dsh-credentials-local`.
  • Signing in does not add the provider configuration, and a model appearing in the selector is not proof of account access — availability still depends on the Harness catalog and your account/organization policies.

05Compatibility, maintenance and safety notes

  • Built against Harness `0.2.2-rc.1`, the current development baseline; older supported releases are documented in the user guide's compatibility section rather than guaranteed to work unchanged.
  • Requires Node.js ≥ 24 and pnpm ≥ 9 on `PATH`, plus either the default Web profile or a custom composition that includes `@deepseek-ai/dsh-llm-pi-ai` and `dsh-credentials-local`.
  • Signing in does not add the provider configuration, and a model appearing in the selector is not proof of account access — availability still depends on the Harness catalog and your account/organization policies.
  • Short-lived Copilot API tokens are not suitable and an arbitrary PAT may not carry Copilot access; sign-out does not revoke GitHub authorization or remove model configuration, so a token injected from outside has to be deleted from the environment or `.env` by hand.
2026-08-172026-11-11v0.4.13

MIT · actively maintained (latest release v0.4.13, 2026-11-11)

06Frequently asked questions

How do I install this plugin into DeepSeek Harness?

Run `dsh plugin --profile web add @lujianjun19/dsh-llm-github-copilot -w`, then restart `dsh web` and hard-refresh the browser. The bundle is registered automatically, so do not add a second plugin `insert` to the profile patch. Update later with `dsh plugin --profile web update @lujianjun19/dsh-llm-github-copilot --latest -w`.

Do I need a Copilot API key or a custom endpoint?

No. The device-flow sign-in stores the token, and the built-in `github-copilot` provider consumes it — no custom endpoint and no pasted API key. If the provider is missing from Settings → Models, add it once, save, pick a model in the chat model selector and send a request.

Which Harness version and environment does it expect?

Harness `0.2.2-rc.1` is the current development baseline (older releases are covered in the user guide's compatibility section), with Node.js ≥ 24 and pnpm ≥ 9 on `PATH`. You also need the default Web profile, or a custom composition that includes `@deepseek-ai/dsh-llm-pi-ai` and `dsh-credentials-local`.

How do I check or clear the stored credential from inside DSH?

Type `/copilot-status` to see whether a token is stored — it does not prove a live request succeeds — and `/copilot-logout` to remove the local grant and writable token reference. Sign-out does not revoke GitHub authorization or delete model configuration; if a token from an external source remains, remove it from the environment or `.env`, restart DSH and sign out again.

Can I reuse an existing GitHub OAuth token instead of signing in?

Yes: export `GITHUB_COPILOT_OAUTH_TOKEN` and start `dsh web`; an existing grant takes precedence. Use a long-lived GitHub OAuth token — an arbitrary PAT may not have Copilot access and short-lived Copilot API tokens are not suitable. The only plugin option, `oauthTokenEnv`, renames that credential reference in `cordis.patch.yml` and does not create another account or provider.

08Data and sources

  • Author-claimedgithub.com3462d5f7c25f…

    GitHub Copilot sign-in for [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness): a device-flow login page…

  • Author-claimedgithub.com3462d5f7c25f…

    dsh plugin --profile web add @lujianjun19/dsh-llm-github-copilot -w

  • Author-claimedgithub.com3462d5f7c25f…

    This plugin **only supplies credentials**; the Harness's built-in `github-copilot` route owns models, token refresh, ima…

  • Author-claimedgithub.com3462d5f7c25f…

    The bundle is registered automatically; do not add a second plugin `insert` to the profile patch.

This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-11-21. Found an error? Submit a correction.

🏆

Best DeepSeek Harness Plugins

Twelve plugins worth installing first — picked from the whole catalog, across every category.

DSH Plugins is an independent community directory of DeepSeek Harness plugins. Not affiliated with or endorsed by DeepSeek. Third-party plugins are not security-audited — review the source before installing.

New DeepSeek Harness plugins, weekly. No spam.