Rules are expressions
The recipients, the links and where they go, the amount, how many went out today: code reads them from the call itself. Never-rules run first, then ask-me, then send.
DataSnack · the write gate for Claude and Codex
DataSnack checks the writes your agent makes to outside services (e.g., Gmail, LinkedIn, Google Sheets, Stripe) against your rules, and code makes the call, not another LLM.
Same call, same rules, same answer. Every time.
private-record · writtenno-refunds-over-200 · not sentHow it works
Not email only: a message, a public post, a payment, a row in a shared sheet, a calendar invite, a delete. If it changes something outside the conversation, it is checked.
Add DataSnack as a connector in Claude, or install the hook in Claude Code and Codex. A few minutes, no code.
Nothing is stopped. You see every write, and what each rule would have done with it, while DataSnack drafts your rules.
One switch on the dashboard, per connector. Now what your rules do not clear waits for you, and what they refuse never goes.
Why code
"Never email a customer without asking" works until the day the model reads it differently. The alternatives today are trusting the prompt or approving every call yourself.
| How you gate your agent | Who decides | Same call, same answer? | What you do |
|---|---|---|---|
| A line in the prompt | The model | Usually | Find out afterwards |
| Approve every call by hand | You | Yes | Click yes all day, or stop reading |
| DataSnack | Code, over rules you can read | Yes | Answer only what no rule covers |
What "code decides" means
The recipients, the links and where they go, the amount, how many went out today: code reads them from the call itself. Never-rules run first, then ask-me, then send.
For what only a reader can tell (an invented number, a promise), Jev, a fast reading model, scores the text. Code compares the score with the rule's limit.
What was read is kept, so asking twice gets the same answer. Anything too close to a limit, or that cannot be checked, is held for you rather than guessed.
No rules to write
Every tool starts with starter rules: payments, deletes, public posts and mass messages are asked about. Nothing to set up.
Paste a task's instructions and its "never" and "at most" lines become rules. They go live when you say they are right.
Your answers and marks become proposed rules, each shown with its evidence. One that contradicts any answer you gave is never shown.
No rule goes live without you: that is the point of a gate you can trust.
Observe, then gate
Each connector has its own mode, switched from the dashboard. Nothing changes in your agent.
Everything goes ahead. DataSnack records each write and what it would have held and why. Nothing is ever stopped, an outage included.
What your rules clear goes out, what they do not waits for your answer on your phone, and what they refuse never goes.
With the hook, in Claude Code and Codex, a blocked call cannot run: the client stops it, whatever the model wants. In Claude's apps and Cowork, the agent asks first because your task tells it to, and DataSnack shows you when it did not. Handled, coming soon, has DataSnack do the sending itself.
One place
Claude, ChatGPT, Codex and Claude Code each have their own settings, and none of them share. DataSnack sits outside all of them, so a rule for every task applies wherever your work runs: "never pay more than $200" means the same through any payment tool, in any assistant.
A rule covers one tool, every tool a task uses, or every task. The wide ones read what every write has in common, so they fit tools DataSnack has never seen.
Whatever was held, from whichever assistant, waits in one Outbox, and every write lands in one record.
Try a new assistant next month. Your rules were never in the old one.
Rules that read one tool's own arguments, a subject line or a channel, stay with that tool.
What it checks
Every action is described the same way whatever app it goes through, so one rule can cover them all: "ask me about any payment over $200", written for every task, holds a Stripe refund and a PayPal payout alike.
Connect it, start in Observe, and switch on Check when the rules look right. Free while in preview.