> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aihubmix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Composer: attachments, screenshots, slash commands, and adding messages while running

> How to use the composer: adding attachments and their limits, taking screenshots, slash commands, queueing or steering while a session runs, stopping the turn, and the error area above the message box.

The **composer** is where you give the agent tasks and add requirements. The new chat page and the session page use the same composer. For the project and run environment selection above it on the new chat page, see [New session](https://docs.aihubmix.com/en/cloud/sessions/new-session.md).

## Where this applies

| Form | Support | Notes |
| - | - | - |
| Desktop app | Supported | In sessions running on this computer, files are added as local references |
| Web app | Supported | Sessions running on a device can add only images, not files |
| Mobile web | Supported | **Take a screenshot** is grayed out when the browser does not support screen sharing |

## Parts of the composer

| Position | Control | Notes |
| - | - | - |
| Above the message box | Error area, the request above the message box, queued messages | See below and [Needs your input](https://docs.aihubmix.com/en/cloud/sessions/user-intervention.md) |
| Bottom left | **+** to add files or images | `⌘U` (Windows `Ctrl+U`) |
| Bottom left | Permissions | See [New session](https://docs.aihubmix.com/en/cloud/sessions/new-session.md) |
| Bottom right | Model, reasoning effort | See [Harness and models](https://docs.aihubmix.com/en/cloud/models/harness-and-models.md) |
| Bottom right | Context usage ring | Shown only on the session page. Hover to see the share used. Context is compacted automatically when it nears the limit |
| Bottom right | Dictation | Not available yet; shows **Dictation: coming soon** |
| Bottom right | **Queue / Steer** toggle | Appears while the turn is running and the message box has content; see below |
| Bottom right | Send / Stop this turn | While the turn is running and the message box is empty, it becomes **Stop this turn** |

Keys:

* `Enter` sends, `Shift+Enter` adds a new line.
* While the turn is running, press `Esc` to stop the current task.
* When the message box is empty, press `↑` to edit your last message (when the current agent supports it); see [Messages and session actions](https://docs.aihubmix.com/en/cloud/sessions/messages.md).

## Attachments

### Add attachments

* Click **+** and choose **Upload files or images** or **Take a screenshot**.
* Drag files onto the message box, or paste a screenshot or file directly.

You can send attachments without any text. When the cursor is at the very start of the message box, press `Backspace` twice to delete the last attachment.

### Limits

| Item | Limit | Message when exceeded |
| - | - | - |
| Attachments per message | 10 | **“file name” not added: up to 10 attachments at a time** |
| Single image (PNG, JPEG, WebP, GIF) | 5 MB | **file name exceeds 5 MB. Choose a smaller file.** |
| Other single file (any type) | 25 MB | **file name exceeds 25 MB. Choose a smaller file.** |
| Total attachment size per message | 100 MB | **“file name” not added: attachments can total up to 100 MB** |
| Empty file | Cannot be added | **“file name” is empty** |

Files over a limit are not added, and the rest are added as usual. HEIC, HEIF, and TIFF images are automatically converted to JPEG.

### Whether you can add images and files

When you cannot add them, the corresponding item in the **+** menu is grayed out with the reason:

| Situation | Message |
| - | - |
| The current agent does not support images | **Agent name doesn’t support image attachments yet** |
| The cloud server is not ready yet or needs an upgrade | **Images can be added once your cloud server is ready**, **Your cloud server needs an upgrade to send files**, and so on |
| In the web app, with a session running on a device | Files are grayed out: **For tasks running on your computer, add files in the desktop app**. Images work as usual |

### Attachment states

While any attachment is still uploading, converting, or has failed to upload, the send button is unavailable, with **Send when attachments are ready**.

| State | What you see | What you can do |
| - | - | - |
| Uploading | **Uploading N%** and a progress bar | Wait, or click × to remove it |
| Upload failed | **Upload incomplete** and the reason | Click the retry button, or remove it |
| Converting | **Converting to JPEG** | Wait |
| Cannot convert | **This browser cannot convert this image. Use JPEG or PNG.** | Remove it and use JPEG / PNG instead |
| Local reference | **Local reference** | Send directly |

### Local references (desktop app)

When the session runs on **this computer**, files added in the desktop app are given to the agent as **Local reference**. They are not uploaded and are not counted toward the 100 MB total. Files outside the project folder are copied into the project folder first (showing **Copying to an allowed folder**). If a file cannot be referenced, the attachment shows the reason. Images are still uploaded as usual.

### Take a screenshot

The image captured with **Take a screenshot** in the **+** menu becomes a pending attachment directly:

| Form | Method |
| - | - |
| Desktop app (macOS) | The system's area selection. Press Space to switch to capturing a window, `Esc` to cancel. The first time you capture another app's window, the system asks for screen recording permission |
| Desktop app (Windows) | Captures the screen where the app is |
| Web app | Choose a view in the browser's screen sharing picker, and one frame is captured |

If capture fails, you see **Couldn’t take the screenshot. Try again**.

### Attachments in sent messages

Click an image to view it larger; click a file to download it. Locally referenced files show only the file name and cannot be downloaded.

## Slash commands

Type `/` at the start of the message box to open the command list, and keep typing to filter it. Commands are listed for the current session's project, agent, and run environment, in the groups **Source device · Device only**, **Cloud shared**, **Project**, and **Built-in**.

* Use `↑` `↓` to select, `Enter` or `Tab` to insert, and `Esc` to close.
* Selecting a command only inserts it into the message box; it is not sent directly.
* Commands you cannot use are grayed out with the reason. The most common is **Choose the source device to use this command** (the command is installed only on a specific device, and the session does not run on that device).

To add and manage plugins and Skills, see [Plugins, MCP, and Skills](https://docs.aihubmix.com/en/cloud/integrations/plugins-mcp-skills.md).

## Adding messages while running: queue and steer

While the agent is working, you can keep writing. There are two ways to send (when the session is idle, messages are sent directly):

| Method | Meaning |
| - | - |
| **Queue** | Waits in the queue area above the message box and is sent in order after this turn ends. Each one starts its own turn |
| **Steer** | Inserted into the current turn immediately, and the agent handles it along with the turn |

### How to choose

* The default method is set in **Settings › General**; see "Default method setting" below.
* When the default is queue, a **Queue | Steer** toggle appears next to the send button, and you can switch this one message to steer.
* `⌘Enter` (Windows `Ctrl+Enter`): sends this message with the method opposite to the default.

### When the agent does not support steering

Currently only Claude Code and Codex support steering. With other agents, **Steer** is grayed out and all messages are sent as queued.

### Queue area

Queued messages show above the message box, one per row. Messages queued by a session timer have a **⏰ Timer** label. You see the same queue after refreshing the page or opening it on another device.

| Action | Effect |
| - | - |
| Drag the handle at the start of the row | Reorders messages |
| **Steer** | Inserts this message into the current turn immediately |
| Delete | Withdraws this unsent message |
| **…** › **Edit message** | Edit in place, then **Save** |
| **…** › **Open in side chat** | Moves the text into a side chat draft and removes it from the queue (unavailable with attachments) |
| **…** › **Turn off queueing** | Changes the default method to steer. Queued messages are kept |

### After stopping the turn

* If you clicked **Stop this turn** here: queued messages continue to be sent in their original order.
* If the turn was stopped elsewhere (for example, on another device): the queue pauses, and the queue area shows **Queue paused** and **Send all**. You can also **Send** or delete them one at a time.

## Default method setting

**Messages sent mid-turn** in the **Chat** group of **Settings › General**: **Queue** (default) or **Steer**. This setting is saved to your account and shared by the desktop app and web app.

## Stop this turn

While the turn is running and the message box is empty, the send button becomes **Stop this turn**. Click it or press `Esc` to stop. For what happens after stopping, see [Errors and recovery](https://docs.aihubmix.com/en/cloud/sessions/errors-and-recovery.md).

## Error area above the message box

Errors related to the current session (sending, uploading, network, preview, unavailable source, and so on) all show directly above the message box. Each card has a description and one main action, such as **Retry** or **Sign in**. For each type of error and how to handle it, see [Errors and recovery](https://docs.aihubmix.com/en/cloud/sessions/errors-and-recovery.md).

## FAQ

### What if an attachment keeps showing Upload incomplete?

Click the retry button on the attachment to upload it again. If it fails repeatedly, check your network, or remove it and add it again.

### Why is the send button grayed out?

Usually an attachment is still uploading or converting, or has failed to upload. Wait for it to finish, or retry or remove the failed attachment.

### What happens to queued messages when I click stop?

When you click stop here, queued messages continue to be sent in order. If the turn was stopped elsewhere, the queue pauses, and you need to click **Send all** or **Send** on each one.

### I want steer by default. Why was my message queued?

When the current agent does not support steering, messages are handled as queued automatically. Claude Code and Codex support steering.

### Why is a slash command grayed out?

Check the reason below the command. Most often, the command is installed only on a specific device, and the current session does not run on that device.

## Related

* [New session](https://docs.aihubmix.com/en/cloud/sessions/new-session.md)
* [Needs your input](https://docs.aihubmix.com/en/cloud/sessions/user-intervention.md)
* [Errors and recovery](https://docs.aihubmix.com/en/cloud/sessions/errors-and-recovery.md)
* [Messages and session actions](https://docs.aihubmix.com/en/cloud/sessions/messages.md)
* [Harness and models](https://docs.aihubmix.com/en/cloud/models/harness-and-models.md)
* [Run environment](https://docs.aihubmix.com/en/cloud/projects/run-environment.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.