Your files · Eavesy

The Mac app saves every capture as a folder of plain files. It's all Markdown, JSON, images and standard audio and video, so any editor, script or agent can read it.

Where they live

Captures go in ~/Eavesy/Recordings unless you change it under Settings → Recordings folder in the Mac app.

Folder names

Each folder is named <date> <title>, using the local date and the title the capture had when it started:

Capture	Folder name
Talk	`2026-06-15 Voice memo`
Meeting	`2026-06-15 Meeting recording`
Video	`2026-06-15 Screen recording`
Clipboard text	`2026-06-15 Note`
Clipboard image	`2026-06-15 Pasted image`
Imported file	`2026-06-15` followed by the file's name

Screenshots taken from the launcher are the exception. Their folder is named Screenshot- followed by an ID.

Folders are never renamed, even after the brief suggests a better title. That keeps paths stable for your scripts and agents. Characters that aren't safe in file names are dropped, and titles are cut at 80 characters.

If a folder with the same name already exists, Eavesy adds the start time, like 2026-06-15 Meeting recording (14-30). A third one the same minute gets (14-30-2), and so on. Existing files are never reused.

Recordings

Talk, meetings and videos look like this:

2026-06-15 Meeting recording/
├── summary.md
├── transcript.md
├── notes.md
├── meeting.json
├── audio.m4a
└── screen.mp4

File	What it holds
`summary.md`	The brief. A placeholder until the cloud brief arrives.
`transcript.md`	The on-device text at first, then the cloud transcript.
`notes.md`	Your own notes. Eavesy never writes AI output here.
`meeting.json`	Metadata for scripts and agents.
`audio.m4a`	The audio.
`screen.mp4`	The screen, for videos only.

You can edit summary.md, transcript.md and notes.md in any editor. When you're signed in, your edits sync to your account. Eavesy never overwrites a file you've changed.

meeting.json

{
  "schemaVersion": 1,
  "id": "local-id",
  "remoteMeetingId": "account-id",
  "title": "Design review",
  "date": "2026-06-15T15:00:00+00:00",
  "startedAt": 1781535600000,
  "durationSeconds": 1820,
  "source": "mixed",
  "status": "complete",
  "files": {
    "audio": "audio.m4a",
    "video": null,
    "summary": "summary.md",
    "transcript": "transcript.md",
    "notes": "notes.md"
  }
}

Field	Meaning
`schemaVersion`	The format version. Currently `1`.
`id`	The ID on this Mac.
`remoteMeetingId`	The ID in your account, or `null` if it hasn't synced.
`title`	The current title, which may differ from the folder name.
`date`	When it started, as an ISO 8601 timestamp.
`startedAt`	When it started, in milliseconds since 1970.
`durationSeconds`	Length in seconds.
`source`	`mic` for Talk, `mixed` for a meeting, `screen` for video.
`status`	Where processing is, for example `processing` or `complete`.
`files`	The file names in this folder. `audio` or `video` is `null` when absent.

If you build on meeting.json, ignore fields you don't recognize. New fields may be added.

Screenshots, clipboard and notes

These folders hold one file and a capture.json:

2026-06-15 Note/
├── note.md
└── capture.json

The file is note.md, image.png or screenshot.png. Imported files keep their extension, such as image.jpg or audio.mp3. Imported audio and video stay on your Mac. When you are signed in, notes, screenshots and images are also uploaded so your other signed-in Macs can show them.

Recordings from the browser

When the Mac app is signed in, recordings you make on the web are copied into the same folder with their transcript and brief. Their audio is not downloaded.