DEDUPEDAccount pooling. Command Code's terms apply to each account, so check whether pooling several accounts is allowed before you rely on rotation.
Who it is forA heavy dsh user with several Command Code accounts who keeps hitting the usage limit on one of them.
The problemWork stops when one account reaches its usage limit.
The outcomeRequests switch to the next account automatically, and the quota panel shows which account is serving.
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
- Open Settings, then Command Code, and add the key for each account in the account list.
- Confirm each account shows its key status and sign-in state.
- Turn on the quota card under Settings, then Command Code, then Integrations & display if you want to watch limits.
- Send normal requests and let rotation switch accounts when one hits its limit.
Prompt for your agent
Configure the Mars-Sea/dsh-commandcode-provider account list in dsh with the keys for <number> 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.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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