---
id: mobile-apps/the-live-chat-swipe-order-should-exclude
title: 'The live-chat swipe order should exclude commanders'
theme: mobile-apps
status: open
created: 2026-08-21
date_source: stated
order: 3
---

**The iPhone app swipes left and right between live chats, and commanders should not be in that order.**

The reason it needs the server's help is that the phone has nowhere to put a tab. The web app solved the
same problem on 2026-08-21 with two tabs inside Live — `Agents (n)` / `Commanders (n)` — and a phone
swiping through a flat sequence cannot do that, so it can only filter if the payload says which rows are
commanders.

**The server side is done and shipped in `2026.08.21.02`.** `GET /chat/live` rows now carry
`isCommander: boolean`, derived server-side from the session's cwd rather than from a database lookup:
every commander shares one directory, so the directory is the answer, it costs no query, and it is already
correct during a commander's first turn before any row exists. `GET /chat/sessions` carries it too.

So the app work is: read the field, drop `isCommander` rows from the swipe sequence, and decide whether
they are reachable at all on mobile or simply absent. A deploy commander appearing between two
conversations you are having is the thing to prevent.

**Owed: a short document for the mobile developer** — the field, where it comes from, and the one caveat
worth stating, which is that a row is `isCommander` from its first turn even before it has a title. The
owner asked for this on 2026-08-21 and said explicitly it should be written against a shipped version
rather than an intended one; that version is `2026.08.21.02`.