Composer

The composer is the box you type in. Almost everything below is one keystroke, and most of it is invisible until you know it is there.

If you only learn two, learn @ and ↑.

Getting files in

Three ways, and you never have to aim:

• Drag a file onto the chat. Anywhere on it, not a small target.
• Click the + to the left of the input and pick from disk.

Each chip carries the icon of its own format, so a spreadsheet, a PDF and a screenshot are told apart without reading the names.

When attachments outgrow the row they collapse into a N more pill. Hover it to peek at the full list, click to keep the list open, and the bin icon there clears every attachment at once.

• Paste. Images, screenshots, and documents go straight into the composer.

In the desktop app, ⌘⇧2 (Ctrl+Shift+2 on Windows) grabs a region of the screen straight into the composer, so you never touch a Downloads folder.

Letting Fluso capture the screen

macOS guards screen capture, and the first ⌘⇧2 is spent asking rather than capturing. What happens, in order:

From then on ⌘⇧2 draws the crosshair straight away.

Watch the whole thing, once

If a press does nothing at all and no dialog appears, the shortcut is being taken by another app before Fluso sees it. Type @ and use Take screenshot instead, or give the shortcut away in that other app.

And a fourth, for files that are already here. Drag a file out of the conversation above, or out of the files panel, and drop it back on the composer to use it again in the next message. Nothing uploads a second time: the file is already on the server, so only its address travels, and the chip arrives ready. The composer's border traces itself while such a drag is in flight, which is how you know it is the target.

The @ menu

Type @ and the composer offers what it can reach: files from this conversation, files in the project, and prompts you saved. Attaching a file this way reuses the copy already on the server, so nothing uploads twice.

Search works two ways. Type part of a name (@quarterly), or type a format (@pdf, @xlsx, @png) to filter by file type.

Two actions live in the menu itself, so an empty project is not a dead end: Upload from computer opens the file picker, and Save prompt stores whatever is currently in the composer.

The whole menu is keyboard-only if you want it: ↑ ↓ to move, PgUp PgDn to jump, Enter or Tab to accept, → to reach a row's delete control, Esc to close without losing your caret.

Saved prompts

A prompt you write twice is a prompt worth keeping. ⌘⇧S files the current draft straight into the library without opening anything; the same thing sits in the @ menu as Save prompt when you would rather see it happen. Either way it joins the Prompts section, and selecting it inserts the text, so you can edit before sending.

⇧ is not decoration there. Plain ⌘S is the save every other site trains you to press, so it stays out of the way.

Recent files

The @ menu carries a Recent files row that starts folded away. Press ⏎ on it and the files you have attached lately appear as a strip you can pick from, without knowing where any of them live. It stays open until you fold it back.

Bringing back what you already sent

Press ↑ in an empty composer and your last message comes back. Keep pressing to walk further back. A counter above the input tells you where you are and when that message was sent.

Attachments come back with the text. If a file has since been deleted, its chip says so instead of failing silently.

↓ walks back towards the present, and the last step returns the draft you were half-way through writing. Esc leaves history where it is.

History keeps the last 50 prompts per thread for three days, and goes away when the chat does. The first message of a chat you have only just started counts too, so ↑ works before there is any history to speak of.

While Fluso is working

The composer stays live during a run. Press Enter and the message joins a queue above it rather than waiting on your patience. Rows can be edited in place (Enter saves, Esc cancels), sent immediately, or dropped.

See Chat for how the queue behaves across reloads, stops, and failures.

How hard Fluso thinks

The mode button on the composer toolbar sets reasoning effort for the current chat. ⌘\ (Ctrl+\) cycles it without leaving the keyboard.

The choice belongs to the chat, not the app, so a quick lookup and a long refactor can sit side by side in your sidebar at different settings. In confidential mode the reasoning level is fixed, so Max is not offered there.

What Fluso may do on its own

Beside the mode button, one control sets how much Fluso does before checking with you. ⌘⇧\ steps through the three levels.

Your choice sticks as the default for new chats. Approvals and permissions covers the approval cards, saved tool rules, and what an organization policy can override.

Dictating

⌘D starts and stops dictation, mid-sentence if you like. Voice notes play back with a real waveform, a scrub bar, and a timecode, so you can check what was captured before sending.

Looking at what you attached

Click a file chip and it opens in a preview panel on the right. Images, PDFs, Word documents, spreadsheets, audio, and video all open full screen, and Esc closes it.

Spreadsheets open as a grid, not a screenshot of one: search across cells, switch sheets by tab, drag column edges to widen them.

In the desktop app, a preview can reveal the original file in Finder or Explorer.

Finding the shortcuts

An empty composer rotates through short hints. Every one of them maps to something that actually works.

Hold ⌘ and each toolbar control labels itself with its own shortcut. Hold it, rather than tap it: there is a short dwell before the labels appear, so every ordinary ⌘-something you press does not flash the whole interface at you.

⌘I opens the full map: composer, @ menu, queue, files, editor, sidebar, mouse gestures, and the single-key commands inside every menu.

Keyboard reference

Next

Chat is what the composer sends into: how a turn is assembled, how the follow-up queue behaves, and what happens while Fluso is working.