Skip to main content
This page covers the most common issues you may encounter when installing, configuring, or running Critiqor — and how to resolve them quickly.
Check that you’re running Python 3.10 or later:
Update pip before retrying:
If the error persists, install inside a virtual environment to avoid system-level conflicts:
If your network or corporate proxy causes SSL verification failures, pass trusted hosts explicitly:
This bypasses SSL certificate verification for the PyPI download only. For a long-term fix, talk to your network administrator about adding the relevant CA certificates to your system trust store.
After installation, the critiqor CLI entry point may not be on your PATH. Try invoking it via Python directly as a fallback:
To fix PATH permanently:
  • macOS / Linux — add your Python bin directory to your shell profile (e.g. ~/.bashrc or ~/.zshrc):
  • Windows — add the Python Scripts directory (e.g. C:\Users\<you>\AppData\Local\Programs\Python\Python3x\Scripts) to your system PATH via System Properties → Environment Variables.
If you’re using a virtual environment, make sure it’s activated before running critiqor:
If your browser doesn’t open automatically:
  1. Check that no firewall or security tool is blocking localhost connections.
  2. Try specifying a host and port explicitly:
  3. Copy the URL printed in your terminal and open it manually in your browser.
If none of these work, verify that the port isn’t already in use by another process:
The dashboard requires a completed run to display a report. Make sure you ran critiqor finalize after your observation session — not just critiqor monitor.The typical workflow is:
If you open the dashboard before finalizing, it has nothing to display yet.
The observation window starts when you run critiqor monitor openclaw, not before. If you started your agent before running the monitor command, those interactions fall outside the session and are not captured.Always follow this order:
  1. Run critiqor monitor openclaw first.
  2. Then start using your agent.
  3. Then run critiqor finalize when done.
If your session completed but no events were recorded:
  • Confirm that OpenClaw was launched through the Critiqor monitor command, not independently in a separate terminal.
  • Verify that you actively interacted with your agent during the observation window.
  • Check that OpenClaw is installed and available in your PATH:
If OpenClaw is not found, install it and re-run critiqor monitor openclaw.
Critiqor writes run artifacts to your current working directory. If that directory is not writable, you’ll see a permission error.
  • Run Critiqor from your home directory or a project folder where you have write access.
  • On macOS / Linux, fix permissions on your project directory if needed:
  • On Windows, make sure you’re not running from a read-only or system-protected path (e.g. C:\Program Files).
Critiqor connects to a backend to generate reliability reports. If the backend is not configured, finalization will fail.Set the required environment variables before running critiqor finalize:
On Windows (PowerShell):
If you don’t have a backend URL or API key, contact Critiqor support to get your credentials.
Run:
Verify the installed version after upgrading:
Critiqor starts OpenClaw automatically when you run critiqor monitor openclaw. If OpenClaw does not launch:
  1. Confirm that OpenClaw is installed on your system.
  2. Confirm that the openclaw binary is available in your PATH:
  3. If it’s not found, install OpenClaw and try again.
If you’re still stuck, open a GitHub issue at github.com/web3curtis/Critiqor and 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)