Give the agent a task in the composer. Add files, quote a previous response, or include a skill when the task needs more context.
Messages can contain up to 120,000 characters. Longer drafts stay in the composer so you can shorten them or split them into several messages.
Pasting 32 KiB or more of text adds that fragment as a text-file attachment so
the agent can inspect it without filling the model context. A smaller paste also
becomes an attachment when inserting it would exceed the message limit. On a
hardware keyboard, use Cmd+Shift+V on Apple devices or Ctrl+Shift+V elsewhere
to keep a large paste editable in the composer instead.
Attach up to 100 files per message. Each image can be up to 10 MiB, with at most 80 MiB of images in one message. Other files, including videos, can be up to 50 MiB each, subject to the environment's upload support and limit. The agent receives them on the environment's machine. Provider and model limits still apply, including images already in the conversation. A video attachment gives the agent a file path; it does not enable native video input.
Uploads begin when you add an attachment. All uploads must finish before the message can send. Retry or remove a failed upload. On web and desktop, reloading before an upload finishes requires you to attach that file again.
You can drag or paste images into the web or desktop composer. HEIC and HEIF photos are converted to JPEG there and when selected from the mobile photo library; photos over the image limit are also resized to fit. On mobile, you can also send files to T3 Code through another app's system share sheet.
See images and videos for previewing and saving media.
On web and desktop, choose Settings → General → Follow-up behavior to queue
new messages for a later turn or steer the running turn immediately. The setting
applies to this client; already queued messages keep their place. Queued messages
are saved on the server and can be edited, reordered, or removed above the composer.
Cmd+Enter on macOS or Ctrl+Enter on Windows and Linux uses the opposite action:
it steers when your default is Queue and queues when your default is Steer.
Use Cmd+Shift+Enter on macOS or Ctrl+Shift+Enter on Windows and Linux to send
the oldest queued message as a steer. This leaves the current draft intact and
requires an active turn that supports steering. Change
thread.steerQueuedMessage in Settings → Keybindings to use another shortcut.
Press Option+Up on macOS or Alt+Up on Windows and Linux with the cursor at the
start of the composer to edit the most recently queued message. Change
thread.editQueuedMessage to use another shortcut.
Mobile has the same choice under Settings → Follow-ups. While a turn is
running the send button shows which action it will take. Long-press it to use the
other action for a single message, or hold Cmd while sending from a hardware
keyboard. The button only offers Steer when the running agent supports it.
Mobile keeps local copies of draft attachments, so you can preview them and queue messages while disconnected. Uploads resume when you reconnect. Drafts and queued messages survive app restarts. Signing out of T3 Connect keeps that work on your device until you sign back into the same account.
On web and desktop, use Settings → Providers → Models to add an unlisted model with a custom name and options. Only options supported by the provider integration affect turns. Antigravity uses its account catalog and does not support custom models.
T3 Code remembers your provider, model, and model options for new threads. A project's configured model takes precedence; resetting that project setting returns to the remembered selection.
Leaving reasoning level or service tier unset uses the provider's own configuration.
On web and desktop, select text within one assistant response and choose Cite in composer. You can add a comment about the quote and write instructions around it.
Select the quote in a draft or sent message to return to its source. If the source is unavailable or has changed, the saved quote remains readable.
The chip shows your comment when it has one, or a short quote preview otherwise. Use the pencil button to add or change the comment. To remove the citation, place the caret beside its chip and delete it like other inline context. Copying, reloading, and restoring a stashed prompt keep each comment with its quote, and sending tells the agent which words were quoted and which comment you wrote. The quoted text and comment count toward the message limit.
Mobile displays saved quotes and comments, but does not create citations or navigate to their sources.
Press ArrowUp in an empty composer to bring back the last prompt you sent in this thread. Press
ArrowUp again to go further back, and ArrowDown to come forward. Moving forward past the newest
prompt clears the composer. Recall walks the prompts loaded in the thread. Attachments, terminal
context, and other extras from the original message are not restored, only the text you typed. A
composer that holds an attachment or a picked element does not count as empty.
When the composer has text, the arrow keys move the caret as usual. Recall takes over only while
the text is an unedited recalled prompt, with the caret on the first visual line for ArrowUp or
the last visual line for ArrowDown, counting wrapped lines. Editing a recalled prompt turns it
into a normal draft.
On web and desktop, choose Edit from here beneath a sent message to rewind the conversation to before that message. Choose Revert and keep changes to leave workspace files as they are, or Revert files too to restore them as well. File restore is only offered for threads running in a worktree, and it is refused when another thread or agent session also uses that directory, a folder inside it, or a folder that contains it, since restoring would erase their changes. A thread that works in the project directory rewinds the conversation only. The selected prompt and its attachments return to the composer for editing and resending. Any unsent draft stays above the restored prompt.
This removes the selected message and later conversation from the active thread and provider history. It does not undo external actions or separate provider memory. The action is available only when the provider supports rewind.
On web and desktop, press Cmd+S on macOS or Ctrl+S on Windows and Linux to save
the current prompt and its attachments for later. Wait for uploads to finish first.
With an empty composer, the same shortcut restores a single stash or opens the
stash menu when there are several.
Stashes containing uploaded files must be restored in their original environment. Those files are retained for 24 hours. After an upload expires, restore the prompt and use Attach again or remove the missing file before sending.
On supported iPhones with iOS 26 or later, use the composer's microphone to record, then confirm to transcribe. Text is inserted where your selection was when recording started, ready for you to review and edit before sending.
The first use may download Apple's speech model and needs a network connection. Later transcription works offline for that language. Recordings can be up to five minutes long. Canceling, leaving the screen, or an audio interruption discards the recording and preserves your existing draft. While recording, the screen stays awake; it can sleep normally once recording stops.
Transcription runs on your device. T3 Code deletes the temporary audio after transcription or cancellation; only the message text is sent when you submit.
On web and desktop, the composer shows Interrupt while the agent is working and the draft is
empty. Adding text or attachments replaces it with a steer arrow. Click it to send a message into
the active turn, or press Enter on desktop. Hold Cmd on macOS or Ctrl on Windows and Linux to
switch the button to a queue icon. Click while holding that key, or press Cmd+Enter or
Ctrl+Enter on desktop, to queue the message for after the active turn.
Queued messages appear above the composer. Rows show a thumbnail of any attached image alongside the text. Drag a row by its handle to reorder it, use the handle's arrow keys, promote the message to a steer, or remove it.
If the server restarts, saved queued messages keep their order and are held. Press Resume in an empty composer on web or desktop, or Resume queue in the queue sheet on mobile, to continue. You can edit, reorder, or remove held messages without starting them.
The pencil on a queued row opens that message in the composer for editing. The original message stays in the queue until you save, and its row is highlighted while you edit. The message's attachments appear above the text with a remove control, and new images can be added the usual way. The checkmark saves the queued message in place; Cancel on its row leaves it unchanged. Whatever you had typed in the composer before starting the edit is restored afterwards. If the queued message starts or is removed while you are editing, the edit ends: changed content moves into the composer when it is empty, and is discarded otherwise.
Type / for commands or $ to add a skill from the selected environment and
provider. On mobile, both are also available before starting a thread on
New task.
The slash menu also includes skills unless you turn off Settings → General → Show skills in slash menu. Only skills enabled for the provider are listed.
After you add or change skills, plugins, or MCP servers, use Restart agent session in the command palette on web and desktop. The conversation continues, and your next message starts the agent again with the new setup.
Provider commands must start the message to run. T3 Code commands such as
/model and /plan, and skill mentions, work on any line.
Send /compact in an existing conversation to reduce context usage when the
provider supports it. Web and desktop also offer compaction from the context meter.
Context you attach lands where your cursor is, as a chip inside your text: a terminal excerpt, a review comment from a diff or file, a preview annotation, or a file. You can type before and after a chip, move it by cutting and pasting, and delete it like a character. Hover a chip for its brief details. Select a terminal excerpt to open its captured output, or select a review comment, picked element, or preview annotation to open its full details. Chips read as "Terminal excerpt, Terminal 1 lines 3-4" and similar to screen readers.
A pull request appears as its icon and number. Its color reflects whether it was open, draft,
merged, or closed when it was attached. Select it to inspect the captured title and branches,
then choose Open pull request to visit the pull request. On web and desktop, type # to browse the newest
pull requests in the current project's repository. Continue typing digits to filter the recent list
by any part of its pull request numbers. A complete number is also resolved directly, even when that
pull request is older than the recent list. Type a single word after # to search pull requests in
the repository by text. Choose a result to insert it as a chip.
Another thread can be context too. Type @ followed by part of its title to pick one from
the same server, or on web and desktop drag a thread out of the sidebar and drop it on the
composer; a multi-selection drops together. The chip shows the thread's current title and
opens it when selected. Your prompt only carries a reference: the agent reads the thread's
history on demand, so attaching a long thread costs nothing until the agent looks. Attaching a
thread does not change it, and the agent cannot send messages to it unless you ask.
Images keep their thumbnail shelf above the text and also get a chip at your cursor, so you can say exactly which image you mean. Deleting an image chip leaves the image on the shelf; removing the thumbnail asks first when the image is still mentioned in your text, then removes both. Files exist only as chips: deleting a file's last chip removes the file from the message.
Copy text that holds chips and paste it into another draft, in the same thread or another one, and the chips come along with what they point to. Images and files are fetched again from the environment they came from; while that happens the chip shows a dashed outline, and if it cannot complete T3 Code tells you and leaves the chip for you to remove or replace. A chip whose context is no longer available shows the same dashed outline; hover it for what to do.
Copying a message with the copy button, or copying text out of it, gives other apps readable Markdown with a link in place of each chip. Older messages that were sent before chips still show their context. Stashing a prompt keeps its chips and what they point to; restoring brings them back.
On mobile, tap a chip to inspect its content. File references open the current file; attached files show the copy that was attached to the message.
Select a file chip in your draft or a sent message to preview it. Code and JSON use syntax highlighting; Markdown, HTML, CSV, and TSV offer rendered and raw views. Audio files have playback controls. Large text files show a limited preview; save the file to read it in full.
On web and desktop, files open beside the conversation with the same controls as a workspace file: a header row with the view toggle, Copy contents and Save file. On mobile, documents open in the same file screen as workspace files; its menu holds Copy contents, Save or share and Open in file viewer. Pictures, videos and PDFs keep their native viewers, and other document formats such as Word or Pages open in the device's own viewer when it has one. If nothing on the device can show a format, save or share it to open it elsewhere.
Select an image or video attachment or link to preview it. Playback support depends on your browser or device; save an unsupported video to open it in another app.
On web and desktop, right-click media to save it or copy its path or URL. On mobile, touch and hold an image or video thumbnail and choose Save or share. On iOS, return to the thumbnail to open this menu after watching a full-screen video.
File links refer to the environment's machine, including when you connect remotely. Previews use the original file, even outside the workspace. Moving or deleting it can break the preview, so save a copy if you need to keep it.
Follow an agent's file link to read a report or other file outside the workspace. These files open read-only. An HTML file outside the workspace cannot load scripts, styles, or images from neighboring files.
On web and desktop, HTML and PDF files open as rendered pages. Switch an HTML file to source view to read its markup; a link to a specific line opens source automatically. HTML previews cannot access your T3 Code session.
The file viewer recognizes images, HTML, and PDF files by their filename extension,
including filenames or folders containing # or ?.
On mobile, select a PDF attachment or link to open it. iOS uses the native viewer; Android opens a compatible installed file viewer.