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

How to run the agent on a server and drive it from a laptop with Dscode

Serve the DSCODE runtime from a server and attach a local terminal to it over a token.

Credentials. The token authenticates the connection but traffic is not encrypted, so only use it over a VPN, LAN or SSH tunnel.

Who it is forA developer whose code, tools and credentials live on a remote server and who wants a local terminal to control the agent there.

The problemRunning the agent on a laptop means the code and tools are not where the work is, and a dropped connection can end the session.

The outcomeA local terminal attached to a server runtime, with tools and files staying on the server.

What you need first

  • A macOS or Linux machine (64-bit glibc Linux is supported in 0.7.46)
  • Install DSCODE using the curl installer in the README quick start
  • A model provider key stored through the `/provider` command in the TUI
  • A Git repository to review, for the diff-based use cases

Steps

  1. On the server, run dscode server --port 8080.
  2. On your machine, run dscode config --runtime host:8080 --token … --alias devbox --set-default, replacing the token and host with your values.
  3. Start the terminal with dscode, or attach to the alias with dscode runtime devbox.
  4. Keep the connection inside a VPN, LAN or SSH tunnel, because the README says it is token-authenticated but not encrypted.

Prompt for your agent

Using the repo qiz029/dscode, start the runtime on <server host> with `dscode server --port 8080`, attach with `dscode runtime devbox`, and report whether the terminal connects. Verify that files you open are read from the server, not from the local machine.

Caveat. The README says the remote connection is not encrypted, so it should not be exposed directly to the public internet.

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