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

How to review every tool call an AI coding agent made with Agent Security

Read the local audit trail and watch live tool calls to see what an agent tried and what the guard decided.

Who it is forA developer or team lead who wants a record of what an AI coding agent did in a session before merging its work.

The problemWithout a record, it is hard to tell which files an agent touched, which calls were refused, and whether a secret was involved.

The outcomeA list of allowed and denied tool calls from the session, read from the local audit file and the live tail.

What you need first

  • A machine where you can run a shell and git (the README installs with git clone and ./scripts/shell/install.sh)
  • Claude Code or Codex installed as the agent you want to guard
  • A new terminal after install, since hooks load only when a session starts
  • For the sandbox use case: Linux with bubblewrap (bwrap) installed, since the README says it is required and macOS and Windows refuse

Steps

  1. Complete the guard install with ./scripts/shell/install.sh and open a new terminal.
  2. Run an agent session in the project, such as solongate run -- claude.
  3. solongate audit
  4. solongate watch
  5. Check that each decision has a matching line in ~/.solongate/local-logs/solongate-audit.jsonl.

Prompt for your agent

Using https://github.com/solongate/agent-security, run `solongate audit` after a session with <agent> in <project-path>. Expected output: a list of tool calls with their allow or deny decisions. Verify that ~/.solongate/local-logs/solongate-audit.jsonl contains one JSON object per decision, matching what the audit view shows.

Caveat. The audit trail records decisions the guard made, so it only shows tool calls that passed through a hook in a session started after install.

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