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

How to continue a DSH session from a phone or browser with DSH Desktop

Enable remote access on your computer and keep the same session open from Remote Web or Android.

Credentials. Sign-in, device directory, signaling, and relay run on a third-party service, and device keys and credentials are stored in DSH_HOME, so review the remote notes before you enable it.

Who it is forA user who starts work on a desktop and wants to answer prompts or send images from a phone while away from the computer.

The problemA session that needs input stalls when the user leaves the desk.

The outcomeThe same workspace and session open on a phone or another desktop, where the user can continue chat, send images, and handle permission requests.

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 Remote in the sidebar and sign in.
  2. Enable remote access for the current computer.
  3. On your phone, open Remote Web at https://dsh.r2049.cn/app or the Android App, and open the same workspace and session.
  4. Continue the conversation, send images, or respond to permission requests from that device.
  5. If you do not need remote access, run dsh plugin --profile web remove ds-harness-remote.

Prompt for your agent

For the vibeinging/dsh-desktop project, confirm that the ds-harness-remote bundle is installed in <profile> and report whether remote access is enabled for the current computer. Verify that the Host opens only outbound connections, as the README states, and that no public listening port is exposed.

Caveat. The README says there is no supported self-hosted server, and an independent security review and real two-machine cross-network testing are not complete.

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