10:42 · Twenty-two minutes in
“Sam, what do you think? Should we move the launch to Monday?”
Ana Petrova · Launch sync · Google Meet
You were there. Camera on, nodding. But for the last four minutes you were in Slack, answering something that felt urgent. Now four faces are waiting, and you have no idea what “Monday” is about.
01 On your Mac, the whole time
It was listening.
Nobody saw it.
You pressed ⌥⌘E when the call started. Since then, Earshot has been writing down the meeting in a see-through window floating over the call, words appearing as people speak.
- Your micis you.
- Your Mac's audiois everyone else, the same sound you hear.
- On this MacParakeet turns each sentence into text in about 0.1 s. 25 languages.
No bot joined the call. No “Earshot Notetaker” tile, no host asking who invited the recorder.
QA found two issues in the export flow, both in the CSV path.
If we fix them tomorrow we can still ship on Thursday.
Support wants a day for the help docs first.
Sam, what do you think? Should we move the launch to Monday?
02 It knew who was talking
Not “Speaker 2.”
Ana.
Earshot tells voices apart by how they sound, and names them from the people on the calendar invite. No browser extension, so it works where your company blocks them.
Name a voice once and Earshot knows it next time. So the notes say who promised what.
On Google Meet, the optional Earshot for Google Meet extension for Chrome, Arc, Brave, Edge and Vivaldi fills in names straight from the call and stops Earshot when you hang up. It talks only to Earshot on your own Mac.
From the calendar invite · 3 people · 2 voices remembered
03 · The cue · 10:42, two seconds later
Your name, a question.
A tap on the shoulder.
You told Earshot your name, and the ways people say it: “Sam, Sammy.” It heard both, and a question mark. So an amber card slid over Slack.
- 1
The question
Word for word, so you answer what was asked.
- 2
Who asked
From the voice, with the name from the invite or a voice it remembers.
- 3
What led up to it
Summed up by Apple Intelligence on your Mac when it's there. Otherwise, the lines themselves.
- 4
An answer to start from
A suggested reply, built from what was said.
04 You answer
You answer
like you never left.
Three seconds of reading. No “sorry, could you repeat the question?”, no scrolling back through a chat you weren't in.
The card stays out of the way of the call, floats over every app, and goes away on its own or with a click.
Sam, what do you think? Should we move the launch to Monday?
Monday works for me. Marko fixes the CSV export tomorrow, QA gets a full pass, and Lena's team gets a day for the docs.
Works for me. I'll have the fix up by noon.
Great. Monday it is.
05 11:00 · The call ends
The call ends.
The words stay.
You leave the call. Once the meeting's time is up and the call goes quiet, Earshot stops on its own, keeps the last sentence, and saves a Markdown file in ~/Documents/Earshot: who was there, a summary with the decisions and action items, the cues you got, every line with a name and a time.
And not one second of sound. Earshot never records audio. Speech becomes text in memory and the sound is dropped within seconds. Nothing is uploaded, because there's nowhere to upload it to.
# Launch sync Tuesday 27 October 2026 · 10:20–11:00 · Google Meet People: Ana Petrova, Marko Ilievski, Lena Hart, You ## Summary The launch moves to Monday so QA gets a full pass and support has a day for the help docs. ## Decisions - Launch on Monday instead of Thursday. ## Action items - Marko: fix the CSV export by noon tomorrow. - Lena: help docs ready before Monday. ## Cues - 10:42 Ana Petrova asked you: “Should we move the launch to Monday?” ## Transcript 10:41 **Lena Hart:** Support wants a day for the help docs first. 10:42 **Ana Petrova:** Sam, what do you think? Should we move the launch to Monday? 10:42 **You:** Monday works for me. Marko fixes…
● Saved · 41 KB of text · 0 bytes of audio