What gets captured
Critiqor records the following during an observation session:- Tool calls and their outcomes — every tool your agent invokes, whether the call succeeded, failed, or returned unexpected results.
- Retry attempts and loops — repeated attempts at the same action, including cases where your agent retries without apparent progress.
- Failures and error events — exceptions, timeouts, and other failure signals that occurred during the run, even if the agent ultimately recovered.
- Execution timing and sequencing — the order in which actions were taken and how long each phase of the run took.
- Cost signals — redundant tool calls, unnecessary repeated work, and other patterns that inflate execution cost without adding value.
- Agent behavior patterns across the session — how your agent’s behavior evolved over the course of a run, including any escalation in retries or error frequency.
Runtime vs final-answer evaluation
Runtime evidence reveals what the agent actually did. Final-answer evaluation only shows what the agent reported.
When observation is active
Observation starts when you runcritiqor monitor openclaw and ends when you run critiqor finalize. During this window, Critiqor runs passively in the background, recording runtime evidence from your agent’s session. When you finalize, Critiqor uses that evidence to produce the reliability report for the run.
Critiqor is passive — it does not modify your agent’s behavior or intercept its responses. Your agent runs exactly as it would without Critiqor present.