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

How to hand a code review to another DSCODE session with Dscode

Send a steering request to a second session on the same machine and read its reply back.

Who it is forA developer running one DSCODE session on a feature who wants a second session to check a change without losing context.

The problemAsking the same agent to review its own work tends to repeat its assumptions, and switching terminals loses the thread.

The outcomeA second session reviews the named file, answers in its own transcript, and the reply is readable from the first terminal.

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. 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 for your agent

Using the repo qiz029/dscode, list sessions with `dscode sessions`, send the review request for <file path> 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.

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