Availability by Surface
Availability depends on the deployment, client version, connected model provider, and distribution channel. This page describes what the current documentation can verify; it is not a promise that every surface is publicly distributed.
| Surface | Current documented access | Boundary |
|---|---|---|
| CLI and local web UI | Approved CLI distribution | No verified public CLI download is listed here |
| Desktop | Approved desktop installer | No verified public Desktop download is listed here |
| VS Code extension | Approved VSIX distribution | Managed runtime installation requires an available configured release channel |
| JavaScript SDK | SDK supplied by your deployment | Public package registry availability is not guaranteed |
| GitHub Action | Approved deployments with access to the Action and a published runtime | Pin both the Action commit and runtime version; sharing is off by default |
| GitLab CI | Operator-configured job using an approved CLI distribution | No verified public GitLab component is offered |
| Hosted and multi-tenant services | Deployment-specific | Confirm identity, retention, region, audit, and support terms with the operator |
| Optional learning and synchronization | Deployment-specific | Confirm consent and data handling before enabling it |
Local sessions and remote operation use different trust and data boundaries. For remote access, see Network; for external data transfers, see Data Handling.