Cloud relay

Connect your account

Each machine connects with its own device key. In the dashboard, create one under Settings > API > Devices, then run the install command shown with it on that machine. It installs the hooks and writes the key into them, readable only by you.

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

A device key pushes that machine's sessions and fetches its action gate settings; it reads nothing from your account. The command lands in your shell history, so revoke the key under Devices if the machine is shared or lost. Reading your account takes an API key from Settings > API > API keys, which cannot push.

On a machine that already has Asondy, this checks a new key with the relay and saves it:

asondy connect

Keep keys out of commits and chat messages.

What a connected session carries

• Project and session identity, coding-tool details and activity timestamps.
• Model, token and context usage the coding tool reports.
• Session events and verification outcomes.
• Conversation turns used to display the session and support remote interaction.

Conversation text can include code and personal data. See What we receive for each field.

Remote interaction

From the dashboard you can watch a connected session and send it an instruction. The coding tool's own permissions still apply.

Session signals and automated intervention

Session data feeds a risk score. It is an estimate, separate from gate verdicts. Risk-based intervention is off by default; when a deployment turns it on, it can pause a worker or ask for review.

Disconnect and data handling

Stop the connection to stop the live stream. Removing a key on the machine does not revoke it; revoke it under Devices. Stored records follow retention and deletion.