[BUG] claude.ai iOS voice chat: session ceiling fires with audio-only warning (or no warning) — limit undocumented, mechanism unknown

Platform: iOS mobile app, claude.ai voice chat
Subscription: Max
Reproducible: Yes (confirmed on two separate sessions, same day)

---

What happened

Two voice chat sessions on iOS terminated with forced cutoffs on the same day, behaving differently from each other:

Session A ("Claiming founder and CTO status"): ~58 minutes of active voice conversation. Near the end, the app delivered an audible "we only have two minutes left" warning, then cut the session mid-sentence. The warning does not appear anywhere in the conversation transcript. No visual indicator was shown.

Session B (stochastic processes): 43 minutes of continuous voice conversation. Session terminated mid-word with an audible blip. No countdown warning, no visual indicator, no transcript entry.

What I expected

Either no hard ceiling, or a visible, logged warning with enough lead time to wrap up — not an audio-only countdown that disappears from the record, and not a silent mid-word cutoff with no warning at all.

Why this is worse for voice

In a text session, a cutoff is at least visible on screen. In voice, the session stops recording while you're still speaking. You don't know it happened until you look down. The "we only have two minutes left" warning in Session A was the only signal, and it existed only in the audio channel.

What the data rules out

I log all claude.ai sessions locally and can characterize the failure precisely. From the three days prior, multiple voice sessions completed without hitting any ceiling:

| Session | Active block | Outcome |
|---|---|---|
| App store economics | 54 min | natural end |
| AI deployment paradox | 58 min | natural end |
| Excire Foto | 60 min | natural end |
| Cursor acquisition | 76 min | natural end |

A 76-minute session completed cleanly. This rules out a simple 60-minute wall-clock limit. The limit is not turn-count either — Session A had 88 total messages, Session B had 102, both terminated. Without access to per-session token counts (which the claude.ai API does not surface to clients), the actual constraint is not determinable from outside.

Two distinct bugs

1. Warning is audio-only. The "we only have two minutes left" message in Session A was not transcribed, not shown in the UI, and left no trace in the conversation record. A user who wasn't looking at the screen — the normal condition during voice use — gets one chance to hear it, then it's gone.

1. Warning fires inconsistently. Session B, which ran longer by turn count, received no warning at all — just a cutoff blip. The two sessions appear to have hit the same ceiling via different code paths.

Not a duplicate of

• #64211: session cut with no warning — that's Claude Code CLI, credit-limit triggered, Windows. Different product, different trigger.
• #55053: 5-hour session window depletion — also Claude Code CLI, not iOS voice chat.
• #61370: voice mode captures no audio — macOS desktop audio capture regression, unrelated.

Request

1. Document the limit (whatever unit it actually measures — tokens, time, or something else)
2. Show a visible in-app warning, not just audio, with enough lead time to finish a thought
3. Log the warning as a system message in the transcript so users have a record
4. Investigate why Session B received no warning — the graceful path should always fire