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

How to review agent changes per file and open a PR with Agentbox

Check each diff the agent made, then commit, push, and open a PR or MR from the browser.

Credentials. The HTTPS token, SSH key, or OAuth grant you connect lets the workspace push to your remote repository.

Who it is forA developer who lets Codex CLI or Claude Code edit a Git repository and wants to review every change before it leaves the server.

The problemAgent edits land in the working tree, and it is easy to commit or push changes you have not read.

The outcomeYou review per-file diffs in the workspace, commit the ones you accept, and open a PR or MR from the same place.

What you need first

  • A Linux server (x86_64 or arm64) with systemd and a local Docker Engine
  • A Claude or Codex subscription, API key, or compatible relay account
  • A browser on your laptop, desktop, or phone
  • Optional: a Git repository and HTTPS token, SSH key, or GitHub or GitLab OAuth for pushing and opening PRs or MRs

Steps

  1. Create a workspace from your Git repository and select a Codex or Claude account.
  2. Describe the change in Chat and let the agent edit files.
  3. Open Changes and review the diff for each file.
  4. Configure a Git connection with an HTTPS token, SSH, or GitHub or GitLab OAuth.
  5. Commit the accepted changes, preview the push, then push and open the PR or MR.

Prompt for your agent

Using the agentbox repo at github.com/devilcoolyue/agentbox, run a workspace on <server-host> against the repository <repo-url>. Ask the agent to make the change <task>, then list every changed file and its diff summary before any commit. Verify that nothing is pushed until the diffs are approved.

Caveat. The README describes the diff and PR flow but does not say how the agent is prevented from editing files before you review them, so review the Changes panel before you commit.

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