项目简介
iFixAi 是面向 AI 智能体的独立审计工具，基于业务 KPI 而非单纯技术指标，回答智能体是否在做它该做的事。它结合对抗性红队测试与运营保障纪律，可通过 CLI 向导、脚本参数或智能体插件运行，两分钟内生成分数报告与审计结果。
README 预览
\n \n \n \n \n \n \n\n\n\n English · 简体中文 · 日本語 · 한국어\n\n\nCatch your agent's mistakes and blind spots before the shit hits the fan.\n\n\n \n \n \n \n \n\n\n\n \n \n \n \n \n \n \n\n\n\n \n \n\n\n\n Quick start •\n Three ways to run •\n Test your agent •\n Scoring •\n Audit recorded actions •\n Docs •\n Contributing\n\n\n\n \n \n \n \n \n \n \n\n\n---\n\n## What it is\n\nThe 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.\n\nIs 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. \n\nAdversarial depth. Assurance discipline. All-in-one auditing process.\n\n## Three ways to run\n\nAll three run the same diagnostic underneath. The difference is how you configure and drive it.\n\n| | **CLI: guided wizard** | **CLI: explicit flags** | **Plugin or Skill** |\n|---|---|---|---|\n| **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 |\n| **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 |\n| **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` |\n| **Keys** | auto-detected by wizard; stored as env-var name in `ifixai.yaml`, never the secret itself | `--ap
常见问题 (1)
故障排除为什么 ifixai judge 在 self-eval 模式下连接到 localhost:8000 而不是我的自定义端点？如何修复 ProviderConnectionError？
故障排除
为什么 ifixai judge 在 self-eval 模式下连接到 localhost:8000 而不是我的自定义端点？如何修复 ProviderConnectionError？根本原因：ifixai/providers/http.py 第 22 行硬编码了 DEFAULT_ENDPOINT = "http://localhost:8000/v1"，并且 --endpoint CLI 值未通过 JudgeConfig 传播，因此 judge 内部的 HTTP provider 会回退到硬编码的默认值，而 SUT 则使用你的自定义端点。临时解决方法：将第 22 行修改为读取环境变量：DEFAULT_ENDPOINT = os.environ.get("IFIXAI_HTTP_ENDPOINT", "http://localhost:8000/v1")，然后在运行 ifixai run 之前执行 export IFIXAI_HTTP_ENDPOINT="https://my-proxy.example.com/v1"。或者，也可以直接临时将 DEFAULT_ENDPOINT 修改为你的代理 URL。永久修复需要通过 JudgeConfig 传播端点（在 issues #14 和 #15 中跟踪）。