apps/mobile
Back returns to the thread the pull request was opened from.
Back lands on the Pull Requests list. Opening the PR replaces the chat's back stack, so the thread is gone from history and has to be found again.
Major degradation or frequent failure
Current Android release
Android app
Fix in progress: #18839 (contextual PR links preserve the chat history). It is currently conflicting with main and has had no activity since 2026-10-21. iOS behavior is out of scope for that PR.
I’m also experiencing this in the Android app:
Both return me to the Pull Requests tab instead of the originating chat. Back should return to the same thread so I can continue the conversation.
Additional real-device reproduction from an Android user, consolidating duplicate #33404. This report is intentionally text-only because the user's screen captures contain sensitive information.
Opening a pull request link from an agent's reply switches T3 Code from the current thread into its internal Pull Requests viewer. Pressing Android's system Back then returns to the Pull Requests list, rather than the thread the link was opened from.
This occurs on both the front display and the expanded inner display of the reporter's Samsung Galaxy Fold 7. The layouts make the same navigation failure look different: the front display shows a full PR list, while the expanded display shows that list on the left and an empty PR detail pane on the right.
The reporter explicitly tested this on the front display; this is not merely a narrowed view on the expanded display.
This empty PR detail state is what the reporter initially described as a blank screen. The front-display test clarifies that both layouts return to the PR list rather than the conversation.
When a PR is opened from a link in a thread, Android's system Back should return to that same originating thread, in the same environment, so the user can continue the conversation.
The return destination should remain the originating thread in both phone and expanded layouts, without requiring the user to remember or search for the thread's name.
| Display/layout | Destination after Android system Back | Result |
|---|---|---|
| Front display, folded phone | Pull Requests list | The originating thread is no longer displayed. |
| Expanded inner display, sidebar/detail layout | Pull Requests list in the left sidebar, with an empty PR detail pane on the right | The originating thread is no longer displayed. |
The reporter has to find and reopen the thread manually. If they do not remember its name, they lose their place and struggle to resume the conversation.
Major degradation or frequent failure. The reporter describes this as recurring throughout normal mobile use. Following an agent's PR link to inspect work repeatedly breaks the return path to the conversation that provided the link.
No exact reproduction rate was measured. The report concerns losing the navigation context; it does not establish deletion of the thread or its messages.
Exact app version/build not provided. The observed interface is branded T3 Code BETA.
The reporter suspects the bug is not specific to this phone model. Both configurations above were tested on the same device; no cross-device reproduction is claimed.
The reporter supplied screenshots of the expanded-display sequence and a short recording of the front-display sequence privately. Screenshots and video are not included in this public report because they contain sensitive information.
The steps and observations above describe the reporter's real-device tests. The reporting agent has not independently reproduced the issue on a separate device or build.
Not available. No root cause has been confirmed.
Manually return to the thread list, find the original conversation, and reopen it. This is difficult when the user does not remember the thread's name.
