Runtime intelligence CLI for reviewing AI agent reliability.
Project description
Critiqor
Runtime Intelligence for AI Agents
Observe. Diagnose. Improve.
pip install critiqor
Critiqor helps developers understand whether AI agent runs can be trusted. It observes agent execution, produces a reliability report, and gives teams a clearer way to review agent behavior before relying on the result.
Instead of asking an agent to explain itself after the fact, Critiqor focuses on observable behavior from the run.
Introduction
AI agents are powerful, but a final answer does not always tell the whole story.
An agent can return something useful while still behaving unreliably during execution. Critiqor gives developers a practical review layer for understanding whether a run looked healthy, risky, inefficient, or worth investigating further.
With Critiqor, you can:
- observe agent runs from the terminal
- review reliability reports in a dashboard
- compare previous runs
- spot behavior that needs developer review
- improve agents with measurable feedback
Dashboard Preview
After an observation session, Critiqor opens a dashboard that summarizes the run in a format designed for developers and teams.
You can review:
- Executive Summary - the fast answer on whether the run looks healthy
- Trust Assessment - readiness and confidence signals
- Primary Diagnosis - what deserves attention
- Run Review - the observed behavior behind the report
- Recommendations - practical next steps
- Historical Runs - previous observations for comparison
Installation
Install Critiqor from PyPI:
pip install critiqor
Check the CLI:
critiqor help
Operating System Compatibility
Critiqor is distributed as a Python CLI package. The package can be installed anywhere Python 3.10+ is available, but the best installation path depends on the operating system and terminal environment.
| Operating system | Compatibility | Recommended install path |
|---|---|---|
| macOS | Supported | Python 3.10+ with pip or pipx |
| Linux | Supported | Distro Python package manager, then pip or pipx |
| Windows | Supported with WSL recommended | WSL2 for OpenClaw workflows, or native Windows Python for basic CLI usage |
macOS
Compatibility: supported and recommended.
macOS provides a reliable terminal environment for Critiqor's OpenClaw observation workflow.
python3 --version
python3 -m pip install critiqor
critiqor help
Optional isolated install with pipx:
brew install pipx
pipx install critiqor
Notes:
- Use Python 3.10 or newer.
- If
pipis missing, install Python from python.org or Homebrew. - Make sure OpenClaw is installed and available on your
PATHbefore runningcritiqor monitor openclaw.
Linux
Compatibility: supported and recommended.
Linux is a strong environment for Critiqor because terminal process handling and OpenClaw runtime workflows are typically predictable.
Debian or Ubuntu setup:
sudo apt update
sudo apt install python3 python3-pip python3-venv
python3 -m pip install critiqor
critiqor help
Fedora setup:
sudo dnf install python3 python3-pip
python3 -m pip install critiqor
critiqor help
Arch setup:
sudo pacman -S python python-pip
python -m pip install critiqor
critiqor help
Notes:
- Use your distro package manager to install Python and pip first.
- A virtual environment is recommended if your distribution restricts global Python installs.
- Make sure OpenClaw is installed and available on your
PATH.
Windows
Compatibility: supported, with WSL2 recommended for OpenClaw monitoring.
Critiqor can be installed on native Windows when Python 3.10+ is available. However, OpenClaw terminal/TUI behavior and child-process handling can vary across PowerShell, Command Prompt, and terminal emulators. For the most reliable Critiqor + OpenClaw workflow, use Windows Subsystem for Linux 2.
Recommended WSL2 workflow:
sudo apt update
sudo apt install python3 python3-pip python3-venv
python3 -m pip install critiqor
critiqor monitor openclaw
Native PowerShell workflow:
py --version
py -m pip install critiqor
critiqor help
Notes:
- Use WSL2 when running
critiqor monitor openclaw. - Native Windows is suitable for checking the CLI, opening reports, and basic workflows.
- If using PowerShell directly, verify OpenClaw itself runs correctly before starting Critiqor.
- The dashboard opens in your browser after a completed run.
Quick Start
1. Start an observation session
critiqor monitor openclaw
Critiqor starts the OpenClaw workflow and begins observing the run.
2. Use OpenClaw normally
Work with your agent as usual. Critiqor stays out of the way while the agent runs.
3. Finalize the observation
critiqor finalize
Critiqor completes the observation, prepares the reliability report, and opens the dashboard. Diagnosis runs locally by default; no Critiqor API key or hosted backend is required. If the richer Core Engine dashboard is not installed, Critiqor uses the dependency-free dashboard included in the Python package.
4. Reopen previous runs
List historical evaluations:
critiqor runs
Open the latest dashboard:
critiqor dashboard
Open a specific run:
critiqor dashboard run_001
Features
Terminal-First Workflow
Start and finish agent observations directly from the Critiqor CLI.
Reliability Reports
Review whether a run looks healthy, needs review, or should be treated with caution.
Dashboard Review
Move from terminal execution to a visual report built for debugging, communication, and decision-making.
Historical Runs
Revisit previous observations and compare reliability over time.
OpenClaw Support
Critiqor currently focuses on OpenClaw-based agent workflows.
When to Use
Use Critiqor when you need to:
- validate agent changes before release
- debug failed or suspicious runs
- compare prompt iterations
- review new agent tools or skills
- catch regressions in behavior
- measure reliability improvements over time
- explain agent behavior to teammates or stakeholders
- decide whether an agent run is ready for production workflows
Trust & Privacy
Critiqor is designed around explicit observation.
Developers control when observation starts, when it ends, and which results they review or share. Critiqor provides reliability signals to support developer judgment; it does not replace tests, human review, or production monitoring.
Principles:
- observation should be explicit
- reports should be grounded in the observed run
- developers should be able to review the result
- sensitive workflow data should remain under user control
- reliability reports should support human decision-making
Philosophy
Critiqor is built on a simple belief:
Reliable agents should be evaluated by what they do, not what they say they did.
That means:
- evaluate observable behavior
- prioritize evidence over self-reporting
- make reliability easier to explain
- improve through measurement
- help developers review the work behind the answer
FAQ
What is Critiqor?
Critiqor is an AI Agent Runtime Intelligence Platform. It helps developers observe agent runs and review reliability reports.
Which workflows are supported?
Critiqor currently supports OpenClaw-focused observation workflows.
How do I install Critiqor?
pip install critiqor
What does the dashboard show?
The dashboard shows an executive summary, trust assessment, primary diagnosis, run review, recommendations, and historical runs.
How should I interpret trust levels?
Trust levels are reliability signals based on the observed run. They help you decide whether a run looks healthy, needs review, or may be risky.
Can I review previous runs?
Yes. Use:
critiqor runs
critiqor dashboard run_001
Does Critiqor replace tests?
No. Critiqor complements tests by helping you review how an agent behaved during a run. Use it alongside unit tests, integration tests, evals, and human review.
How do I report bugs?
Open a GitHub issue with:
- your Critiqor version
- your Python version
- the command you ran
- what you expected
- what happened instead
Contributing
Critiqor is early and evolving quickly.
Useful contributions include:
- bug reports
- documentation improvements
- OpenClaw workflow feedback
- dashboard usability feedback
- integration requests
If you are proposing a larger change, please open an issue first so the direction can be discussed.
License
Critiqor is released under the MIT License. See LICENSE for details.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file critiqor-0.2.9.tar.gz.
File metadata
- Download URL: critiqor-0.2.9.tar.gz
- Upload date:
- Size: 55.1 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.13.2
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
6dac351650c5ea21778349ec229be8e881cc4ac0b537e9c36b31ccdc2c50302f
|
|
| MD5 |
b30abf0fb8e83b351f5bae4be20776bb
|
|
| BLAKE2b-256 |
c990f23ac692468982578d7d5abb2f4fc67ff08a877b786d29791e5cd38e38a4
|
File details
Details for the file critiqor-0.2.9-py3-none-any.whl.
File metadata
- Download URL: critiqor-0.2.9-py3-none-any.whl
- Upload date:
- Size: 45.9 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.13.2
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
c3cd2ad0ad7154120cd6f4f9e4f0d26b79bc7320b0a30ada09762f835862b0d9
|
|
| MD5 |
31b410915825aebcd222af1d4b3f86b0
|
|
| BLAKE2b-256 |
d370a8533971a543eb396597f3cad8c469ea2a1889523129d5c63e30ca1af477
|