Skip to main content

Agent Auto Approve

English · 한국어

agent-auto-approve is a Python CLI for managing tool approval hooks for Codex CLI, Claude Code, and Antigravity CLI. You can register hooks for a project or for your user account. With Codex and Claude Code, you can also apply a hook to a single new session.

Installation

The CLI requires Python 3.8 or later. Both installation methods use uv. Install uv

From PyPI

Install using the package name. PyPI package

uv tool install agent-auto-approve

From GitHub Releases

Download the wheel (.whl) from the release's Assets. Run the command below in your download directory and substitute the filename if you downloaded a different version. GitHub Releases

uv tool install ./agent_auto_approve-0.1.2-py3-none-any.whl

Check that the CLI runs after installation.

agent-auto-approve --help

Quick start

By default, install and launch apply no workspace path restriction to approval requests passed to the hook. Add --workspace-only as shown below to limit automatic approval to your workspace.

Go to the root of the project you want to set up. For a project with a .codex directory, register a hook scoped to the workspace and check the registration.

agent-auto-approve install . --workspace-only
agent-auto-approve hooks .

After registering a Codex hook, install asks the shared local app server to reload its configuration when available. Its existing chats can pick up the hook without restarting. For sessions running separately, open a new Codex chat to load the registration. Review new or changed hooks using /hooks in the CLI or Settings → Hooks in the desktop app. Codex hook trust

To try the hook in a single new Codex session, run this command from the project directory.

agent-auto-approve launch --workspace-only

launch looks for the selected agent's CLI on your PATH. On Windows, launching Claude Code requires the native claude.exe. Claude Code hooks require version 2.1.139 or later for args support. Claude Code changelog

Use --claude for Claude Code. From a project root containing .claude, register a hook scoped to the workspace and check the registration.

agent-auto-approve install --claude . --workspace-only
agent-auto-approve hooks --claude .

Claude Code watches its settings files, so a running session can pick up hook changes without restarting. To apply the hook to a single new Claude Code session, run agent-auto-approve launch --claude --workspace-only. Claude Code settings reload

Use --agy for Antigravity CLI. From a project root containing .agents, register the hook, check the registration, and then run agy. Use /hooks to see what the running session has loaded. Antigravity hooks

agent-auto-approve install --agy . --workspace-only
agent-auto-approve hooks --agy .
agy

Commands

Command Behavior
agent-auto-approve install [DIR] [--workspace-only] Registers a project hook when you supply DIR and a global hook for your user account when you omit it. The project must contain the selected agent's .codex, .claude, or .agents directory.
agent-auto-approve launch [--claude] [--workspace-only] Detects the operating system and starts a new session with the hook. Codex uses a temporary hook script and Claude Code uses a temporary settings file. The temporary file is removed when the session ends.
agent-auto-approve find [DIR] [--agy] [--claude] [--codex] Prints absolute paths to .agents, .claude, and .codex directories, one per line. Combine agent flags to select specific directory types. With no flags, it searches for all supported types.
agent-auto-approve hooks [DIR] Shows the scope, approval mode, and absolute settings file path for registered hooks.
agent-auto-approve uninstall [DIR] [--all] Removes the project hook when you supply DIR and the global hook when you omit it. --all searches recursively under DIR or under your home directory if you omit DIR.

install, hooks, and uninstall accept one of --agy, --claude, and --codex. launch accepts --claude or --codex. These commands default to Codex.

Agent Global settings file Project settings file
Codex CODEX_HOME/hooks.json, defaults to ~/.codex/hooks.json DIR/.codex/hooks.json
Claude Code CLAUDE_CONFIG_DIR/settings.json, defaults to ~/.claude/settings.json DIR/.claude/settings.local.json
Antigravity CLI ~/.gemini/config/hooks.json DIR/.agents/hooks.json

The Antigravity CLI, app, and IDE read the same hook settings files. Antigravity hook settings

find and hooks search the specified directory and its descendants. When you omit DIR, the search starts in your home directory. In that case, hooks also checks the selected agent's global configuration directory if it is set outside your home directory. The commands skip inaccessible directories.

In a terminal, the progress line shows directory... and changes to directory... found when it finds a match. In terminals that support color, only found appears in green. The command clears the progress line before printing the results.

Run agent-auto-approve --help to list commands. Add --help to a command, as in agent-auto-approve find --help, to see its arguments and options. You can also use -h.

Automatic approval scope

By default, the hook automatically approves tool approval requests it receives. Claude Code and Antigravity questions that require a user response use their usual prompt flow. With --workspace-only, the hook approves a request only when it can verify that the target path and, where applicable, the command's working directory are within the boundary below.

Setup command Workspace boundary
agent-auto-approve install --workspace-only Codex uses the session's working directory. Claude Code uses the project root where the session started. Antigravity uses the working directories supplied in the hook's workspacePaths.
agent-auto-approve install DIR --workspace-only The specified project root DIR
agent-auto-approve launch --workspace-only The directory where you ran launch

Path checks support simple POSIX touch and mkdir commands, explicit Codex filesystem permission requests, and basic Claude Code and Antigravity file tools that receive absolute paths. For Antigravity, the hook checks explicit paths for file reads, creation, edits, and directory listings. If an Antigravity command request omits the working directory (Cwd), the hook can check the target only when it is an absolute path. Requests involving paths outside the workspace or paths the hook cannot verify go through the agent's usual approval flow. For example, if the boundary is ~/work/test, touch ~/note.txt goes through the usual approval flow because it would create a file in your home directory.

Claude Code's explicit deny rules, managed hook settings, and workspace trust policies still apply. Network sandbox prompts are handled separately. A global hook and a project hook can both apply to the same session. Check the mode of each applicable registration if you need approval limited to the workspace. Claude Code hook reference

If a global hook from this tool is registered for the same agent, a project install DIR or launch shows the global settings path and approval mode and asks whether to continue. Enter y to continue. Enter n or press Enter without a response to cancel.

Uninstall

To remove a project hook, run agent-auto-approve uninstall . from the project root. To remove a global hook, run agent-auto-approve uninstall. This also works when the global settings are outside your home directory. Add --claude for Claude Code or --agy for Antigravity. The tool removes only hooks it registered.

An open session that already loaded the removed hook can continue with its normal approval flow. Codex's shared local app server can reload the removal immediately. For older registrations, uninstall leaves a compatibility script for open sessions. Close sessions that loaded an older registration before removing the CLI, since their cached hook command still uses its Python interpreter.

After removing the registered hooks, uninstall the CLI.

uv tool uninstall agent-auto-approve

Building the package

To install from source, clone the repository and run uv tool install . from the root directory containing pyproject.toml.

Run uv build from the repository root to create a wheel and a source distribution in dist/.

Contributing and reporting security issues

Metadata

Release files for agent-auto-approve 0.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for agent-auto-approve 0.1.2
File Size Uploaded Provenance Actions
agent_auto_approve-0.1.2.tar.gz 22.4 kB With provenance Details for agent_auto_approve-0.1.2.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for agent-auto-approve 0.1.2
File Interpreter ABI Platform Actions
agent_auto_approve-0.1.2-py3-none-any.whl Python 3 none any Details for agent_auto_approve-0.1.2-py3-none-any.whl

Total release size: 41.0 kB

Release files / agent_auto_approve-0.1.2.tar.gz

Download URL agent_auto_approve-0.1.2.tar.gz
Size 22.4 kB
Tags Source
SHA-256 checksum
How to use checksums
0018a5b1dd16a6c1a6dd804f6b8e8289cbe36d22d884f9c4e6c8013671c88292
BLAKE2b-256 checksum
How to use checksums
44ffcee0263f05e55889bf0ddf17ccf3c18d97a1afeff89798d8ea9ff8b38f1e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.

Transparency log

Release files / agent_auto_approve-0.1.2-py3-none-any.whl

Download URL agent_auto_approve-0.1.2-py3-none-any.whl
Size 18.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
92da09104cd0a3e913f711ec953c9157f155ba9afe0a0c0a1e7a56aa3addf8d9
BLAKE2b-256 checksum
How to use checksums
35bd683ca545c5083a1e70107e6f0f951161833c01f5f2d955810c4dbdc09742
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.

Transparency log

Security for agent-auto-approve 0.1.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for agent_auto_approve-0.1.2.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page