Before submitting
Area
apps/web
Steps to reproduce
- Start T3 Code in remote/headless mode.
- Connect from a mobile browser using the remote web UI.
- Open any chat/conversation with at least one assistant/agent response.
- Try to copy a full assistant response.
- Compare this with copying your own user message, where long-press/copy behavior or a copy action is easier to use.
- Try to manually select a long assistant response that requires scrolling.
Expected behavior
Assistant/agent messages should have an easy, mobile-friendly copy action, for example a small copy icon/button on the message, similar to other chat apps and similar to the existing user-message copy behavior.
The action should copy the full assistant response text without requiring manual text selection.
Actual behavior
On mobile web, copying assistant/agent responses is very difficult:
- User messages are comparatively easy to copy via long press or an appearing copy action.
- Assistant/agent responses do not expose an equally easy copy action on mobile.
- Manual text selection is hard on mobile, especially for long responses.
- When selecting across scroll, the browser often selects unrelated UI as well, including navigation/header/sidebar content, making the copied text messy.
There was a previous feature request for adding copy actions to assistant responses, and it appears to have been closed as completed:
#1455
This issue is specifically about the mobile web / remote web UX, where the copy action is either missing, not discoverable, or not usable enough for assistant messages.
Impact
Major degradation or frequent failure.
This is especially painful for remote/headless usage from a phone, where users often need to copy agent output into GitHub issues, prompts, docs, chats, or terminal commands.
Version or commit
T3 Code 0.0.24 (latest npm release as of 2026-05-25), run via npx t3 serve --host 172.18.0.1 --port 35489 --no-browser
Environment
- T3 Code mode: remote/headless server
- Server OS: Ubuntu 24.04.4 LTS (x86_64)
- Server Node.js: v24.15.0 (via nvm)
- Client: Android phone
- Browser: Chrome mobile
- Connection: LAN URL with token
Logs or stack traces
No relevant server-side errors. This appears to be a UI/UX issue rather than a backend failure.
Screenshots, recordings, or supporting files
No recording yet. Repro should be visible by opening a long assistant response on mobile web and trying to copy the full response.
Workaround
Use a desktop browser / desktop app, or manually select text on mobile. Manual selection is unreliable for long messages because it can include unrelated page UI.
Before submitting
Area
apps/web
Steps to reproduce
Expected behavior
Assistant/agent messages should have an easy, mobile-friendly copy action, for example a small copy icon/button on the message, similar to other chat apps and similar to the existing user-message copy behavior.
The action should copy the full assistant response text without requiring manual text selection.
Actual behavior
On mobile web, copying assistant/agent responses is very difficult:
There was a previous feature request for adding copy actions to assistant responses, and it appears to have been closed as completed:
#1455
This issue is specifically about the mobile web / remote web UX, where the copy action is either missing, not discoverable, or not usable enough for assistant messages.
Impact
Major degradation or frequent failure.
This is especially painful for remote/headless usage from a phone, where users often need to copy agent output into GitHub issues, prompts, docs, chats, or terminal commands.
Version or commit
T3 Code 0.0.24 (latest npm release as of 2026-05-25), run via
npx t3 serve --host 172.18.0.1 --port 35489 --no-browserEnvironment
Logs or stack traces
No relevant server-side errors. This appears to be a UI/UX issue rather than a backend failure.
Screenshots, recordings, or supporting files
No recording yet. Repro should be visible by opening a long assistant response on mobile web and trying to copy the full response.
Workaround
Use a desktop browser / desktop app, or manually select text on mobile. Manual selection is unreliable for long messages because it can include unrelated page UI.