How it gets overlooked
You are waiting for the agent. The agent is waiting for you. A permission request or unanswered question can leave a task stalled while both sides assume the other is still working.
This becomes easy to miss when you have several agents open. One asks for approval in a terminal you are no longer watching. Another needs a decision before it can continue. The session is still there, but the next step belongs to a person.
What ClawMetry detects
ClawMetry can flag a session with a pending approval in its approvals queue. It can also use a recorded unanswered question or permission request together with measured idle time. Those sources give the finding a concrete reason.
The difference that changes the finding
Triggering example
1 pending approval
Warning finding
Quiet comparison
0 pending approvals
No finding for this detector.
The checked comparison supplies one pending approval and gets a warning. With no pending approval and no other blocked signal, the detector stays quiet. A brief question alone is not treated as a long wait without the required idle evidence.
Inspect the detector result
{
"kind": "blocked_on_user",
"severity": "warning",
"evidence": {
"pending_approvals": 1,
"idle_seconds": 0,
"threshold": 1,
"threshold_source": "static",
"observed": "pending rows in the approvals table for this session"
}
}How the example was checked
These examples evaluate the published detector with authored event data or disposable configuration files. The videos illustrate those behaviors. They are not recordings of live agents or the product interface. No command in the examples was executed.
The result establishes behavior for these inputs. It does not establish runtime ingestion, prevention or a real compromise. Inspect the pinned source contract.
What to check next
Open the relevant approval or return to the runtime question. Read the requested action before answering. Once you respond, verify that the session actually continues. The useful outcome is a visible handoff back to the agent.
- Open the pending request
- Review before answering
- Check that work resumes
What this signal establishes
Coverage depends on recorded approvals, questions and idle facts. This finding does not mean every runtime approval is routed through ClawMetry.