Mobile app doesn't render thinking trace from remote Copilot sessions

**Mood:** 😔
**Category:** Bug

The GitHub mobile app doesn't render the thinking / reasoning trace from remote Copilot Coding Agent sessions. The same session viewed on github.com (desktop or mobile browser) shows the full extended-thinking output between tool calls; the native mobile app only shows tool calls and the final response.

This makes it hard to follow long-running remote sessions from a phone — which is exactly the surface where you most want to peek in without booting a laptop. You either see "the agent ran N tools and stopped" with no insight into its plan, or you give up and switch to mobile-browser github.com (which works, per workaround below).

**Repro**
1. Start a remote Copilot Coding Agent session on github.com that triggers extended thinking (any non-trivial task).
2. While it is running (or after), open the same session in the GitHub mobile app.
3. Compare to the same session in mobile browser → github.com.

**Expected:** thinking blocks render between tool calls, same as desktop / mobile browser.

**Actual:** thinking blocks are absent; only tool calls and final response are shown.

**Workaround:** open github.com in Chrome/Firefox on the device instead of the native app.

Originally raised at orgs/community/discussions/197451 — filing here in case the desktop/CLI Copilot team owns part of the wire format. If the mobile client team owns the rendering, please route accordingly.

---
| Field | Value |
| --- | --- |
| App version | (GitHub mobile app version — please fill in before submitting) |
| OS | (Android or iOS ) |
| Theme | (System / Light / Dark) |
| Path | Remote Copilot session view |
| Tenure | (Week N) |

Inizia riproducendo la session remota di Copilot nell'app mobile nativa di GitHub e confrontandola con la stessa sessione su github.com in un browser mobile. Usa una sessione che attivi extended thinking; il lavoro è completato quando nell'app compaiono blocchi di pensiero tra le chiamate agli strumenti, in corrispondenza della visualizzazione nel browser. L'issue non indica file né test e occorre ancora fornire la versione dell'app e il sistema operativo.

Scritto dal modello di indicizzazione a partire dal testo della issue.