Search the reviewed record
List and search saved meetings, then read one meeting with participant labels, analytics, and an optional reviewed transcript.
Give your chosen AI client read-only access to finalized captions as the active Timeline changes, then translate the same conversation into multiple languages at once, maintain a live brief, or track decisions. Saved meetings, Meeting Analytics, and Voice Notes remain available when you enable them. Turn access off and it stops. MCP is included with NotchLive Pro.
AI Connections is off by default. Enable saved meetings and notes first, then choose whether the active Timeline is also available. Connecting a client does not grant access while the main control is off.
Let the client find reviewed meetings and transcripts, Meeting Analytics, and Voice Notes. Use it to retrieve a decision, compare meetings, or draft a follow-up from saved work.
Once AI Connections is on, a second off-by-default control makes the Timeline currently visible in NotchLive available. Leaving it off limits access to saved content.
NotchLive does not push a meeting into an AI service or start a conversation on its own. The connection to NotchLive is local, but Codex or Claude may send requested content to its model provider according to that client's settings and policy.
Nothing is exposed before you enable the local server in NotchLive Settings.
Saved meetings and notes become available with AI Connections. If you also need the active Timeline, turn on its separate caption control.
When a configured client requests NotchLive context, it can call only read-only tools. Turn access off and the configured client is refused.
NotchLive treats automatic speaker attribution as evidence, not identity. Rename, merge, reassign, split, or leave speech unresolved. Your reviewed participant map, rather than an automatic acoustic guess, is the meeting structure used by analytics, exports, saved output, and MCP results.
See how speaker diarization worksThe server exposes narrow retrieval tools, not control over NotchLive or your Mac.
List and search saved meetings, then read one meeting with participant labels, analytics, and an optional reviewed transcript.
List saved Voice Notes and read the note you ask for without granting access to unrelated files.
Retrieve the active Timeline only when its separate setting is on. No setting means no live-meeting result.
Open NotchLive Settings, go to AI Connections, and use Set Up… for Codex or Claude Desktop. NotchLive writes the local connection for the installed desktop client, so a separate CLI install is not required.
Turn on “Allow AI apps to access NotchLive” to share saved meetings and notes. If needed, separately turn on “Include active meeting captions.” Setup alone does not grant access while the main switch is off.
No. AI Connections starts off, NotchLive never initiates a request, and configured clients are refused until you enable access. Once enabled, the AI app may send requested content to its model provider.
The client still has its local configuration, but NotchLive refuses the connection and returns no meeting data until you enable AI Connections again.
No. The NotchLive MCP server is read-only and exposes no write, delete, rename, recording, microphone, network, or model tools.
No. Active Timeline access has its own separate, off-by-default control.
Yes. When active Timeline access is enabled, Codex or Claude can request each finalized caption and translate the same stream into multiple requested languages. This AI-client workflow is separate from the 20 languages built into NotchLive through Apple Translation.
No. NotchLive can configure the installed Codex or Claude Desktop app directly from Settings.
Use NotchLive for live captions, then explicitly connect Codex or Claude when you want parallel translations, a live brief, or reviewed meeting context.