Cloud relay

Connect your account

Use the connector from your project to manage cloud API keys. It validates a new key with the relay before saving it and stores the key file with owner-only permissions.

asondy connect

Choose the account you intend to use and start the dashboard connection from the connector. Keep keys out of commits, chat messages and terminal command arguments. If cloud push is disabled by a local protection, resolve the reported deployment condition before enabling it.

What a connected session carries

• Project and session identity, coding-tool details and activity timestamps.
• Available model, token, cache and context measurements from the integration.
• Session events and verification outcomes.
• Conversation turns used to display the session and support remote interaction.

Conversation text can include code and personal information. Review what your coding tool’s transcript contains before connecting a sensitive workspace. Metric availability and precision vary across integrations.

Remote interaction

The relay supports an authenticated dashboard view and commands directed to a connected session. Use the correct account and project when sending a remote instruction. Keep the local coding tool’s permissions and repository approval rules in place.

Model routing is a separate choice

Installing Asondy does not reroute model requests by default. Enabling --route-model-traffic configures supported clients to route requests through Asondy to the configured model provider. Those requests may contain prompts, source code and responses.

The router can retry a failed request with another configured provider. A rate limit, rejected key or server error can therefore cause the same content to reach more than one provider. Only configure providers that are authorized for the workspace’s data.

The selected provider’s terms and data handling apply to requests it receives. Review both the provider configuration and your workspace’s permission to share that content.

Session signals and automated intervention

Cloud session measurements also feed risk estimates and calibration records. They describe observed patterns and can be wrong; they are separate from deterministic gate verdicts.

The reviewed implementation leaves risk-based intervention off by default. When explicitly enabled in a deployment, it can pause a worker or request further review based on the score. Review both the deployment setting and the evidence before relying on this behavior.

Disconnect and data handling

Stop the running connection to stop that session’s live stream. Removing a key from the connector removes that local saved entry; it should not be treated as proof that all issued credentials or previously stored cloud records have been deleted.

Account data, persistent audit events and usage records are separate from the temporary live-session buffer. See retention and deletion for the distinction.