The bot problem
Recording a meeting
without a bot.
The meeting platforms have started locking recording bots out. If the tool you rely on is a bot, that is your problem too. Here is what changed, and what the alternative actually looks like.
What changed in 2026
Microsoft added bot detection to Teams meetings. Third-party recording bots are now held in the lobby and require an organizer to admit them explicitly; the capability began reaching targeted-release tenants in mid-May 2026 and general availability followed in early June. The stated reasoning is not really about spam — it is about where meeting content ends up. A bot has to move what it hears out of the tenant to process it, which puts your conversation under the bot vendor's privacy policy, in the vendor's jurisdiction, on the vendor's retention schedule.
University IT departments reached the same conclusion earlier and published it plainly — Stanford and Cornell both advise staff away from third-party meeting bots. Corporate blocklists have been spreading for longer than that, quietly: a bot dials in, the security policy leaves it in the lobby, and the person who invited it finds out when the meeting is already over.
Why the bot exists at all
A bot is not a design choice anyone loves. It is what you build when your product is a web service: the service has no way onto the audio, so it joins the call as a participant to hear it. Everything users dislike about bots — the extra name in the participant list, the announcement, the awkward question from a client, the recording that lives in someone else's cloud — follows from that one architectural fact.
It also changes the meeting. People speak differently when a third-party recorder is visibly present. That is not a privacy abstraction; it is the reason the candid part of the call happens after the bot leaves.
The alternative: record the Mac, not the meeting
Your Mac already has the audio. Both sides of it. macOS 14.2 added a
supported way for an app to tap another application's audio output —
AudioHardwareCreateProcessTap — and Heliotype uses it to
capture what the meeting app is playing, alongside your microphone.
Nothing dials in. Nothing appears in the participant list. There is no
bot to detect, admit, or block, because there is no extra participant
at all.
It is an audio-only tap, not screen recording, so the purple screen-recording indicator never turns on and nothing on your screen is captured. When you stop, the recording is named after the meeting on your calendar and a speaker-labeled transcript is written beside it, in a folder you chose.
What that changes, concretely
| Bot-based recorder | Heliotype | |
|---|---|---|
| In the participant list | Yes — a named bot everyone sees | Nothing joins |
| If IT blocks bots | Stops working | Unaffected — there is no bot to block |
| Where the recording lives | The vendor's cloud | A folder on your Mac |
| Who processes the audio | The vendor, under their contract | Your own AssemblyAI account, under your key |
| Works in ad-hoc calls | Needs an invite the bot can join | Any call your Mac plays audio for |
| Cost shape | Per seat, per month, forever | $29 once, plus your own per-hour transcription |
Where a bot is still the right answer
If you need the recording to happen when you are not in the meeting, a bot is the tool — Heliotype records your Mac, so your Mac has to be in the call. If your team needs one shared searchable archive with permissions and admin controls, that is a web service's job, not a local app's. And if you are not on Apple Silicon, this is not for you yet. The full list of what Heliotype can't do is on its own page, in plain language.
If your notetaker just stopped working
- Download Heliotype (Apple Silicon, macOS 15+ to record) and drag it to Applications. It is signed and notarized by Apple, so the first launch is a plain double-click.
- Paste an AssemblyAI key. New accounts include about $50 of credit — more than 200 hours of audio — with no card required.
- Start your next call and click record in the menu bar. Nothing joins. When you stop, the transcript is already beside the recording.