feat: add history manager to track AI responses and transformations#273
Open
saurondark22 wants to merge 2 commits into
Open
feat: add history manager to track AI responses and transformations#273saurondark22 wants to merge 2 commits into
saurondark22 wants to merge 2 commits into
Conversation
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
1 participant
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.
This PR adds a full history tracking system that lets users browse, search, and reuse their past AI-generated responses and text transformations across sessions.
Changes:
history_manager.py— a dedicated module for persisting and querying history entries with metadata (timestamp, original text, transformed text, provider used, tool applied)ui/HistoryWindow.py— a full scroll able UI window for browsing history, expand-collapse each history entry.WritingToolApp.py— all AI responses and transformations are automatically saved after generationKey features:
Why this matters: Users frequently want to revisit or reuse previous AI outputs. Without history, these are lost once the popup closes sometimes destructive when undo unavailable. This makes WritingTools significantly more useful for iterative writing workflows.
I'll keep this as a draft for now, test it myself, compile a list of quality‑of‑life improvements, and also examine what happens as the history builds up.