Repository navigation
Add a button to regenerate meeting summaries - #27
Merged
tommusrhodus merged 2 commits intoNov 17, 2026
Merged
Conversation
Confirm summary replacement using current instructions, preserve existing content until success, and keep transcript, notes and to-dos unchanged. Refs a8cteam51#24
…del only for that one The Summary tab's toolbar has a Regenerate menu with Regenerate summary and Regenerate to-dos. Each asks first, sends the model only the request for its own part (the summary no longer pays for a to-dos pass it throws away), and replaces only that file. Regenerating the to-dos replaces the whole list, ticked and added ones included, as the confirmation says. Nothing is written if the part was changed elsewhere meanwhile, or if the model's answer is empty or unreadable; the notice says which part failed and Try again retries it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
Pushed 6f59e21 on top of this: Regenerate is now a menu with Regenerate summary and Regenerate to-dos, since to-do instructions can change in Settings too. Each one asks the model only for its own part. Before, regenerating the summary still ran the to-dos request and threw the result away. Regenerating the to-dos replaces the whole list, ticked and added ones included, and the confirmation says so. Tested in a built copy against sample meetings and a stand-in model server: one request per regeneration, only the regenerated file changes, a failure leaves the old one in place, and Try again retries the same part. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.




Summary
Adds Regenerate summary to the Summary tab toolbar, so changing instructions in Settings no longer requires deleting
summary.mdby hand.The action asks for confirmation, then generates a replacement using current instructions. The previous summary stays until a non-empty replacement succeeds. Transcript, notes, existing to-dos, and metadata remain unchanged. If the summary changes during generation, regeneration stops rather than overwriting those edits. Progress, errors, and retry are shown; regeneration controls are disabled without a transcript or while a job is already running.
Closes #24
Verification
swift buildpassed.swift test: 92 tests across 23 suites passed.Manual UI smoke testing is still outstanding, including confirmation/cancellation, busy/error/retry feedback, and missing-transcript states.
Validation details
Compared with trunk at
271c50b58ee0e7f41265406ba67e17f1ee975fb8: two Swift Testing test functions added; no existing tests removed or modified. Existing initial summary generation and retry coverage remains. The final build and all 92 tests passed after the retry-disabled-state correction. That narrow modifier correction was inspected by the implementation lead; the original independent reviews were not rerun.git diff --checkpassed. The committed files are content-identical to the final checked working tree.README documents the new action and preservation behavior. No dependencies or CI jobs changed. Hosted CI has not yet been verified; duration/compute impact is unmeasured. The existing PR workflow builds, tests, and checks shell-script syntax. This PR contains no migrations, release tags, or installed-app updates. No private calendar or meeting data is included.