Install Asondy

Before you begin

• Node.js 22 or newer: required for the built-in SQLite support used by the dashboard.
• macOS or Linux: the supported operating environments documented by the project.
• A supported coding tool: check integration coverage for the guards it can enforce.
• zsh: required if you want the terminal prompt link to the local dashboard.

node --version

Run the installer

npx create-asondy install

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.

What installation changes

The installer places the Asondy skill under ~/.claude/skills/asondy, installs command and agent definitions, and registers the applicable hook integrations. It also configures a guarded zsh prompt link for the dashboard. The exact configuration changes depend on the tools present on your machine.

Model traffic keeps its existing route by default. Routing through Asondy is an explicit installer option, --route-model-traffic; review the routing behavior before enabling it.

Check your first session

• Open a repository in your coding tool.
• Confirm that the installed integration is loaded and trusted.
• Use the dashboard link shown in your terminal to inspect the session.
• Give the Asondy command a small goal with an observable acceptance criterion.

The local dashboard uses a project-derived port and binds to 127.0.0.1. ASONDY_DASHBOARD_PORT can override its port. Project state is separate from the installed skill and normally lives in .asondy.

Updates and removal

The CLI includes a background update mechanism that can pull the latest revision and reinstall. In controlled CI or test environments, ASONDY_NO_AUTOUPDATE=1 disables that automatic update behavior.

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 dashboard

Check the Node.js version, reopen the terminal and use the URL printed for this project. Check for a port conflict if you set a custom port.

Hooks do not run

Restart the coding tool, review its hook trust settings and confirm that the requested guard is supported by that integration.

Cloud connection fails

Check the account key, relay URL and network access. If the connector reports that cloud push is disabled, preserve that protection and resolve the deployment issue first.