Windows, macOS (Apple Silicon) and Linux (x86_64, glibc 2.28 or newer) are supported today. See Supported Software for the platform requirements and which integrations each platform covers.
What runs on the workstation
Argus consists of a desktop application and plugins that integrate with the engineering software installed on the same machine. The application accepts no inbound connections from the network. CAD models, simulation files, and generated code stay on the workstation.Optional connections to a Cosmon backend
By default, the desktop application can run without contacting a Cosmon backend at all. Each connection below is configured independently.Authorization
Argus is licensed under one of three models.
Machine-locked licensing is used by customers that need the application to run with no contact with Cosmon at any point.
LLM routing
The agent calls a large language model over HTTPS. Routing is configured per deployment.
In BYOK mode the desktop application calls the customer’s chosen endpoint directly. The endpoint does not have to be hosted by Cosmon.
Operational telemetry
When enabled, the desktop application sends operational telemetry to the Cosmon backend: usage counts, error reports, the application version, and OS metadata. Spans that would carry prompts or tool results are removed on the workstation before upload, and the backend drops any such span that reaches it from an Enterprise account. Telemetry is on by default and can be turned off in Settings.Conversation history sync
When enabled, the desktop application sends the conversation history to the Cosmon backend after each agent run. On the Enterprise plan the backend discards the content on arrival and keeps only counts, token totals, tool names and model names; on other plans the history is stored to support diagnostics and product analytics. Because history includes prompts and tool results, and those may contain engineering context, this is the one connection that can carry engineering content to Cosmon. Sync is on by default and can be turned off in Settings. Three further connections carry no conversation content: the version check and update download, error reports (stack traces, application version, OS) relayed through the Cosmon backend, and product analytics toanalytics.cosmon.com with all replayed text masked. See Data handling for the full per-connection breakdown and what Cosmon stores on each plan.
Backend topology
When backend connections are enabled, the destination depends on what the customer has provisioned.
The set of opt-in connections behaves identically across topologies. Only the destination URL changes.
Configuration spectrum
The four connections above are set independently, so deployments fall on a spectrum. Two endpoints of that spectrum:Fully airgapped
Machine-locked license, BYOK to an internal LLM endpoint, telemetry off, history sync off, and the update check blocked or disabled. Only then are there no outbound connections to Cosmon.
Fully Cosmon-connected
Named (SSO) license, Cosmon-routed LLM, telemetry on, history sync on. All connections active, against
desktop-api.cosmon.com.Further reading
Data handling
What leaves the workstation, what Cosmon stores per plan, staff access, retention and deletion.
Release integrity
Code signing, checksums, SLSA provenance and how to verify a build.