Install Asondy

  1. Before you begin

    • An Asondy account: every plan needs one, Free included. Create one free with Google, GitHub, Microsoft or an email and password.
    • Node.js 22 or newer: the installer and the hooks run on it. Check it with node --version.
    • macOS or Linux.
    • A supported coding tool: check integration coverage for the action gates it can enforce.

  2. Connect this machine

    In the dashboard, open Settings > API > Devices and choose Add device. It shows this command with the machine's new key in place of <device key>. Run it on that machine: it installs the hooks for your coding tool and writes the key into them, so each session reports to your dashboard.

    ASONDY_DEVICE_KEY=<device key> npx create-asondy install claude

    The key is shown once, and it reads nothing from your account. Name another coding tool in place of claude, or leave it out and the installer asks.

  3. Restart your coding tool

    Restart your coding tool after installation. In Codex, review the installed hooks with /hooks and complete the trust step. Existing sessions may need to be reopened before the new hooks take effect.

  4. Check your first session

    • Open a repository in your coding tool.
    • Confirm that the installed integration is loaded and trusted.
    • Open your dashboard: the session shows under its project in Projects, and the Overview counts what the action gates stop.
    • Give the Asondy command a small goal with an observable acceptance criterion.

    Project state is separate from the installed skill and normally lives in .asondy.

What installation changes

The installer places the Asondy skill under ~/.claude/skills/asondy, installs command and agent definitions, and registers the applicable hook integrations. What it writes depends on the coding tools it finds.

Push protection stays scoped: an agent push to the default branch is refused in every repository, while a push from your own terminal is refused only inside repositories that hold an .asondy/ folder.

Updates and removal

Asondy updates itself in the background. Set ASONDY_NO_AUTOUPDATE=1 to turn that off in CI or tests.

To remove the installed integration, run the uninstaller from an Asondy source checkout:

node bin/uninstall.js

Removing the local integration is separate from deleting hosted account records. See your data choices for cloud data.

Troubleshooting

No session in the dashboard
Check that you ran the install command shown with the device key, then restart the coding tool and open a new session. The machine needs network access to asondy.com.
Hooks do not run
Restart the coding tool, review its hook trust settings and confirm that the requested gate is supported by that integration.
Cloud connection fails
Check that the machine holds a device key from Settings > API > Devices, not an API key, then the relay URL and network access. If the connector reports that cloud push is disabled, preserve that protection and resolve the deployment issue first.

References

Continue readingWorkflow