# Which operator your app works with

{/* Generated by scripts/generate-compat-reference.mjs from src/data/compat/operator-compat.json.
    Do not edit by hand: run `pnpm generate:compat-reference` and commit the result. */}

The app on your phone and the operator behind your airdress are released separately. A store build stays on phones for months while operators move on, so each build is checked against the operator versions in use.
This page is generated from the same matrix as the [compatibility reference](/reference/app-operator-compatibility/), as of **2026-10-29**.

## Airdress Chat 0.8.0 (37)

Live on the App Store since 2026-10-29.

### On operator v0.1.161

Chat works: all 7 chat features are at full level. None of them was measured on this operator version; the levels are read from the code of both sides. These results hold while the operator keeps `federation`, `group_conversations` and `person_mls` as they are today.

**Works:** Notifications while the app is closed, Push-to-talk, Events tab, Home Assistant link, Block and report a person and Publish my name and photo.

**Works with a difference:**

- Agent devices (editor sessions as devices): Not measured, and it needs a measurement before anyone relies on it: a 0.8.0 build shows an agent's join request as a plain device join; its approve path seals the root via root-transfers where 0.10.0 approves by delegation; whether the operator refuses a root deposit for device_class agent is not established from the code read.

**Missing, and what the app shows:**

- Group conversations: New group is hidden; an unknown counterparty kind renders "This version can't show this conversation".
- Location to your own airdress: The settings row says the operator has it off.
- Shells on your own machines: No surface in builds before 0.9.0.
- Places and live location on the map: No surface in builds before 0.10.0.

**Not assessed yet:** Apps on your own machine and Send to a screen.

**If the operator changes a setting:**

- With `person_mls` on, Chat myself moves from full to degraded. An owner device keeps its v2 credential; member devices move to v3.
- With `person_mls` on, People on this airdress moves from full to degraded. Household threads become MLS groups; what a 0.8.0 member's device does is unmeasured.
- With `federation` off, People on other airdresses moves from full to absent. Explained: Nothing answered at \{airdress\}.
- With `group_conversations` on, Group conversations moves from absent to degraded. A group envelope reaches a build with no group model; the unknown counterparty kind should render "This version can't show this conversation" - inferred from the app's strings, not measured.
- With `location_enabled` on, Location to your own airdress moves from absent to full. Assumed; location_track_heartbeat_seconds is served and a 0.8.0 build that finds none beats every 10 minutes.
- With `shells` on, Shells on your own machines stays absent. Nothing drawn; shell_host_linked and shell_attention arrive on the client stream and 0.8.0 should ignore unknown event types - inferred, test owed.

### On operator v0.1.123-hotfix.1

Chat works as far as it was assessed: 5 of 7 chat features are at full level, and People on this airdress and People on other airdresses have no result on this version. 3 of them were measured on this pair; the rest are read from the code or assumed.

**Works:** Block and report a person.

### If you run your own operator

This build has been assessed on operator versions v0.1.123-hotfix.1 to v0.1.161. An operator older than v0.1.123-hotfix.1 has no result here, so expect features to be missing or to fail.
On an operator newer than v0.1.161 the app draws nothing for features it predates and gives no notice about them: this build has no compatibility screen. Update the app when a newer build is on the store.