# Termaxa A cooperative gate that previews, evaluates, and records shell commands run by AI coding agents. - Findings24: - Website: - Pricing: Freemium - Categories: AI Agent Infrastructure, AI Developer Tools ## What is Termaxa? Termaxa is a developer tool that acts as a cooperative gate for shell commands and selected file operations run by AI coding agents. It previews the likely consequence of an action, applies a policy, and returns an allow, ask, or deny decision before execution. Its examples include affected files, database rows, and commits that a force push would remove. The product is intended to work inside agent workflows rather than beside them. It provides hooks for Claude Code, Codex, Cursor, and Copilot, and records decisions in a location outside the project repository. For selected destructive operations, it can create backups before the action runs. ## What can Termaxa do? ### Impact previews Shows the expected consequence of a command, including affected files, PostgreSQL rows and dependent tables, or commits a Git force push would lose. ### Policy-based decisions Evaluates commands against project rules and returns an allow, ask, or deny decision. The default policy blocks examples such as recursive force deletion. ### Backups before selected operations Can copy affected paths to \`.termaxa/backups\` before deletion and use database dumps before PostgreSQL changes, providing rollback support for supported workflows. ### Agent and native-tool hooks Integrates with Claude Code, Codex, Cursor, and Copilot. Supported event handling includes shell commands and, in relevant integrations, Write, Edit, Delete, and patch file headers. ### Receipts and replay Keeps decision records outside the repository in \`~/.termaxa\` and provides \`termaxa replay\` to evaluate commands agents have already run. ## Use Cases ### Review destructive file commands Use the gate to inspect commands such as \`rm -rf\` before execution. The decision can include the target path, file count, and the reason a policy blocked the operation. ### Protect Git history Preview what a force push would remove before sending it to a remote, rather than relying only on the command text or a generic approval prompt. ### Stage database changes Run a PostgreSQL change through a workflow that previews affected rows and dependent tables and creates a \`pg\_dump\` before the operation when supported. ### Inspect infrastructure changes Place Termaxa in front of Terraform apply workflows so the plan and policy decision are available before infrastructure changes are executed. ## Frequently Asked Questions ### Which agent tools does Termaxa integrate with? The site lists hooks for Claude Code, Codex, Cursor, and Copilot. Integration behavior differs: for example, Codex is documented as honoring deny decisions through its hook, while Claude Code can also be reached through a configured shell wrapper. ### Can Termaxa inspect commands without running them? Yes. \`termaxa check "\"\` reads a command and returns a decision, reason, and contextual impact without executing it. ### Where are Termaxa’s records stored? The site says state was moved out of the repository to \`~/.termaxa\`, so a repository reset cannot remove the audit records. The records contain the gate’s decisions and related context. ### Does Termaxa automatically allow every command? No. Commands are evaluated against policy and may be allowed, asked about, or denied. The default policy example denies \`rm -rf ./scratch\` because it detects the recursive force-delete flags. ## Quick Facts - **Category**: Developer Tool - **Primary users**: Teams and individuals using AI coding agents - **Integrations**: Claude Code, Codex, Cursor, and Copilot - **Installation evidence**: Prebuilt binaries; the site documents Homebrew installation and project commands such as \`termaxa init\` and \`termaxa doctor\` - **Platforms listed**: Linux x86\_64, macOS arm64, macOS x86\_64, and Windows - **Command-line checks**: \`termaxa check\` evaluates a command; \`termaxa replay\` reviews commands already run