By Dmytro Barabash, founder of Nod · Published September 1, 2026
The context path
Capture happens through the Mac, the result becomes a summary and transcript in the user's account, and a question retrieves only the material the current user can access. The public connector grant is meetings:read: search, open, and read. It cannot create, edit, delete, or act.
- Conversation capture without an assistant joining the call
- Source-linked retrieval across summaries and transcripts
- Read-only OAuth authorization that can be revoked
- No automatic transfer of meeting content into another assistant
A practical combined question
Once a connector is publicly installable, a user can ask ChatGPT or Claude to retrieve the meeting where a customer discussed a requirement, then reason about that context beside a document, ticket, or email the user has separately connected. Nod supplies the conversation; the assistant supplies the broader reasoning surface.
Availability and data boundary
The connector services are built, but public listing approval is pending. Until the corresponding directory enables installation, do not treat the public connectors as available. After a user connects one, the assistant's own plan, region, workspace controls, retention, and training settings govern the assistant side of the exchange.
Related
Read the connectors overview, Nod for ChatGPT, and Nod for Claude. For the underlying category, start at AI working memory.
Frequently asked questions
What is an AI context layer?
It is a permissioned way for an assistant to retrieve relevant source information instead of relying only on what a user pastes into the current chat.
Are Nod's ChatGPT and Claude connectors available now?
The read-only connectors are built, but public installation is awaiting directory approval. Their pages show the pending state until a listing is approved.
Can the connectors change my Nod data?
No. The public grant is read-only and limited to meeting search and retrieval. It cannot create, edit, delete, or execute work.