Pre-action firewall · <0.5ms local · Not a prompt · Not a postmortem

One repeated agent mistake. One configured gate.

ThumbGate checks proposed tool calls before execution in supported hook integrations. The $499 Setup Sprint turns one recurring failure in a supported local workflow into a configured gate, a regression test, and rollout and rollback evidence.

Illustrative example, not a recorded result. Matching destructive actions warn by default; advisory integrations do not guarantee execution blocking.

Free (MIT): npx thumbgate init

ThumbGate: thumbs up and thumbs down become a pre-action gate that can ALLOW, WARN, or DENY before the tool call runs
7 CLIs · local gate

Claude Code, Cursor, Codex, or similar agents.

Dashboard: npx thumbgate dashboard --open · /thumbgate-dashboard · thumbgate-dashboard · demo · strict-mode deny example ↓

$499one time · done-with-you setup

Setup Sprint

One 60-minute working review, one supported local workflow, one configured gate and regression test, plus written rollout and rollback proof. Delivery within two business days after access and agreed materials are available, subject to confirmed scheduling. If it cannot be reduced to a supported gate, the existing refund boundary applies. No enterprise rollout, SSO, hosted team sync or org-wide audit dashboard.

Prefer a call? Book a 15-min triage call →

  • One configured local gate and its regression test
Why it’s called ThumbGate

Thumbs teach. The gate enforces.

Without ThumbGate the same AI agent mistake repeats. With ThumbGate one thumbs-down becomes a local pre-action gate that can refresh or expire.
Agent proposes a tool, ThumbGate decides ALLOW WARN or DENY, thumbs feedback becomes a rule that closes the loop.
Self-improving product loop

Pre-action checks—and the systems that refine them.

Corrections become local lessons; repeated negatives become gates; the next action is checked before execution. Click a step for the under-the-hood demo.

Self-improving ThumbGate loop: thumbs up or thumbs down become a local lesson, then a prevention rule, then ALLOW WARN or DENY on the next tool call. The loop closes under your control without retraining the model.
Is it really self-improving? Yes — the control layer, not the LLM. 👍/👎 → local lesson → ranked rule → next tool call gated. No model retrain.

Each reviewed outcome closes the loop—under your control. Lessons are re-ranked per action, repeated failures can promote into gates, and stale auto-promoted gates expire. The firewall improves from explicit feedback without retraining the model or silently rewriting policy.

What the $499 setup buys

A managed gate for one painful workflow.

Boundary: the offer covers one supported local workflow. If the workflow cannot be reduced to one supported gate, the order is refunded instead of silently upsold.
What "stop" honestly means

Hard deny where configured. Honest warning everywhere else.

proposed  git push --force origin main
mode      strict enforcement
rule      protect-main
source    core protection · strict mode
decision  DENY
reason    force-push to protected branch
next      decision recorded before execution

Why not a static hook? Prompts compact away; static bash hooks don't learn from 👍/👎. Detected secret exfiltration and gate-process bypass attempts are denied by default. Matching destructive actions warn by default and deny in strict mode. This is a managed strict-mode example, not a claim that every free install blocks every risky command automatically.

Read the test-backed verification evidence →

White paper · Scorecard · Architecture · Dogfood, not customer stories

Enforcement by agent and mode

Per-agent enforcement and default block vs warn
AgentEnforcementDefault (secrets)Default (destructive)Strict mode
Claude Code, Codex, Gemini CLIBlocks before tool runsDENYWARNDENY
Cursor, Cline, OpenCodeAdvisoryDENYWARNDENY
AmpFeedback onlyLoggedLoggedLogged
Before you buy

Five questions, answered plainly.

One 60-minute working review for one repeated AI-agent workflow failure, one configured local gate for a supported workflow, its regression test, and a written rollout and rollback proof within two business days after access and the agreed materials are available.
No. Detected secret exfiltration and gate-process bypass attempts are denied by default. Matching destructive actions warn unless strict enforcement is enabled. The managed gate defines the right boundary for your workflow instead of pretending every warning is a firewall.
No. The $499 Setup Sprint configures one supported workflow with you. Shared hosting, SSO, compliance packaging, an org-wide audit log, and multi-workflow rollout are not included and are not generally available.
No. ThumbGate does not change model weights and does not silently rewrite production policy. Self-improving under your control means explicit approvals and feedback teach the local control layer what to allow, block, or escalate next time: lessons are stored and re-ranked, repeated negative patterns can promote into gates, and stale auto-promoted gates expire.
No. The promotion, demotion, and lesson-ranking logic ships in the public npm bundle under an MIT license — run npm pack thumbgate and read it yourself. Your lessons live in a local SQLite file you own, not a server you can't query. The $499 Setup Sprint adds a done-with-you failure map, one configured gate, and its regression proof, not access to intelligence withheld from the free install.
Limits

What this does not do.

  • Does not retrain model weights or silently rewrite production policy.
  • Does not contain the blast radius — that is a sandbox's job.
  • Default install warns on destructive actions; hard deny needs strict mode (THUMBGATE_STRICT_ENFORCEMENT=1).
  • The $499 Setup Sprint covers one supported local workflow. Multi-system implementation, SSO, a hosted audit log, and compliance packaging require separate scope and are not generally available.
Start free today

Block the mistake your agent made last week.

Run npx thumbgate init (MIT), or book a $499 setup.

Install free See the $499 setup