Skip to content

Feature Request: Add incremental transcript processing for the Local backend so AI notes can be refreshed every 5 min #123

Description

@ari-agent

Add incremental transcript processing for the Local backend so AI notes can be refreshed every 5 minutes during a recording.

User-facing goal:

  1. The app should periodically checkpoint the transcript every 5 minutes while recording.
  2. Each checkpoint should trigger AI notes generation from the new transcript since the last checkpoint.
  3. Notes generation should be incremental, reusing the existing AI notes and only appending/updating with new transcript content from the latest checkpoint.

Done looks like:

  • Local recordings produce updated AI notes without waiting for the recording to stop.
  • The notes remain consistent across multiple checkpoints instead of being regenerated from scratch each time.
  • Users can see the notes evolve during a long meeting with minimal delay or duplication.

Business Context

We already have a Local backend that writes transcript.md and note.md on disk after recording, and the codebase has existing local notes retry/finalize flows plus design docs for on-device transcription and notes generation. This request extends that flow to support long recordings better and reduce the latency gap between transcript capture and useful notes for the Local/offline experience.

Implementation Guidelines

  • Only build the feature or fix the bug described above
  • Do not add root-level documentation markdown unless explicitly requested in the feature description
  • Do not add testing plan documentation unless explicitly requested in the feature description
  • Focus on delivering the user-facing functionality described above

Activity

  1. ari-agent commented on Jun 18, 2026

    @ari-agent
    Author
  2. self-assigned this
    on Jun 18, 2026
  3. ari-agent commented on Jun 19, 2026

    @ari-agent
    Author

    Yeah — summary quality is the whole game here. The bar I’d push for is concise, specific, and structured by meeting intent, with decisions, risks, and next steps front and center instead of a mushy paragraph of AI prose.

  4. removed their assignment
    on Jun 30, 2026
  5. added theissue type on Sep 13, 2026
  6. shawnzhu commented on Sep 13, 2026

    @shawnzhu
    Contributor

    /shape

  7. self-assigned this
    on Sep 13, 2026
  8. github-actions commented on Sep 13, 2026

    @github-actions
    Contributor

    🤖 Design spec ready for review: #403

  9. added a commit that references this issue on Sep 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions