See what is being checked. Decide what happens next.
These settings apply to all runtimes on this node. Checks find evidence. They do not block an action on their own.
Approvals ask for a decision. Findings explain what a check noticed.
Keep watching, notify someone, ask for approval, or take an automatic action.
A policy can act automatically when a detector reports a condition. New policies start in monitor mode. They record the proposed action without changing the agent. An enabled policy can escalate its actions over time. For example, it can pause an agent, then kill it five minutes later if the condition continues. Each step requires the condition to remain active when the waiting period ends.
An agent can give different answers to the same request. Enable replay to measure this variation in failed sessions. Each replay runs your agent and can incur costs.
Review automatic responses and agent reports. For permission decisions and delivered notifications, open their history.
This view shows components read by Claude Code, Codex, Cursor, Gemini CLI, opencode, and OpenClaw. It includes MCP servers, skills, plugins, instruction files, and hook files. This view combines these runtimes. New or changed components flag the active sessions that load them. ClawMetry reads these files without starting a component. It does not inspect MCP tool descriptions.
Notes that agents sent through the ClawMetry MCP tool are counted by category. This view also shows how often an agent reported the same condition as a detector. Uncorroborated means that no independent evidence was found. It does not mean that the report is false.
See related behavior signals