Skip to main content
Got questions about Critiqor? Here are answers to the things developers ask most often — covering what Critiqor does, how it handles your data, and how to get the most out of it.
Critiqor is an AI Agent Runtime Intelligence Platform. It observes your AI agents during execution, captures runtime evidence, and delivers reliability diagnostics through a local dashboard.It helps you see what your agent actually did — not just what it reported. Instead of relying on logs or agent self-reporting, Critiqor gives you an independent record of what happened during a real run.
Critiqor currently supports OpenClaw. You can monitor any agent running through OpenClaw using critiqor monitor openclaw.Support for additional frameworks and runtimes is on the roadmap. If you’d like to request a specific integration, open a GitHub issue at github.com/web3curtis/Critiqor.
Yes. Critiqor stores all run artifacts locally on your machine by default. Nothing leaves your machine unless you have explicitly configured a backend connection via CRITIQOR_BACKEND_URL.You control when observation starts, when it ends, and which results you review or share. Critiqor does not send telemetry or usage data without your explicit configuration.
No. Critiqor is a passive observer. It does not intercept, modify, or change your agent’s responses or behavior in any way. It runs alongside your agent and records what happens — your agent behaves exactly as it would without Critiqor present.
Run:
Check your current version at any time with:
Yes. Every critiqor finalize creates a new run with its own reliability report. Your runs accumulate over time, so you can track how your agent performs across different sessions or code changes.List all your runs:
Open a specific run’s dashboard:
Yes. Use critiqor check to run policy checks against your evaluation history. It exits non-zero if your defined thresholds are not met, making it compatible with CI/CD pipelines like GitHub Actions, GitLab CI, and CircleCI.
See the Policy Checks guide for details on configuring thresholds and failure conditions.
No. Critiqor complements your existing test suite — it doesn’t replace it.Unit tests, integration tests, evals, and human review each catch different classes of problems. Critiqor adds a layer that shows you what actually happened during a real agent run, which is something static tests alone can’t provide. Use all of these together for the most reliable agent development workflow.
Open a GitHub issue at github.com/web3curtis/Critiqor.To help us resolve it quickly, include:
  • Your Critiqor version (pip show critiqor)
  • Your Python version (python --version)
  • The exact command you ran
  • What you expected to happen
  • What actually happened (include any error output)
Useful contributions include:
  • Bug reports — clear, reproducible issues with version and environment details
  • Documentation improvements — corrections, clarifications, or missing examples
  • OpenClaw workflow feedback — real-world usage patterns that could improve the experience
  • Dashboard usability feedback — report anything confusing or missing in the local dashboard
  • Framework integration requests — let us know which runtimes or agent frameworks you’d like supported
If you’re proposing a larger change — such as a new feature or a significant refactor — open an issue first to discuss it before writing code. This ensures your effort aligns with the project’s direction.
Critiqor supports Python 3.10, 3.11, 3.12, and 3.13.To check which version you’re running:
If you’re on Python 3.9 or earlier, upgrade to a supported version before installing Critiqor.