fix: auto-reset web session on new client chat & make cookie optional with fallback - #28
Open
zenyxx-xd wants to merge 3 commits into
Open
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
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 of Changes
Auto-reset Web Session on New Client Conversation:
x-agent-session,agentIddefaults to'dev-agent'. When a user starts a fresh conversation in OpenCode,FreeDeepseekAPIwas reusing the previouschat_session.idon DeepSeek Web, mixing messages from old sessions into the same Web chat.server.js: if an incoming payload contains zero assistant responses (messages.some(m => m.role === 'assistant') === false),FreeDeepseekAPIrecognizes that the client started a brand new conversation and callsresetRemoteSession(session)so DeepSeek Web creates a freshchat_session.id.Make
cookieOptional with Default Fallback:a.config.cookieis empty ("").server.jswas rejecting accounts withNo valid DeepSeek auth accountsdue to stricta.config.token && a.config.cookiefilters."Cookie": config.cookie || "ds_cookie_preference=%7B%22level%22%3A%22all%22%7D;") and relaxed the stricta.config.cookierequirement inserver.js&scripts/doctor.js, allowing token-only auth to work out-of-the-box.