Compatibility & release channels.

01. System requirement

• macOS 26 or later: required to install and run Termy.
• Earlier macOS releases: not supported.

02. Release channels

• Stable — Production-ready. Monthly. Commercially supported; security fixes can ship outside the calendar.
• Beta — Working preview. As needed. Explicit opt-in; known limitations and regressions are possible.
• Labs — Experimental. No promise. No compatibility or support promise; capabilities may change or disappear.

Channels use separate signed update feeds. Change channel in Termy → Settings → About. Stable is the default and the only channel covered by the commercial support promise.

03. Integration maturity

• 1Password SSH Agent — Stable. Termy reads public identities and delegates signing; private keys are never copied.
• Linked OpenSSH config. Hosts linked to an alias refresh their route before each connection and reconnect, including multi-hop ProxyJump. ProxyCommand is unsupported; Match and ProxyCommand commands are never executed.
• Tailscale / MagicDNS inventory — Beta. Local discovery only; Termy stores host metadata, never tailnet credentials or account profiles.
• termyctl portable inventory — Beta. Versioned, size-bounded, secret-free JSON; commands and raw output are outside the schema.

04. Local intelligence

Download a local model in Settings → Intelligence, with download sizes and memory guidance to help you choose one that fits your Mac. The built-in engine runs it on your device without a separate AI server. Apple Intelligence is an alternative when available.

Previously downloaded MLX models cannot run in the new engine. Download a replacement in Intelligence settings; older files remain until you remove them. Companion Intelligence is an optional beta feature with its own model settings.

05. Release rule

A release is compatible only after the same artifact builds for the macOS 26 deployment target and passes clean-install launch testing on supported macOS releases. Signing, notarization, activation, update, and the core SSH path are separate release gates.