Resources
Documentation
A clear path from your first install to verified agent work.
What Asondy does
Asondy runs checks and enforces gates in supported AI coding tools. Guards check specific conditions at supported workflow stages; the goal loop organizes planning, implementation and independent review. The dashboard shows session activity and check results.
The name stands for Agentic Systems ON Deterministic Yield. Deterministic gates evaluate configured conditions. They do not make an AI model’s output deterministic or establish that software is free of defects.
Start with a local installation. Connect the cloud relay when you want a hosted view of sessions, remote controls or server-side verification. Model routing is a separate, optional setting.
Install and start a session
Use Node.js 22 or newer on macOS or Linux. The terminal prompt link requires zsh. Run the installer, then restart your coding tool so it can load the installed integration.
npx create-asondy install
For Codex, review and trust the installed hooks through /hooks. See the installation guide for setup details, updates and removal.
Give the loop a goal
In a coding tool with the Asondy command installed, describe the outcome and what would count as success. Concrete acceptance criteria make the result easier to verify.
/asondy Add password reset. Verify that links expire, cannot be reused, and never reveal whether an account exists.
The loop breaks the goal into scoped work, runs checks and reviews the result before completion. Explore the workflow.
Know what is active
An integration’s presence does not mean every guard can block every action. Enforcement depends on the hook API exposed by your coding tool.
- Claude Code: the full integration registers lifecycle and tool-action hooks.
- Kimi Code, Codex, Gemini CLI and Qwen Code: shared push-gate, model-policy and reply-brevity integration.
- OpenCode, Hermes, Cursor agent and Continue: telemetry and routing support; their enforcement surfaces differ.
- Aider: no native hook system for action blocking.
Keep repository branch protections and CI checks enabled. Asondy adds checks inside supported coding workflows; the repository still controls which changes can merge.
Available session metrics vary by integration. See the Guards guide for gate coverage and individual check details.
Verify the submitted revision
Server-authoritative verification identifies the repository and commit. The server fetches that revision, runs the configured gates and returns a verdict with check results. That verdict applies to the revision that was checked; changed code needs a new result.
Connect the cloud relay
The relay can carry session events, usage information and conversation turns to the dashboard. Review the data flow before connecting a repository that contains confidential or personal information.