#2158

docs: plan meeting recording and notes that can be added to any Space

DraftDouglasymlaiwants to merge intofrom

Pull Request

Related Issue

N/A — maintainer-directed work; no linked issue required for this PR.

Description

Draft. This branch only adds the plan, docs/meeting-notes-plan.md. The implementation will follow in the pull requests listed in §8 of the plan. It builds on the Apple Intelligence models plan (#2157).

Problem

People hold meetings on Zoom, Meet, Teams or in the room, and then retype what was decided before Eigent can help with the follow-up. Eigent cannot record or transcribe a meeting, and there is no place to keep meeting notes that several Spaces can use.

Approach

  • Add Meetings, a library at the same level as Spaces. A meeting belongs to no Space until the person adds it to one.
  • Record on the Mac without a bot joining the call: the microphone and the Mac's system audio, with a live transcript labelled You / Others and a field for the person's own notes.
  • After the meeting, write a note with a summary, decisions, action items and open questions. On a Mac with Apple Intelligence, this runs on the device by default. People can pick another model, and Eigent says when the transcript would leave the Mac. It never falls back to a cloud model on its own.
  • Add to Space copies the note into the Space's folder as a Markdown file. Sessions can use it like any other file, it shows in Files, and Eigent never overwrites an edited copy without asking. A meeting note can also be attached to a single message, and Start a session opens a new Session with the note attached.
  • Recordings, transcripts and notes stay on the Mac and are not synced. There is a clear recording indicator, a consent reminder before the first recording, retention settings, and no automatic recording.

Testing

Not started. This branch only adds the plan document, which passes the repository's Prettier check. The Apple API details in §3 were checked against the macOS 27.2 SDK. Testing will follow §9 of the plan.

Testing Evidence (REQUIRED)

  • I have included human-verified testing evidence in this PR.
  • This PR includes frontend/UI changes, and I attached screenshot(s) or screen recording(s).
  • No frontend/UI changes in this PR.

Not yet available: the branch currently contains only the plan document.

What is the purpose of this pull request?

  • Bug fix
  • New Feature
  • Documentation update
  • Other

Contribution Guidelines Acknowledgement

Activity

1

This pull request is a draft

Merging is unavailable until it is marked ready for review.