Repository navigation
Conversation
The comparison in Files and Collectives can now summarize the changes between the two versions shown, with the instance's AI provider. "Summarize changes" sits in the comparison's header, on the row of Previous and Next, and says that both complete versions are sent to the AI provider; nothing starts without a click. The summary shows its place in the queue, then a card labelled as AI-generated, with both versions, the gist and the changes grouped by meaning, Copy and collapse. A stored summary of the same two texts shows at once for anyone who opens them. Side by side it spans both documents; in the list of changes it sits above the list. Every state that stops a summary says why and what to do, and a server that does not answer is asked again. The comparison loads both files as bytes, so the texts it fingerprints are the ones the server reads; it fingerprints them only for a summary. The summary code is a separate chunk, loaded only where summaries are on, which pages learn from initial state. The Files sidebar gets "Summarize recent changes": it opens the list of changes from the newest version at least an hour older than the latest change, or the oldest kept one, ready to summarize. Resolves #8904 Assisted-by: ClaudeCode:claude-opus-5-5 Signed-off-by: Hoang Pham <hoangmaths96@gmail.com>
hweihwang
force-pushed
the
feat/version-summaries
branch
from
November 9, 2026 11:36
23bb9c3 to
24eca60
Compare
This branch has not been deployed
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
The comparison can now summarize what changed between the two versions shown, in Files, and in Collectives once nextcloud/collectives#2878 is released. The list of changes already shows every edit; the summary says what the newer version means: the gist in a sentence or two, then the changes grouped by topic, with every changed number, date and name as old and new value.
The comparison now loads both files as bytes, so the texts it fingerprints are exactly what the server reads; the fingerprints are computed only when a summary is asked for. The summary code is a separate chunk, loaded only where summaries are on, which pages learn from initial state without a request. What each state shows, says and when it asks again is one entry per state in
states.ts.🖼️ Screenshots
The whole flow in Files: compare, summarize, change the older version, summarize again, list of changes.
flow.mp4
When it cannot summarize:
The summaries above come from Claude Haiku through integration_openai's OpenAI-compatible endpoint.
🏁 Checklist
npm run lint/npm run stylelint/composer run cs:check)version-summaries.spec.tson core's testing chat provider, in Files and on a phone, and that only an administrator can change the setting🤖 AI (if applicable)