Mobile: mid-turn assistant messages collapse into the tool-activity chip, so the final message can read as missing its context
Environment
- Claude Code session viewed in the claude.ai/code mobile client (iOS), session also active in desktop CLI
- Model: claude-fable-5
What happened
During a long agentic turn (multiple tool calls: log queries, a bug diagnosis, an edit, a commit/push), the assistant's brief between-tool-call narration — the connective tissue like "two new comments landed, one is a real bug: X reported Y" and "traced it to the manifest's orientation field" — is collapsed on mobile into the tool-activity chip ("Ran 6 commands, used a tool, read a file +6 -3").
The final text message of the turn then opened with "Fixed and pushed (7892bb2…)" — which assumed the reader had seen the discovery-and-diagnosis narration. On the phone, none of that was visible, so the reply to my question ("how's traffic?") appeared to begin mid-story with the fix for a bug I'd never been shown.
My reaction as a user, verbatim: "i think you're having conversations with yourself and only sending me the last part."
Expected
Either:
- key mid-turn assistant text (not tool output — the model's own narration between calls) stays visible on mobile rather than being folded into the activity chip, or
- the collapse is fine, but then the product/harness guidance should push models to make each turn's final message fully self-contained (mine recovered by re-explaining when asked — the info existed, it just wasn't surfaced).
Repro sketch
- Ask the agent something simple while it's mid-workstream (background monitors firing, multi-step turn follows).
- Let it discover a new issue mid-turn, narrate briefly between tool calls, and finish with a result-focused final message.
- View on mobile: the narration is inside the collapsed chip; the final message references context you never saw.
Why it matters
On desktop the interleaved narration reads fine, so the model gets no signal anything is wrong. On mobile the same transcript reads as non-sequitur replies, and the user has to ask the agent to repeat itself — the summary exists but lands in the collapsed section.