Meeting mode
Meeting mode listens to a meeting, writes down what was said, and afterwards turns it into minutes and a list of things to do.
The transcription happens on your computer. The audio does not go to a cloud service.
Starting one
Under the message box in the conversation panel is ⊙ START MEETING MODE, outlined in red. It is red because it turns on your microphone.
A dialog appears and tells you exactly what you are agreeing to:
Meeting Mode records and transcribes everything this microphone hears until you stop it. Transcription runs entirely on this machine — no audio leaves it. Let the people in the room know.
and underneath, in smaller type:
Recording-consent law varies by jurisdiction and is your responsibility.
Both sentences mean what they say. The app cannot know who is in your room or what the law is where you are. Telling people they are being recorded is your job, and in many places it is not optional.
You can give the meeting a title — the field is marked (optional) — then confirm, or CANCEL.
The first time: downloading the model
Because transcription runs locally, a speech model has to be on your machine. If it is not, the dialog says Local transcription required and offers DOWNLOAD MODEL.
Do this before the meeting, not at the start of it. It is a download, and the meeting will have begun by the time it finishes.
Virtual meetings
If you are on a video call, the app tries to capture the application's audio as well as your microphone, so you get everyone rather than just yourself.
For a call it can tap — Google Meet or Microsoft Teams — it says:
This meeting is virtual (Google Meet). [Your apex agent] will also capture Google Meet's audio on this machine — still nothing leaves it.
(The dialog uses your apex agent's own name. The square brackets are ours.)
With a caveat that matters:
Screen capture needs the display awake — if the screen sleeps or locks mid-meeting, I fall back to your side only.
So turn off your screen saver before a long call. A locked screen halfway through means the second half of the transcript has only your voice in it.
For anything else, the app does not pretend:
I can't capture this app's audio yet — I'll hear your side only.
Which is the honest answer, and better to know before the meeting than after.
If screen recording is switched off
Screen Recording permission is off — I can only hear your side; echo cancellation removes the others. Grant it in System Settings → Privacy & Security → Screen Recording, or start anyway degraded.
The detail worth understanding: echo cancellation is why you cannot simply point the microphone at your speakers. Your computer deliberately strips out sound it is playing so that other people do not hear themselves echo. That same cleverness removes the other participants from your recording. Capturing the application's audio directly is the only way round it.
There is an OPEN SCREEN RECORDING SETTINGS button to take you straight there. You can also start anyway and accept a one-sided transcript.
While it runs
The panel shows RECORDING & TRANSCRIBING and a LIVE TRANSCRIPT you can expand or collapse, which says Listening… between utterances.
Keep it collapsed in a meeting. Watching your own words appear is distracting, and so is watching someone else's.
One microphone at a time
Meeting Mode owns the microphone — stop the meeting to talk to the orb.
You cannot hold a voice conversation with your apex agent while a meeting is being recorded. One or the other.
Asking a question mid-meeting
You can still invoke the agent during a meeting using the wake phrase, and there is a setting for how it answers:
When invoked mid-meeting ('Hey Nexus'), [it] speaks its answer aloud. Off = silent text advice in the chat panel only.
Off is the right default for most meetings. Silent advice on your screen is useful. An agent speaking out loud in someone else's meeting rarely is.
See Voice.
Meetings in your calendar
If the app knows about a scheduled meeting, it offers to start recording when the time comes — a card appears in the conversation with the meeting's title and time.
Two useful behaviours are built into that card. Dismissing it means "not this time", not "never" — the scheduled join stays armed until it expires, so dismissing by accident costs you nothing. And the card is only marked handled when a meeting really started — cancelling the consent dialog leaves the offer live rather than burning it.
Afterwards
When you stop, two things are produced: minutes drafted from the transcript, and tasks created from the things people agreed to do, via a CREATE TASKS control so you can look before they appear.
If the drafting fails, the message is specific about what survived:
Minutes drafting failed — the transcript is saved.
Your record is never the thing that gets lost. Minutes can be redrafted from a transcript; a transcript cannot be recovered from nothing.
Past meetings are listed under System Config → Workspace, which says No meetings recorded yet until there are some.
Running something after every meeting
The obvious next step is a workflow that takes what a meeting produced and files it — every client call becoming a summary in that client's folder, without you doing it by hand. Build it as a manual workflow and run it when a meeting ends. See Workflows.
Some versions also list a Call Completed workflow trigger. That one is for telephony, which is not switched on in shipped builds, and it would not fire for a recorded meeting in any case.
Related
- Conversations — where meeting mode starts.
- Voice — microphone modes and the wake phrase.
- Workflows — acting on what a meeting produced.
