Can you trust your agents?

Know exactly what your agents did.

Your agents declare what they will do before they act. GateBolt holds them to it, and keeps the trail.

Free forever. No credit card.

Asked to fix one test, the agent also tried to edit the production deploy workflow and a database migration.
payments-api · fix/flaky-refund-test
Went as plannedEdits to 2 files stopped
The agent changed only what it said it would.
Task: “Fix the flaky refund test”
What it said
tests/refund.test.ts
src/refund.ts
What it did
tests/refund.test.ts
src/refund.ts
.github/workflows/deploy-production.yml stopped · not in the intent
db/migrations/0042_drop_refunds_table.sql stopped · not in the intent
Changes checked by your CI. Stops reported by the gate.
Problem

In 2026, AI agents went where nobody sent them.

Each time, the people answerable found out afterwards.

JUNE 2026

An AI lab’s agent got into a government health portal.

CNBC
SUMMER 2026

Its agents probed three US government agencies.

CNN
APRIL 2026

A coding agent deleted a company’s database in nine seconds.

The New Stack
Solution

The agent says it first. Anything else is stopped.

To go further, it has to declare again, before it acts.

Stopping needs strict mode in Code, or Enforce in Gateway. Without it the action goes ahead: Code reports it at the CI check, and Gateway on Record marks file changes only.