You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched existing issues and did not find a duplicate.
I am describing a concrete problem or use case, not just a vague idea.
Area
apps/mobile
Problem or use case
On the mobile app there is no way to paste clipboard text into the integrated terminal. The chat already offers "Copy code" and "Copy message" actions, but after copying a command from a chat code block there is no paste affordance on the terminal screen — neither in the terminal toolbar (esc/tab/ctrl/arrow keys) nor in the terminal menu. Commands can't be transferred from the chat to the terminal, and typing them by hand on a phone keyboard is slow and error-prone.
Steps: open a thread → copy a command from a chat code block → open the thread's terminal → there is no way to paste it.
Proposed solution
Add a paste action to the mobile terminal that writes the clipboard text to the terminal session, exposed as a key in the terminal toolbar and/or an entry in the terminal menu (iOS header toolbar and the Android anchored menu).
Why this matters
Anyone driving an agent from their phone frequently gets shell commands in chat responses. Being able to copy them and run them in the terminal is a core part of that loop; today it is impossible on mobile, while desktop terminals support paste.
Smallest useful scope
A single "paste" action on the terminal screen that reads the system clipboard and sends it as input to the active terminal session. No paste-preview, bracketed-paste handling, or multi-line confirmation needed for a first pass.
Alternatives considered
Retyping commands manually on the mobile keyboard, or switching to a desktop to run them — both defeat the purpose of the mobile terminal.
Risks or tradeoffs
Clipboard reads can fail or be empty (permission prompts, empty clipboard) and should fail quietly or with a small notice. Pasting multi-line text executes each line immediately in most shells, which is standard terminal behavior but worth noting.
This discussion was converted from issue #6394 on August 15, 2026 09:53.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Before submitting
Area
apps/mobile
Problem or use case
On the mobile app there is no way to paste clipboard text into the integrated terminal. The chat already offers "Copy code" and "Copy message" actions, but after copying a command from a chat code block there is no paste affordance on the terminal screen — neither in the terminal toolbar (esc/tab/ctrl/arrow keys) nor in the terminal menu. Commands can't be transferred from the chat to the terminal, and typing them by hand on a phone keyboard is slow and error-prone.
Steps: open a thread → copy a command from a chat code block → open the thread's terminal → there is no way to paste it.
Proposed solution
Add a paste action to the mobile terminal that writes the clipboard text to the terminal session, exposed as a key in the terminal toolbar and/or an entry in the terminal menu (iOS header toolbar and the Android anchored menu).
Why this matters
Anyone driving an agent from their phone frequently gets shell commands in chat responses. Being able to copy them and run them in the terminal is a core part of that loop; today it is impossible on mobile, while desktop terminals support paste.
Smallest useful scope
A single "paste" action on the terminal screen that reads the system clipboard and sends it as input to the active terminal session. No paste-preview, bracketed-paste handling, or multi-line confirmation needed for a first pass.
Alternatives considered
Retyping commands manually on the mobile keyboard, or switching to a desktop to run them — both defeat the purpose of the mobile terminal.
Risks or tradeoffs
Clipboard reads can fail or be empty (permission prompts, empty clipboard) and should fail quietly or with a small notice. Pasting multi-line text executes each line immediately in most shells, which is standard terminal behavior but worth noting.
Contribution
All reactions