[Bug] [Frontend] Query History does not persist after browser refresh

[shivambind269-ai]

Summary

The application claims that the last 50 analyses are saved locally and available through Query History. However, after refreshing the page or reopening the browser, previously analyzed queries are no longer visible in the history panel.

Steps To Reproduce

1. Open the QyverixAI application.
2. Paste any code snippet and click "Analyze Code".
3. Verify that the analysis appears in Query History.
4. Refresh the browser page or close and reopen the browser.
5. Check the Query History section.

Expected Behavior

Previously analyzed queries should remain available after page refresh and browser restart, as Query History is expected to be stored locally.

Actual Behavior

Query History is cleared after refresh/reopen, and previously analyzed entries are lost.

Environment

OS: Windows 11
Browser: Chrome
Version: Latest Stable Release

Possible Cause

The history state may be stored only in memory and not persisted to localStorage, or localStorage retrieval may not be functioning correctly during application initialization.

[shivambind269-ai]

Hi Maintainers,

I would like to work on this issue.

I plan to investigate whether the query history is being properly persisted in localStorage and verify the logic responsible for restoring saved analyses after page refresh/reload. I will also add any necessary fixes and testing to ensure the history remains available across browser sessions.

Could you please assign this issue to me?

Thank you!

[naraeingowtham]

hey @imDarshanGK , i'd like to take this one!
looks like the history is probably being kept in memory only and not actually written to localStorage, or maybe it's not being read back on page load. i'll dig into the init logic and get it persisting properly across refreshes.
can i get assigned?

[boss477]

Hi @imDarshanGK! I would like to work on this issue under GSSoC 2026.

Here is my proposed approach to implement history persistence in the frontend:

1. Initialize State:
   • On page load, read query history from localStorage, parse it, and load it into the frontend state.
2. Synchronize & Save:
   • Update frontend/script.js to stringify and write the history array to localStorage whenever a new analysis is added, favorited, or deleted.
3. UI Sync:
   • Verify that the rendered list in the sidebar/history panel accurately reflects the loaded state immediately on startup.

Could you please assign this issue to me? Thanks!