How it works

This page follows one change from your prompt to the merge into main and shows where Asondy checks it.

  1. You prompt your coding agent

    Install Asondy once with ASONDY_DEVICE_KEY=<device key> npx create-asondy install claude. It installs into your coding agent on your own machine, with no server or proxy in between. Then you prompt the agent the way you always do.

  2. Actions are checked before they run

    Before the agent runs a command, reads or edits a file or fetches a page, the action gates check that one action. They are fixed rules that run on your machine and call no model. A bad action is refused and the agent gets the reason, for example rm -rf outside the project, a read of .env, a push to main or a key pasted into a prompt. The action never runs. Asondy blocks it instead of logging it for you to read later, and the agent reads the reason and tries another way.

    Claude Code gets every action gate and is the only coding tool the installer supports today. Support for other coding tools is coming. See Agent setup for what the installer writes.

    If your org owner turns on the Data gate, each prompt, command and file write goes to asondy.com, is checked in memory and is not stored before it goes ahead. It stays off until then, and what we receive covers retention.

  3. Code is checked at push

    When the agent pushes or opens a pull request, the push gate scans the change for secrets before it leaves your machine, in every repo. In a repo set up with an Asondy goal, an .asondy folder holding criteria.json, OWNER or GOAL.md, it also runs 20 code gates. They look for deleted or weakened tests, complexity, duplication and AI-style code patterns, among others. A failed push goes back to the agent with the failed check, and the agent fixes the code and pushes again. Every gate is on the Gates page.

    The agent's edits to the hooks and settings that run these checks are refused, and a push from the agent that tells git to skip its hooks is still checked, because the push gate runs in the agent and not in git. Deleting the .asondy goal files stops the code gates, while the secret scan still runs. If a check crashes or runs out of time, the gates that stop secrets before a push or PR, PR size and quality gates before a push, a merge on red CI, a push to the default branch, a force-push or history rewrite, and a write that persists past the session refuse the action. When the hooks run through the dispatcher (install with --dispatch), the self-protect and switch-file gates refuse too. Other hooks mostly let it through; self-protect refuses a call naming its files when its engine crashes, and not when it times out, while the Data gate follows the org's fail mode. You can switch gates off, since it is your machine. Turn one off on the dashboard Gates page, uninstall Asondy, or push from your own terminal and tell git to skip its hooks. That is one reason to keep CI and branch protection on.

  4. Pull request, CI and review

    The pull request goes through your CI, branch protection and reviewers as it does today. Asondy adds two checks before the merge. The agent cannot merge while CI is red or has not run. If you install the PR Gate, a GitHub App, it runs Asondy's 17 diff code gates on every pull request as a check, so a push made outside an agent meets those diff code gates.

  5. The merge and after

    The merge happens once CI is green and your reviewers agree. After the merge Asondy lists any branches left over, and it does not deploy, watch production or roll anything back. What it allowed and blocked along the way stays in a record on your machine, and in the dashboard if you connected one. Asondy sits in front of CI, branch protection and code review and works alongside them.

Questions

Does my code leave my machine?

Not by default. Every gate reads your files where they are, and a connected dashboard gets counts, names, ids and hashes, never code or prompts. Content sharing and the Data gate (step 2) send content once someone turns them on, Verify and Harness send content only when you run them, and the PR Gate reads a pull request's changed files from GitHub once you install it. What we receive lists every field.

Does it add token costs?

An allowed ls or a small edit adds nothing to the agent's context in this benchmark, and neither does a plain prompt. A refusal adds its reason, 25 to 97 tokens in our benchmark. A token notice adds 35 to 48 tokens when the context has grown large, a subagent brief names no target, a foreground wait outlasts the prompt cache, a command has already held the turn past it, or a slow command is rerun with no file changed. The 9 PostToolUse hook groups that run after an action add context this benchmark does not measure. The first session adds about 1242 tokens, because the hook audit lists the flags it finds once and Asondy asks one question. Later sessions add a one-line hook audit of about 31 tokens, and a repo with surface-check findings adds those findings. The installed skill, agents and commands add about 417 tokens to the agent's lists of skills, agents and commands. These are context tokens, so they are the same on Claude Pro, Max 5x and Max 20x.

Does it slow my agents?

Each action waits for its checks, which run at once. The measured actions are a plain ls, an rm -rf outside the project, a read of .env and a small edit. On a 10-core Mac a fresh install's checks took 91 to 206 ms at the median and at most 252 ms at the 95th percentile, over 51 runs of each action. The 9 PostToolUse hook groups that run after an action are not in this benchmark for time, and the merge gate can hold a merge for up to 15 s before it answers. A push or pull request also waits for its code gates, up to 75 s when one runs long; a push is not in this benchmark. The checks run on your machine, and some of them ask the network. The merge gate asks GitHub for the CI state and can post a comment on the pull request. The push gate asks GitHub for the pull request and fetches its base branch. The push-to-main gate asks the remote for its default branch. The one-way gate looks a package up on npm, PyPI, crates.io or RubyGems. The Data gate asks asondy.com once it is on, and a connected machine sends session status to the dashboard.

Is CI not enough?

CI sees code only after a push. A deleted file or a read secret happens on your machine with no push, so CI never sees it, and that is what step 2 covers. Keep CI on too.

Can I add my own rules?

Yes. Put a Markdown file in .asondy/rules/ whose header sets event, matcher, pattern, action (block or warn) and message. This one stops the agent from running terraform destroy.

---
event: PreToolUse
matcher: Bash
pattern: terraform destroy
action: block
message: Ask the platform team before you destroy infrastructure.
---