# AI use cases for DSH Commandcode Provider (Mars-Sea/dsh-commandcode-provider) Repo: [Mars-Sea/dsh-commandcode-provider](https://github.com/Mars-Sea/dsh-commandcode-provider) | Use cases: 5 | Page: https://dedupedai.com/use-cases/mars-sea-dsh-commandcode-provider/ A DeepSeek Harness provider plugin that adds Command Code model access, a live model catalog, and a settings page to dsh. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Run Command Code models in the dsh web app: https://dedupedai.com/use-cases/mars-sea-dsh-commandcode-provider/use-command-code-models-in-dsh-web/ - Use Command Code models in the dsh terminal UI: https://dedupedai.com/use-cases/mars-sea-dsh-commandcode-provider/use-command-code-models-in-dsh-terminal/ - Keep dsh sessions running across several Command Code accounts: https://dedupedai.com/use-cases/mars-sea-dsh-commandcode-provider/rotate-command-code-accounts-when-limits-hit/ - Compare token cost and response speed from past dsh sessions: https://dedupedai.com/use-cases/mars-sea-dsh-commandcode-provider/compare-model-cost-and-speed-from-sessions/ - Watch Command Code 5-hour and weekly limits in the sidebar: https://dedupedai.com/use-cases/mars-sea-dsh-commandcode-provider/watch-command-code-quota-in-sidebar/ ## How to run Command Code models in the dsh web app with DSH Commandcode Provider Repo: [Mars-Sea/dsh-commandcode-provider](https://github.com/Mars-Sea/dsh-commandcode-provider) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Install the plugin, add your key, and pick Command Code models in the web model picker. **Who it is for:** A dsh web user with a Command Code account who wants those models in the normal chat picker. **The problem:** Command Code models are not in dsh by default, and the key setup is easy to get wrong. **The outcome:** Command Code models appear under commandcode in the picker, and messages sent with them get answers. ### Steps 1. (Optional) Run `npm i -g command-code@latest`, then run `cmd login` to get a key through the official CLI. 2. Run `dsh plugin --profile web add @mars-sea/dsh-commandcode-provider@latest`. 3. Restart the web app. 4. Open Settings, then Command Code, and paste your key or click Sign in to Command Code. 5. Open Settings, then Models to confirm the Command Code card, then pick a model your plan includes. ### Prompt to paste into your agent ```text Install the Mars-Sea/dsh-commandcode-provider plugin into the dsh profile and confirm the commandcode provider appears in the model picker. Expected output: a list of commandcode models in the picker. Verify that a test message sent with one included model returns a reply. ``` ### Caveat You need your own Command Code account, and the in-browser sign-in only works when the Host and your browser are on the same machine. Risk, credentials: The API key and the CLI login file give access to your Command Code account, so keep them out of shared profiles and logs. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/mars-sea-dsh-commandcode-provider/use-command-code-models-in-dsh-web/ ## How to use Command Code models in the dsh terminal UI with DSH Commandcode Provider Repo: [Mars-Sea/dsh-commandcode-provider](https://github.com/Mars-Sea/dsh-commandcode-provider) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Add the plugin to the dsh-tui profile and select Command Code models from /model. **Who it is for:** A developer who works in the dsh terminal UI and wants Command Code models there. **The problem:** The web install does not reach the terminal, because each dsh profile owns its own plugin list. **The outcome:** The terminal session lists commandcode models and runs requests with a chosen Command Code model. ### Steps 1. Run `dsh plugin --profile dsh-tui add @mars-sea/dsh-commandcode-provider@0.11.15` (pin the exact version as the README advises). 2. Open `/settings`, then Command Code, and enter your API key. 3. Choose the models to show by checking them on the same page. 4. Run `/model commandcode/deepseek/deepseek-v4.1-flash` or pick a commandcode model from the selector. ### Prompt to paste into your agent ```text Add @mars-sea/dsh-commandcode-provider@0.11.15 to the dsh-tui profile of dsh and confirm /model lists commandcode models. Expected output: a commandcode entry with plan and context annotations in /model. Verify that /commandcode opens the usage dashboard. ``` ### Caveat The README warns that a bare package name or @latest can resolve to an older build for 24 hours after a release, so pin the exact version. Risk, credentials: The terminal key field is write-only and goes to the credential store, but anyone with access to your terminal session can still use the account. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/mars-sea-dsh-commandcode-provider/use-command-code-models-in-dsh-terminal/ ## How to keep dsh sessions running across several Command Code accounts with DSH Commandcode Provider Repo: [Mars-Sea/dsh-commandcode-provider](https://github.com/Mars-Sea/dsh-commandcode-provider) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README Add more than one account so requests move to the next one when a usage limit is hit. **Who it is for:** A heavy dsh user with several Command Code accounts who keeps hitting the usage limit on one of them. **The problem:** Work stops when one account reaches its usage limit. **The outcome:** Requests switch to the next account automatically, and the quota panel shows which account is serving. ### Steps 1. Open Settings, then Command Code, and add the key for each account in the account list. 2. Confirm each account shows its key status and sign-in state. 3. Turn on the quota card under Settings, then Command Code, then Integrations & display if you want to watch limits. 4. Send normal requests and let rotation switch accounts when one hits its limit. ### Prompt to paste into your agent ```text Configure the Mars-Sea/dsh-commandcode-provider account list in dsh with the keys for accounts and confirm the active account in the settings page. Expected output: each account listed with its key status. Verify that a request continues after the first account is at its limit. ``` ### Caveat Rotation only switches accounts after a usage limit is hit, so it does not balance load across accounts ahead of time. Risk, account pooling: Command Code's terms apply to each account, so check whether pooling several accounts is allowed before you rely on rotation. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/mars-sea-dsh-commandcode-provider/rotate-command-code-accounts-when-limits-hit/ ## How to compare token cost and response speed from past dsh sessions with DSH Commandcode Provider Repo: [Mars-Sea/dsh-commandcode-provider](https://github.com/Mars-Sea/dsh-commandcode-provider) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Open Model analysis to see tokens, estimated cost, timing, and retries by session or date range. **Who it is for:** A dsh user who wants to check what recent work cost and how fast each model responded before choosing one. **The problem:** Token use, cost, and failures are hard to see across many sessions and models. **The outcome:** A view of tokens, estimated cost, response timing, and failures and retries for the chosen sessions or date range. ### Steps 1. Install the plugin into your profile as in the web install steps. 2. Open Settings, then Command Code, then Model analysis. 3. Choose recent sessions or a date range. 4. Read tokens, estimated cost, response timing, and failures and retries, and check the notes on missing data and scan limits. ### Prompt to paste into your agent ```text Use the Model analysis page of the Mars-Sea/dsh-commandcode-provider plugin to summarize tokens, estimated cost, and response timing for the last days. Expected output: a short table per model with the limits and missing data noted. Verify that the estimates are labeled as estimates from current prices, not invoices. ``` ### Caveat Estimates use current prices, extrapolation applies only to complete date ranges, and the results are not invoices. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/mars-sea-dsh-commandcode-provider/compare-model-cost-and-speed-from-sessions/ ## How to watch Command Code 5-hour and weekly limits in the sidebar with DSH Commandcode Provider Repo: [Mars-Sea/dsh-commandcode-provider](https://github.com/Mars-Sea/dsh-commandcode-provider) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README Turn on the quota card to see your plan and both usage windows next to Settings. **Who it is for:** A dsh user on a Command Code plan who wants to see remaining usage before a long task. **The problem:** Usage windows reset on a schedule, and it is easy to hit a limit without warning. **The outcome:** A sidebar card shows the serving account's plan, the 5-hour and weekly windows, and the reset times. ### Steps 1. Install the plugin into your profile and restart the web app. 2. Open Settings, then Command Code, then Integrations & display. 3. Turn on Show the quota card in the sidebar and save. 4. Click the card to open the dashboard with both windows and the reset times. ### Prompt to paste into your agent ```text Enable the quota card for the Mars-Sea/dsh-commandcode-provider plugin in the dsh profile and confirm the sidebar card appears above Settings. Expected output: the plan name and the 5-hour and weekly progress bars. Verify that the card disappears again when the switch is turned off. ``` ### Caveat The card is off by default and runs no background usage poll while hidden, so it only reflects the account currently serving requests. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/mars-sea-dsh-commandcode-provider/watch-command-code-quota-in-sidebar/