Every action on the record

Know exactly what every agent did, and why it was allowed.

Clawvisor records each tool call, its arguments, and the decision that permitted it in a complete, replayable log. Every entry is tied back to the task that authorized it and the human who approved that task, so 'what did the agent do' is a query, not an investigation.
Logged & attributed

Triage the failing CI check on billing-api and file an issue.

dev-agentexpires when task completes
Tools requested2

  • github · get_pr

    repo: billing-api

    read

  • github · create_issue

    repo: billing-api

    write
low risk

The problem with black-box agents

When an agent runs free against your tools, the only record is whatever scattered logging each tool happens to keep. Reconstructing a single agent run means stitching together Gmail history, Git events, and database logs by hand, and none of them know which task or which person set the work in motion. By the time something looks wrong, the trail is cold and incomplete.

How observability works

01

Every call, captured

Tool name, arguments, result status, and timing are logged at the gateway, the one place every request already passes through.

02

Tied to the task

Each entry links to the task that authorized it and the human who approved it, so cause and authority are never ambiguous.

03

Full traceability

Each entry is written at the gateway as the call happens, so every run leaves a complete, ordered record.

04

Replayable & exportable

Step through any run after the fact, with the full call history in one place.

run #4821 · support-agent · 14:01:55 → 14:02:11
14:01:55

google.gmail · get_thread thread #4821 200

task #4821 · approved by J. Mercer

14:01:57

dropbox · delete "/Finance/2026-Q1" denied

task #4821 · blocked by policy · never executed

14:02:08

github · list_issues repo: billing-api 200

task #4821 · approved by J. Mercer

14:02:09

google.calendar · list_events next 14 days 200

task #4821 · approved by J. Mercer

14:02:11

google.gmail · send_message thread #4821 sent

task #4821 · approved by J. Mercer

✓ signed · auditable · ordered5 calls · 1 denied

Audits, incident reviews, and 'who approved this' all become a single lookup.

It’s one of the power-ups you get from approving the task instead of the tools.

Requests must match the task

Purpose verification

You approve a task, not a standing permission. Every request the agent makes is checked against the purpose you approved — a calendar read for your morning briefing goes through, an expense audit across all history does not.

Every action on the recordYou're here

Audit trail

Every request, every purpose declaration, every decision, every credential injection. A complete record of what your agent asked for and what Clawvisor allowed.

The agent never sees your keys

Credential injection

Your API keys and OAuth tokens live in an encrypted vault. Clawvisor injects credentials server-side and returns sanitized results, so a leaked prompt or transcript can't leak a token.

Scored before it runs

Risk assessment

Every request is scored for risk before execution. Clawvisor flags anomalous parameters, unusual access patterns, scope creep, and prompt-injection attempts hiding in tool arguments.

Let your agents act. Safely.

Connect your accounts and put a gatekeeper in front of your agents in minutes. Free to start, no credit card.

Get started freeRead the docs