DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to run DSH workers in CI or on a machine with no DSH instance running with DSH Crew

Set up the standalone fallback with a DeepSeek key so dispatch works in headless environments.

Short answer: Obtain an API key from platform.deepseek.com; then write the key to ~/.config/dsh-crew/.env as DEEPSEEK_API_KEY=sk-; install the plugin from npm: dsh plugin --profile web add @zseven-w/dsh-crew@latest. All steps.

Credentials. The DeepSeek API key is stored in a plain .env file on the machine, so restrict its file permissions and keep it out of version control.

Who it is forA DevOps engineer who wants scripted or automated coding jobs on a build server or CI runner where no DSH web instance is running.

The problemWithout a running DSH instance, the hub path is unavailable, so dispatch needs its own runtime and credentials.

The outcomeDispatch falls back to a standalone DSH runtime, and the smoke test reports which path it used and whether configuration is OK.

What you need first

  • A DeepSeek Harness (DSH) instance to install the plugin into, or a DeepSeek API key for the standalone fallback
  • npm and node available on the machine, since the install commands use them
  • Claude Code or Codex installed as the orchestrating host

Steps

  1. Obtain an API key from platform.deepseek.com
  2. Write the key to ~/.config/dsh-crew/.env as DEEPSEEK_API_KEY=sk-...
  3. Install the plugin from npm: dsh plugin --profile web add @zseven-w/dsh-crew@latest
  4. Run the smoke test: node scripts/smoke.mjs
  5. Confirm the output says smoke test passed, configuration OK and note which path was used (inferred, check the README)

Prompt for your agent

In the dsh-crew repo (ZSeven-W/dsh-crew), configure the standalone fallback with a DEEPSEEK_API_KEY in ~/.config/dsh-crew/.env and run `node scripts/smoke.mjs`. Expected output: the smoke test line that shows which path ran and whether configuration passed. Verify it reports `smoke test passed` before any scripted dispatch.

Caveat. The README says the standalone fallback needs its own key, while the hub mode uses the DSH instance's existing credentials.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for ZSeven-W/dsh-crew and "Run DSH workers in CI or on a machine with no DSH instance running"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer