Introducing Eavesy for context you can keep

Eavesy keeps the things you would otherwise have to explain again: a conversation, a screen walkthrough, a screenshot, or a note copied from another app. The Mac app saves them as normal files, and you choose what to give your AI assistant.

Choose the capture for the task

Talk records your microphone and can paste on-device recognition into the app you are using. Meeting records your microphone and computer audio. Video adds the screen. Clipboard text, images, and screenshots can also be kept as local captures.

Capturing the screen does not mean a text-only assistant has inspected it. For a visual task, attach the relevant screenshot or use a local agent that can open the image. See the walkthrough guide.

Local files and optional cloud processing

Recording, on-device captions, and on-device dictation can work without an account when the required permissions and recognition are available. Sign in for cloud audio transcription, summaries, and synced access. Processing can finish after you stop, so check that the transcript and brief are complete before using them.

The Mac app keeps Markdown, JSON, and available media in a recording folder. Local screenshots and clipboard notes are not uploaded to the hosted MCP server. You can inspect the files in an editor or copy a brief into your notes vault.

Hand over the evidence deliberately

Paste the relevant text into an assistant, give a local coding agent a permitted file path, or authorize hosted MCP access to supported synced recordings and dictations. These paths have different access boundaries. A path pasted into a browser chat does not upload the file.

Start with a worked example, a copyable template, or the Mac download. Review generated text against its source before treating it as a decision or an instruction.