# Supported platforms

## Desktop Packages

| Platform | Architecture | Distributed package |
|---|---|---|
| macOS | Apple Silicon (`aarch64`) | `.dmg` |
| macOS | Intel (`x86_64`) | `.dmg` |
| Linux | `x86_64` | `.AppImage`, `.deb`, `.rpm` |
| Windows | `x86_64` | `.msi`, setup `.exe` |

Desktop packages are currently unsigned. macOS and Windows may display an
unknown-developer warning; verify the release checksum before opening them.
Linux targets Ubuntu 24.04+ or a current RPM-family distribution with GTK4 and
WebKitGTK 6.0. Other operating systems and architectures are not represented by
v1.3.0 release packages. The macOS deployment target is 12.0 or later.

Package upgrades preserve the existing `com.matt.reticle` application-data
location. AppImage upgrades replace the AppImage file; native installers can be
installed over the previous version. On Windows, do not switch between the MSI
and setup EXE during an upgrade.

## Team Daemon

The documented v1.3.0 production path is a customer-operated Linux host using
systemd and a Caddy reverse proxy. The licensed artifact and architecture are
specified in the applicable order; do not assume an unlisted Team build is
available. Confirm the target distribution, architecture, libc/runtime needs,
and checksum before deployment. Team release builds produce static Go binaries
for Linux amd64, arm64, and armv7. External check tools such as `curl`, `jq`, and
`ssh` are installed separately on the daemon host.

## Execution Capability

| Capability | Platform condition |
|---|---|
| HTTP checks | System `curl` on the Reticle process PATH and network reachability; `jq` for JSON predicates |
| Remote SSH checks/actions | Requires a compatible system `ssh` client and configured non-interactive authentication |
| Local `shell.command` checks/actions | Unix only; requires `bash` |
| Desktop interactive SSH/kubectl shell | macOS/Linux Desktop only; requires the corresponding local tools/configuration and workspace trust. Not implemented on Windows. |
| Team browser/ad-hoc shell | Not supported on any platform |

## Browsers And Clients

Use a currently maintained browser with WebSocket, session storage, and modern
JavaScript support. TLS termination and proxy compatibility are deployment
responsibilities. JSON and MCP clients should send bearer credentials in the
`Authorization` header rather than query strings.
