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

How to coordinate several DSH session windows as one team with DSH Desktop

Route tasks between DSH session windows and let one window act as team lead.

Who it is forA user running several DSH sessions in parallel who wants them to hand work to each other and report results back.

The problemWork split across separate DSH windows has no shared task flow, so the user must copy results and track dependencies by hand.

The outcomeA role-based group of session windows where messages and task results appear as real DSH messages in the target window, and the lead assigns tasks and dependencies.

What you need first

  • A model credential configured in DSH settings (the README says the project does not write API keys into its files)
  • A Windows x64, macOS Apple Silicon, or Linux x64 machine, or Node.js 24 or later if you run from source
  • A Git repository as the working directory if you want Git worktrees

Steps

  1. Open the plugin marketplace under Settings and confirm that @vibeinging/dsh-session-teams is installed, since it ships by default in new profiles.
  2. In one session, tell the window to hand a task to another window by its name, and check that the message appears in the target window.
  3. Ask one window to act as team lead, create a group of role-based windows, and assign tasks and dependencies in plain language.
  4. Review the results members report back as messages, then adjust tasks in the lead window.
  5. If you do not need the feature, run dsh plugin --profile web remove @vibeinging/dsh-session-teams.

Prompt for your agent

In the vibeinging/dsh-desktop setup, ask the session window <placeholder> to hand a short task to another named window and report whether the message appeared in the target window as a real DSH message. Verify that the team state is stored through the official Session API in the current profile and that no external network connection is made, as the README states.

Caveat. The README describes the team behavior but does not list limits on group size or task count, so test with a small group first.

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