FAQ
The questions worth answering before you install.
Meeting Pulse is small enough that the boundaries matter. Here they are in plain language.
What does Meeting Pulse tell a viewer?
The viewer shows a small availability state such as “In a meeting,” “Call okay,” “Meeting status unavailable,” or “Not connected.” It does not show meeting titles, URLs, participants, audio, video, or screen contents.
Does Meeting Pulse read my calendar?
No. Calendar access is not required. Meeting Pulse detects supported call states through macOS Accessibility APIs on the owner’s Mac.
Does it record my meetings?
No. Meeting Pulse does not use Screen Recording, screenshots, OCR, audio, or video for this product surface.
Which meeting apps are supported?
The current product is designed around Google Meet in Chrome and native Slack Huddles. Read the release notes and project documentation for the current implementation boundaries.
Why does the app need Accessibility permission?
The owner app uses macOS Accessibility APIs to look for supported application states. The permission is for local detection, not for publishing the contents of a meeting.
Is the viewer realtime?
No. The owner and viewer exchange updates periodically. Meeting Pulse makes stale and unavailable states visible so a viewer is not given false certainty.
Can the owner set a status manually?
Yes. The owner can use manual Busy or Available controls for a duration, and can set a separate Call okay signal.
Is Meeting Pulse open source?
Yes. The project is MIT licensed and its source, product decisions, issue tracker, and contribution paths are on GitHub.