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

How to rename subscriptions and models for a shared setup with DSH Plugin Subscriptions

Give providers and models clearer display names in the picker without changing their IDs or routing.

Who it is forA DSH user or team lead who shares a setup and wants names like Work Codex or Fast draft in the model picker.

The problemDefault provider and model names are hard to tell apart when several accounts or models are in use.

The outcomeDisplay names appear in the model picker and group titles, and the underlying provider and model IDs stay the same.

What you need first

  • DeepSeek Harness (DSH) installed, with a web UI you can open
  • An active ChatGPT Plus or Pro, Claude Pro or Max, or X Premium subscription, or a GitHub Copilot or Google Antigravity account, for the provider you want
  • Permission to install the plugin into DSH, following the Install section of the README

Steps

  1. Install the plugin into DSH by following the Install section of the README.
  2. Open Settings, then Subscriptions, then Manage, and enter a subscription display name of up to 80 characters.
  3. To rename a model, open Edit model list and change its display name, then click Save.
  4. To restore a name, clear it or choose Reset to default, then save.
  5. Open the session model picker and confirm the new names appear.

Prompt for your agent

Using the dsh-plugin-subscriptions repo, set the display name of the <provider> subscription to <name> in DSH Settings. Expected output: the new name shown in the session model picker. Verify that the provider and model IDs are unchanged.

Caveat. Display names only change presentation, so the README says routing and reasoning settings are unaffected, and names are capped at 80 single-line characters.

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