Agentagon

Find failures. Test fixes. Ship with evidence.

Agentagon helps your coding agent review code and execution traces, prepare evaluations, and compare fixes against a recorded baseline. The Python CLI captures evidence, runs checks and saves reports; the ag plugin supplies workflows for Codex and Claude Code. Your coding agent supplies the reasoning and reviews.

Start with Audit your agent to investigate a concern, or Improve your agent to bring one known failure through evaluation and repair. Review, Eval and Ship support the later steps. Install the plugin if needed.

See an improvement: the ticket-retry demonstration runs an actual model against controlled tool state, compares request-scoped idempotency with a regressing alternative, and retains a test for duplicate creation. It is a seeded example with explicit model access and execution limits.

Prerequisites

• Python 3.12+ with pip and venv, on macOS or Linux. The implementation uses Unix facilities such as fcntl.
• Git to clone this repository, review changes, and run evaluation or fix workflows. Full code audits also accept directories without Git.
• Codex or Claude Code with its native plugin manager for agent-led workflows. The local example below needs neither host nor credentials.

Installation downloads Python dependencies. No Agentagon account or API key is required for the local example or core workflows; your coding host and configured services have their own access requirements.

Installation

Install the CLI from PyPI using pipx:

pipx install agentagon
agentagon install --host codex
# Or: agentagon install --host claude-code

Start a new coding-host session after registration. CLI installation and host registration are separate steps; select the host you use. Downloadable wheels, source archives and checksums are also available in GitHub Releases.

For source installation in an isolated environment:

git clone https://github.com/agentagon/agentagon.git
cd agentagon
python3 -m venv .venv
. .venv/bin/activate
python -m pip install .
agentagon --help

Ensure python3 --version reports 3.12 or newer. Keep this environment active for the following commands; reactivate it in each new shell.

For a persistent CLI and native host plugins, use the plugin installer. It creates a separate runtime and registers ag with selected or detected hosts.

Anonymous skill and Intelligence usage telemetry is enabled by default. Disable it with agentagon setup --scope user --set telemetry.enabled false or AGENTAGON_TELEMETRY_DISABLED=1. See collected fields, privacy and delivery.

Optional Agentagon Intelligence is available through live /v1/audit, /v1/eval and /v1/fix routes. Configure the issued origin explicitly and follow the workflow-specific request and privacy rules.

Quick start

For an offline installation check, run the bundled synthetic application example from the repository root:

python examples/local-audit/demo.py

It creates a temporary application, captures its source, prepares an evidence packet and writes a partial report. After installation, this example needs no network services. Expected JSON has this shape; paths and IDs vary:

{
  "workspace": "/tmp/agentagon-example-…/app",
  "audit_id": "audit_…",
  "pending_action": "evidence",
  "packet": "/tmp/agentagon-example-…/app/.agentagon/audits/audit_…/packets/packet_….json",
  "response_template": "/tmp/agentagon-example-…/app/.agentagon/audits/audit_…/packets/packet_….response.json",
  "report": "/tmp/agentagon-example-…/app/.agentagon/reports/audit_…/report.md"
}

Open the printed packet and report files. pending_action: "evidence" means the coding agent still needs to review the evidence, not that the application passed an audit. The temporary directory remains available for inspection; remove it when finished. See the example guide to open its dashboard.

Use with your coding agent

After installing the plugin, start a new host session in your application's directory. In Claude Code:

/ag:audit Check input validation and tool error handling.

In Codex, choose ag:audit from the native skill picker. Agentagon skills automatically open the application's dashboard as work begins and reuse it across workflows. Use ag:dashboard to reopen it or inspect another result.

Evaluation and fix workflows require a clean committed checkout and configured execution limits. See the capability overview for integrations and workflow boundaries.

Configuration and saved data

No configuration is needed for the quickstart: the example isolates its settings automatically. To inspect settings for your current directory:

agentagon setup

Project overrides take precedence over user defaults. Credential settings store environment-variable names, not secret values. Use ag:setup and the configuration guide for traces and preferences, execution profiles for evaluations and fixes, and Intelligence setup for optional audit, evaluation and fix guidance.

Evidence is stored locally; your coding host and configured services determine where model processing occurs.

Development and contributing

See CONTRIBUTING.md for editable installation, local development, tests and the pull request workflow. The documentation index links deeper guides and references.

To explore the implementation, start with how Agentagon works and the extension walkthrough. Maintainers can follow release preparation.

Report vulnerabilities through SECURITY.md. Participation follows the Code of Conduct.

License

Apache-2.0.