Supernormal.

Desktop recording instead of a participant bot

Supernormal now uses a Mac and Windows desktop application to capture conversations without a separate bot in the participant list. It requires an account, a compatible device and microphone and system-audio permissions. Official documentation describes the move from the old extension and Norma to desktop capture; previous instructions should not be treated as the current connection method.

A meeting can be started from a notification, detected automatically or recorded manually. Afterward, transcripts, summaries and next steps are available. Having no visible bot is not permission to record secretly: notify participants in accordance with team rules and the agreement for the conversation.

From a meeting to a brief or email

The current Supernormal also targets agencies that need client materials after discussions. Meeting context can inform a draft email, document, presentation or spreadsheet. Projects limit the discussions used for new work, while templates define its format.

This is useful when decisions have actually been made. If a client merely discussed a possible deadline, AI should not turn it into a promised date. Correct the main notes before generating derived material. Convenient formatting does not replace fact-checking, and an agreed structure does not establish client approval of the content.

Example: prepare a brief after a call

Decide which conversations belong to the project and agree on recording in advance. After the call, check the client's goals, budget constraints and open questions. Then request a brief with separate fields for confirmed decisions and information still requiring clarification.

Check surnames, product names and deadlines against the transcript. Remove assumptions about participants' authority. Before sending the document to the client, check its visual structure and make sure it contains no internal notes from another project. This is an editorial workflow example, rather than a test we performed with Supernormal.

Credits, connections and processing location

There is a free plan with credits and paid team offers. Check current note-taking and content-creation resources, including quotas and available administrative settings. Desktop minimum system requirements matter more than a general statement that it works on Mac or Windows.

MCP is documented for sharing meeting context with other AI tools. It is not cited here as proof of a universal REST API. Desktop capture also does not establish that all subsequent AI processing runs locally. Before connecting a work calendar, check automatic recording, storage, project access and material-sharing rules.

Suitable tasks

• Record supported meetings without a bot
• Prepare a brief from a client discussion
• Draft an email or presentation
• Share context through MCP