Context

Fluent – Two Tabs As Context

Context is what you are working on right now: a browser tab, an app's window, the text you selected. Attach it to a prompt and Fluent answers about your actual page or document, with nothing to copy and paste.

Context works the same way in the Smart Panel and the chat window. For files, see Attachments. For what Fluent should know long-term, see Memory.

Attach

Everything you attach shows as a chip in the prompt. There are three ways to add one:

WayHow it works
@Type @ and a few letters of a name, such as @cal for Calendar. Press Tab to move through the suggestions and Return to pick one, or click it.
+Click + next to the prompt. The menu has Files, Tabs, Apps, Actions, Integrations, Memory, and Variables, with a search field on top.
⌘\` | Adds a chip for the app or browser tab you are looking at. Press it again to remove the chip.
Fluent – Picking Context With @

What each kind of chip adds to your request:

ChipWhat Fluent sends
Browser tabThe page's title, address, and text
AppThe text in the app's window
FileThe file's content, see Attachments
ActionThe action's prompt, inside yours
Integration or toolA pointer for the model to use that integration or tool
Memory groupWhat the group holds, or for a large group, the parts that match your request
VariableThe variable's value

Attach as many chips as the task needs. To leave one out, delete it like a word.

Examples:

SituationAttachAsk
Three product pages openThe three tabs"Compare these in a table: price, weight, battery life."
An email to answerMail, with ⌘\` | "Draft a reply that accepts Tuesday at 3 and asks for the agenda."
A PDF open in the browserThe tab"List every deadline in this document with its date."
A talk to rehearseKeynote"Shorten the presenter notes so the talk fits in 15 minutes."
A folder open in FinderNothing, with the Finder integration on"How many PDFs are in this folder?"

Browser

Fluent – A Firefox Tab As Context

Browser context uses the page title, URL, and page content. Attach several tabs and Fluent reads them together.

Supported browsers include Safari, Chrome, Arc, Brave, Edge, Opera, Vivaldi, Chromium, Helium, Comet, and Firefox with the browsers built on it: Firefox Developer Edition and Nightly, Zen, LibreWolf, and Waterfox. Their beta, dev, canary, nightly, and snapshot builds work too, and so do Brave Origin and Opera GX.

@ and + list the tabs in the front window of the browser you are in, or of the one you used last. For Safari and Chrome-style browsers, macOS asks once whether Fluent may control the browser: allow it, or Fluent can't list that browser's tabs.

The tab you are looking at needs no setup: Fluent reads its whole page. Tabs in the background need browser scripting, which Safari and Chrome-style browsers allow once it is turned on:

  • Safari: Settings → Advanced → Show features for web developers
  • Safari: Settings → Developer → Allow JavaScript from Apple Events
  • Chrome-style browsers: View → Developer → Allow JavaScript from Apple Events

Browser automation, where the Browser integration clicks and types for you, needs it too. Show setup tip in Settings → Context has the same steps.

Firefox and the browsers built on it can't be scripted, so Fluent reads them through Accessibility: the tab in the front window is attached with its whole page, other tabs can't be, and the Browser integration doesn't control Firefox.

Reading the tab in front needs the Accessibility permission in every browser. When it's missing, Settings → Context says so under Enable browser context and offers Allow Accessibility.

Fluent reads a page when you send your request. In Firefox, or without browser scripting, keep the tab showing until then: a tab that has gone to the background sends only its title and address.

A PDF or another document open in the browser, such as a Word, Excel, RTF, or OpenDocument file, is read from the file itself, so Fluent gets the document's full text rather than the viewer around it.

A very long page takes a moment to read: a long article a second or two, the largest pages on the web up to a minute.

Apps

App context is the text in an app's window. Attach the app you are looking at with ⌘\`, or any open app from + or @, where apps are listed by their window title.

Some apps are read in their own way:

AppWhat Fluent reads
MailThe whole conversation of the selected message. The first time, Fluent asks for access to your Mail folder: click Grant Access
NotesThe open note
MessagesThe open conversation
PagesThe document's text
KeynoteThe text of every slide, with presenter notes
NumbersThe selected cells, or the whole table
FinderThe folder the front window shows, with the Finder integration on

For Pages, Keynote, and Numbers, macOS asks once whether Fluent may control the app. In other apps, Fluent reads the text macOS Accessibility exposes in the focused window.

With the Finder integration on, Fluent also knows which folder the front Finder window shows whenever you open it over Finder, so "this folder" works without attaching anything.

If app context comes back empty, check the Accessibility permission first.

Follow-Ups

Everything you attach stays with the chat. Ask a follow-up and Fluent sends the tabs and apps again as they were when you first asked, so the tab can be closed by then, even in a chat you reopen from History. Files stay available as long as they are still where they were on your Mac.

Chips work as links, in the prompt and in sent messages:

  • A tab chip takes you back to that tab, or opens the page again if the tab is gone
  • An app chip switches to the app, and opens it if it has quit
  • A file chip shows a preview of the file

Automatic

Turn these on in Settings → Context if you want context without asking for it:

  • Automatically attach active tab: when the Smart Panel opens over a browser, the tab you are looking at is already a chip in the prompt
  • Automatically attach active app: the same for any other app

The chip is a snapshot: switching tabs or apps after the panel opens doesn't change it. Delete the chip to leave it out of that request. Requests that skip the prompt, such as an action you run by its shortcut, get the tab or app too.

Both settings are off by default.

Ask Fluent, the voice mode, always attaches the app or tab you are in while app or browser context is on. See Voice.

Selected Text Only

Text you select before opening the Smart Panel comes along as the input. To see it as a chip in the prompt, turn on Settings → Smart Panel → Show text selection as attachment.

With Use selected text only on, Fluent adds no app or browser context by itself while text is selected. Chips you put in the prompt are still sent.

Use it for actions that should see only the selection, such as grammar fixes, translation, and rewrites, especially the ones you run by shortcut. Turn it off when Fluent should also consider the page or document around the selection.

Settings

Fluent – Context Settings

Open Settings → Context:

SettingWhat it doesDefault
Enable app contextLets Fluent read app windowsOn
Automatically attach active appAttaches the app you are in when the Smart Panel opensOff
Enable browser contextLets Fluent read browser tabsOn
Automatically attach active tabAttaches the tab you are looking at when the Smart Panel opensOff
Use selected text onlyAdds no context by itself while text is selectedOff
Items shown in suggestions and menusWhich kinds of items @ and + offer, and in what order (Priority)All but Variables
Prioritize active appOver a browser, its tabs come first; over any other app, that app doesOn
Show suggestions while typingSuggests tabs, apps, and the rest as you type, without @Off
Disable suggestion animationsTurns off the animations of the @, /, and # suggestionsOff

Recommended starting points:

  • For editing text with shortcuts: turn on Use selected text only
  • For research: keep browser context on and attach tabs with @
  • For always working on the page in front of you: turn on Automatically attach active tab