DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to use Command Code models in the dsh terminal UI with DSH Commandcode Provider

Add the plugin to the dsh-tui profile and select Command Code models from /model.

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.

Who it is forA developer who works in the dsh terminal UI and wants Command Code models there.

The problemThe web install does not reach the terminal, because each dsh profile owns its own plugin list.

The outcomeThe terminal session lists commandcode models and runs requests with a chosen Command Code model.

What you need first

  • A Command Code account with an API key or subscription
  • A dsh profile on 0.2.0-rc.2 or 0.2.1-rc.2
  • Node.js 22+ if you use the official command-code CLI to sign in

Steps

  1. Run dsh plugin --profile dsh-tui add @mars-sea/[email protected] (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 for your agent

Add @mars-sea/[email protected] 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.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page