ifixai-ai / iFixAi

English · 简体中文 · 日本語 · 한국어 
 Catch your agent's mistakes and blind spots before the shit hits the fan. 
 Quick start •
 Three ways to run •
 Test your agent •
 Scoring •
 Audit recorded actions •
 Docs •
 Contributing 
---
## What it is
The existing Eval, Red-teaming, and Observability Tools are evaluating the agent mainly based on tech capability (token efficiency, latency, prompt injections). They cannot answer the most crucial question.
Is the agent doing the job it is supposed to do based on the business KPIs and Organizational Structure? iFixAi gives you this answer in less than 120 seconds by striking the right balance between AI-Red Teaming and Operational Assurance. 
Adversarial depth. Assurance discipline. All-in-one auditing process.
## Three ways to run
All three run the same diagnostic underneath. The difference is how you configure and drive it.
| | **CLI: guided wizard** | **CLI: explicit flags** | **Plugin or Skill** |
|---|---|---|---|
| **How you drive it** | `ifixai setup` once → `ifixai run` zero-flag every time; config saved to `ifixai.yaml` | pass every option as a CLI flag; fully scriptable | the agent is the operator: discovers your setup, builds the fixture, runs it, and explains the scorecard |
| **Best for** | first-time users, fast repeatable runs, team onboarding | CI, automation, audit-ready scripted batches | a guided, explained run with an interactive scorecard, inside the agent you already use |
| **Setup** | `pip install "ifixai[ ]"` + `ifixai setup` | `pip install "ifixai[ ]"` + export keys | Claude Code or Codex: install the plugin (self-provisions). Any agent: `uvx ifixai install` scaffolds `/ifixai-skill` |
| **Keys** | auto-detected by wizard; stored as env-var name in `ifixai.yaml`, never the secret itself | `--api-key` flag or env var | each provider's key from its environment variable, never on the command line |
| **What you test** | any provider, or your agent's real endpoint | same | same |
| **Who grades it** | self, one independent vendor, or a multi-judge ensemble | same | same |
| **Output** | JSON + Markdown reports + rich terminal scorecard | same | interactive results artifact (+ JSON source of truth; static-report fallback) |
| **Suite** | pick with arrow keys in the wizard | 10 inspections by default; `--full-run` for all 60, or `--suite smoke\|strategic\|essential\|core\|extended\|all` | the agent picks `--mode`/`--suite`, same engine as the CLI |
| **Works in** | any terminal | any terminal / CI | Claude Code, Cursor, Codex, VS Code, Windsurf, Cline, Continue, Gemini, Zed |
## Quick start
**Explore business-policy compositions:** Policy Lab finds shortest harmful sequences of permitted actions and checks permission repairs against legitimate completion goals. Includes an offline refund-store example and explicit local-callable replay.
Now try it yourself. Pick a path from the table above; full walkthrough: **docs/get-started.md**.
### Guided wizard (recommended)
 [code] 
`ifixai setup` detect