[Feature]: Allow native text selection within assistant responses

[fionn77]

Before submitting

• I searched existing issues and did not find a native-mobile request for selecting part of an assistant response.
• I am describing a concrete mobile use case.

Area

apps/mobile on Android.

Thanks for the work on the native mobile app. This request is about making model output easier to reuse on a phone.

Problem or use case

The Android app currently lets me copy an entire assistant response, but I cannot select a specific sentence, command, filename, or short passage from the response.

For a long answer, copying everything and trimming it in another app is awkward. Standard Android long-press text selection with draggable handles would make small pieces of model output much easier to reuse.

Proposed solution

Allow text inside assistant responses to be selected using native mobile selection behavior.

A useful implementation could either:

• make rendered assistant text directly selectable; or
• provide a per-message Select text action that temporarily enters a selection mode.

The existing full-response copy action should remain available. Links, code blocks, expandable tool/result rows, and scrolling should continue to work without accidental activation while selecting text.

Expected behavior

1. Long-press assistant text.
2. Adjust the standard Android selection handles.
3. Copy only the selected passage.

Environment

• Official T3 Code native Android app
• Google Pixel 7a
• Android OS and app/OTA versions not captured

Related issue

#2804 concerns making the full-response copy action usable on mobile web. This request is different: selecting an arbitrary subsection of assistant output in the native mobile app.

I am happy to test this behavior on Android if it is implemented.

[abcumpanici]

@juliusmarminge I’d be happy to contribute a focused Android fix for this, partial text selection would make my day-to-day use much easier. Would you be open to a PR?