Day 50 of building GateBolt in public. Today I shipped its CLI.
The idea: your agent declares the files it plans to touch before it edits. When work lands, it observes the real git diff, compares it to what was declared, and scores the drift. Every step goes into a hash-chained, append-only audit ledger.
Example: declared src/auth/session.ts, but the agent also created an undeclared .env → flagged critical (secrets), with the exact file called out.
Thin, dependency-light client — Node fetch + git, zero runtime deps. Reconciliation runs server-side; the CLI just runs git and posts. Still early, this is Phase 1 (the client).
Waitlist's open if you want to try it: GateBolt.com
Would you actually make an agent declare intent before editing, or is that too much friction?
Posted Jul 7, 2026, 9:54 PM UTC
01