DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to keep several remote machines open in parallel with one session each with Agentreach

Open one reach session per box and track them with reach status.

Who it is forAn engineer juggling several build boxes, staging VMs or client servers who wants a separate agent session for each one.

The problemKeeping track of which agent session belongs to which machine gets messy as the number of boxes grows.

The outcomeEach target has its own named session, and reach status lists them with their mode, file ops and working directory.

What you need first

  • Go toolchain, or a pre-built reach binary from the releases page
  • An ssh binary on your machine that already reaches the target
  • The coding agent installed on your local machine, such as Claude Code or Codex
  • Access to the target over SSH, with keys or config already set up

Steps

  1. Open a session for each target with reach build-box:/srv/app claude (inferred, check the README)
  2. Open another session with reach client-box:/srv/app codex
  3. List the active sessions with reach status
  4. Reuse a session by running another command against the same target
  5. Close each one with reach down build-box-app using the name from the status list

Prompt for your agent

Use the repo bojieli/agentreach to list the active sessions on this machine with `reach status`, using <target> as a reference. Expected output: a table with NAME, TARGET, MODE, FILEOPS and CWD for each open session. Verify that a second command against the same target reuses its session.

Caveat. Sessions are named after their target by default, so two targets with the same host name would need a chosen name from reach up --name.

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