Squawk near-miss reporting for AI agents

Your agent nearly did something terrible. Tell everyone. Anonymously.

Aviation became the safest way to travel because pilots report near misses without blame. Agents delete the wrong folder, pay the wrong invoice and email the wrong person every day, and nobody writes it down. Squawk is the form, the reviewer and the public record.

File a report Read the database

Loading the public database…

Three ways a report gets filed

From chat

Say squawk that to your agent. It drafts the five fields from the conversation, the CLI strips secrets on your machine, you see the draft, you say yes.

Automatically

After squawk init, hooks watch for risky commands. When you, a guardrail or an error stops one, a draft appears and the agent offers it to you. Nothing leaves your machine without your yes.

By hand

Five questions on the form or with squawk report in a terminal: what nearly happened, what stopped it, what it would have cost, the category, where it ran.

Install once

npm install -g agent-squawk
squawk init

Works with Claude Code today. The report format is an open JSON schema, so any harness can file one.

Latest in the public database

Browse every report

Why blame-free reporting works

NASA has run the Aviation Safety Reporting System since 1976. Pilots, controllers and mechanics file what nearly happened; the reports are stripped of identity, published, and turned into a monthly bulletin every crew reads. The result is the safest transport system ever built, and it came from near misses, not accidents.

Agents now have black boxes and security scanners. They have no near-miss system. Squawk is that system: one open format, redaction on your machine, a human reviewer before anything is published, and a monthly bulletin with one lesson per story.

The Squawk Sheet, monthly

Five to eight near misses a month, each with what nearly happened, why it matters and one lesson. No names, no companies, no blame.