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

How to watch every agent project status from one control room with DSH Worktable

Install the plugin and bind one conversation to get a live card grid of working, needs-you, and done projects.

Remote script. The install command pulls a tarball from a GitHub Release and registers it in your DSH profile, which may ask for authorization and writes to ~/.dsh, so check the source URL before running it.

Who it is forA developer running several agent projects in DeepSeek Harness who keeps losing track of which one is waiting for input.

The problemAgent projects run in separate conversations, so checking whether each one is busy, blocked, or finished means opening them one by one.

The outcomeA pinned control-room card shows each bound project as working, needs you, or done, with a short cleaned message preview.

What you need first

  • A working DeepSeek Harness (dsh) install with the web profile, or the Desktop app on Windows for the tested Desktop scope
  • Node.js and npm if you plan to clone the repo and build from source
  • A browser where you can keep the same origin, since projects and layouts are stored in browser localStorage

Steps

  1. Install the plugin with dsh plugin --profile web add "https://github.com/Aisland-SJL/dsh-worktable/releases/latest/download/dsh-worktable.tgz"
  2. If the dsh command is missing, run npx @deepseek-ai/dsh in its place with the same arguments.
  3. Restart the DSH web process and refresh the GUI.
  4. Click the pinned 🖥️ control-room card, then bind one conversation by joining an existing one or creating a new one.
  5. Open the sidebar ＋ for each agent project, choose a layout preset, and set its project folder and bound conversation so it appears on the card grid.

Prompt for your agent

Use the repo Aisland-SJL/dsh-worktable to set up the control room in DeepSeek Harness web at <harness-url>. Report the card grid state for each bound project (working, needs you, or done). Verify that projects with no bound conversation show as idle.

Caveat. The control room only monitors projects that are bound to a conversation, and all project state stays in the browser's localStorage and IndexedDB rather than syncing across machines.

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