Session storage can grow too large.

[etherandrius]

Before submitting your bug report

• I've tried using the "Ask AI" feature on the Continue docs site to see if the docs have an answer
• I believe this is a bug. I'll try to join the Continue Discord for questions
• I'm not able to find an open issue that reports the same bug
• I've seen the troubleshooting guide on the Continue Docs

Relevant environment info

- OS: linux vs code backend / mac VS code frontend running in Chromium.
- Continue version: v1.1.65
- IDE version: VS Code web running in a browser

Description

Continue stores the current session in localStorage. For longer conversations this context can grow too large and hit QuotaExceededError

https://developer.mozilla.org/en-US/docs/Web/API/Storage_API/Storage_quotas_and_eviction_criteria#web_storage

Browsers can store up to 5 MiB of local storage, and 5 MiB of session storage per origin.

My use-case is pretty long conversations and large amount of tool usage. Every so often I get QuotaExceededError and have to clear localStorage.

In the most recent case I had 76 messages before the error was hit.

The biggest culprit seems to be the promptLogs key which stores all the tools and their properties. I have about 30 large tools with complex input schemas and long descriptions. appliedRules key is not helping either.

If I delete the two keys I get a 30x smaller size

[etherandrius]

Attempted fix

• Fix: Remove completionOptions and appliedRules from PromptLog #7338 - removing completionOptions
• Fix: Remove applied rules from chat history #7343 - removing appliedRule text from history

I think that completionOptions and appliedRules should be deleted from history.

[RomneyDa]

@etherandrius thanks for opening this, I merged #7338 and left some comments on #7343.

I'm thinking that I will soon stop persisting the chat history to local storage, since the only benefit it provides is a slightly quicker startup which feels buggy when it refreshes anyways, and it runs counter to a change I want to make that loads sessions for the last workspace. Thoughts on this?

[etherandrius]

@RomneyDa +1 to loading history from disk.