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

How to audit what an agent ran or changed on a server with Agentreach

Use the reach log to review every command and write an agent made on a target.

Who it is forAn ops engineer who let an agent work on a server and needs to confirm exactly which commands ran and which files changed.

The problemAfter an agent session on a remote machine, it is hard to tell which commands ran and which files were rewritten.

The outcomeA timestamped list of commands, exit codes and file writes that reach made on the target.

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. Start or continue a session with reach build-box claude
  2. Let the agent work on the target
  3. Review the record with reach log
  4. Compare any listed write against the file on the target
  5. Close the session with reach down when finished

Prompt for your agent

Use the repo bojieli/agentreach to review the actions taken on <target> during an agent session. Run `reach log` and report each exec and write entry with its status. Expected output: a table with WHEN, ACTION, STATUS and DETAIL columns that matches what the agent did.

Caveat. The README describes reach log as a record of what reach ran and changed, so commands run outside reach are not part of this audit.

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