# AI use cases for Dscode (qiz029/dscode) Repo: [qiz029/dscode](https://github.com/qiz029/dscode) | Use cases: 4 | Page: https://dedupedai.com/use-cases/qiz029-dscode/ DSCODE is a terminal coding agent for macOS and Linux, built on DeepSeek Harness, with a persistent shell, sessions that other sessions can message, auto approval and session telemetry. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Review a Git diff in a script or CI job: https://dedupedai.com/use-cases/qiz029-dscode/run-dscode-in-ci-on-git-diffs/ - Hand a code review to another DSCODE session: https://dedupedai.com/use-cases/qiz029-dscode/hand-a-review-to-another-local-session/ - Get an independent review before committing a change: https://dedupedai.com/use-cases/qiz029-dscode/review-changes-before-committing/ - Run the agent on a server and drive it from a laptop: https://dedupedai.com/use-cases/qiz029-dscode/run-dscode-runtime-on-a-remote-server/ ## How to review a Git diff in a script or CI job with Dscode Repo: [qiz029/dscode](https://github.com/qiz029/dscode) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Pipe a diff into a non-interactive DSCODE turn and get the reply on stdout with a meaningful exit code. **Who it is for:** A developer or CI maintainer who wants an automatic code review step in a pipeline without opening the TUI. **The problem:** Reviews done by hand do not run on every change, and an agent in a terminal is hard to call from a script. **The outcome:** A review reply printed to stdout that a pipeline can save or check, with the exit code reflecting the turn. ### Steps 1. Install DSCODE on the machine or CI runner using the curl installer in the README quick start. 2. Open `dscode` once and run `/provider` to store your model provider key. 3. From the repository folder, run `git diff | dscode exec "review this"`. (inferred, check the README) 4. Read the reply on stdout; tool activity and the session id appear on stderr. 5. Add `--json` for structured output, or `--resume` to continue an earlier session, when the script needs it. ### Prompt to paste into your agent ```text Using the repo qiz029/dscode, run `git diff | dscode exec "review this"` inside and return the reply and the exit code. Verify that the exit code is 0 and that the reply text was written to stdout, not stderr. ``` ### Caveat The README describes `exec` and `--resume` only in outline, so confirm exact flag behaviour with `dscode --help` before relying on it in production. Risk, credentials: The provider key is stored by DSCODE, so keep CI secrets scoped and do not print them in job logs. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/qiz029-dscode/run-dscode-in-ci-on-git-diffs/ ## How to hand a code review to another DSCODE session with Dscode Repo: [qiz029/dscode](https://github.com/qiz029/dscode) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Send a steering request to a second session on the same machine and read its reply back. **Who it is for:** A developer running one DSCODE session on a feature who wants a second session to check a change without losing context. **The problem:** Asking the same agent to review its own work tends to repeat its assumptions, and switching terminals loses the thread. **The outcome:** A second session reviews the named file, answers in its own transcript, and the reply is readable from the first terminal. ### Steps 1. List the sessions on this machine with `dscode sessions`. 2. Send the task with `dscode send --steer "review the change in parser.ts and reply"`. (inferred, check the README) 3. Follow progress with `dscode watch` (arguments: check `dscode --help`, inferred). (inferred, check the README) 4. Read the answer with `dscode read` (arguments: check `dscode --help`, inferred). (inferred, check the README) ### Prompt to paste into your agent ```text Using the repo qiz029/dscode, list sessions with `dscode sessions`, send the review request for with `dscode send --steer`, and return the reply from `dscode read`. Verify that the reply names the file you asked about. ``` ### Caveat The README gives the session command names but not their full arguments, so check the session-bridge documentation before scripting them. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/qiz029-dscode/hand-a-review-to-another-local-session/ ## How to get an independent review before committing a change with Dscode Repo: [qiz029/dscode](https://github.com/qiz029/dscode) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Run the separate reviewer on staged work, a branch or a path, and check what it cost. **Who it is for:** A developer about to commit an agent-written change who wants a second, read-only model to check it first. **The problem:** Agent edits can contain mistakes that the author model did not catch, and approvals are easy to give without reading them. **The outcome:** A list of concrete findings from a read-only reviewer, plus a usage summary for the review. ### Steps 1. Start `dscode` in the repository folder. 2. Run `/review` to review the staging area, or give it a base branch, a commit or a path. 3. Set approvals with `/permission auto-review` if you want an independent reviewer to decide them. 4. Check what the review allowed and cost with `/review-usage`. ### Prompt to paste into your agent ```text Using the repo qiz029/dscode, start DSCODE in , run `/review` on the staged changes, and return the findings. Verify that each finding names a file and a concrete problem. ``` ### Caveat The reviewer is a separate model, so its findings still need a human check before a commit. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/qiz029-dscode/review-changes-before-committing/ ## How to run the agent on a server and drive it from a laptop with Dscode Repo: [qiz029/dscode](https://github.com/qiz029/dscode) | Difficulty: Advanced | Time: 60 minutes | Basis: From the README Serve the DSCODE runtime from a server and attach a local terminal to it over a token. **Who it is for:** A developer whose code, tools and credentials live on a remote server and who wants a local terminal to control the agent there. **The problem:** Running 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 outcome:** A local terminal attached to a server runtime, with tools and files staying on the server. ### 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 to paste into your agent ```text Using the repo qiz029/dscode, start the runtime on 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. Risk, credentials: The token authenticates the connection but traffic is not encrypted, so only use it over a VPN, LAN or SSH tunnel. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/qiz029-dscode/run-dscode-runtime-on-a-remote-server/