feat: isolate session history per Qoder CLI edition - #29
Merged
Conversation
Session metadata in .qoderian/sessions mixed conversations from both CLI editions, so switching editions left the other edition's sessions visible in the history list even though their message files live under a different config root (~/.qoder vs ~/.qoder-cn). - Stamp SessionMetadata/Conversation with the owning edition on create and save; updates keep the original stamp - Filter the conversation index by the active edition; legacy metadata without a stamp stays visible unless its jsonl provably lives under the other edition's projects root - One-shot startup migration attributes legacy metadata by history file location; sessions missing everywhere stay unstamped for re-evaluation - Switching editions force-closes every open tab before activating the new edition so no previous-edition conversation stays open (closing the last tab spawns a blank one), then rebuilds the conversation index - Add edition-aware session path/existence helpers and unit tests Co-authored-by: QoderAI (Qwen 3.8 Max) <qoder_ai@qoder.com>
luoxuanzao
force-pushed
the
feat/session-edition-isolation
branch
from
August 17, 2026 16:54
06c10a0 to
6134a31
Compare
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.
Summary
.qoderian/sessionsmixed conversations from both CLI editions, so switching betweenqodercli(global) andqoderclicn(cn) left the other edition's sessions visible in the history list even though their message files live under a different config root (~/.qodervs~/.qoder-cn).Verification
npm run typechecknpm run lintnpm run test(3335 passed)npm run buildnpm run release:checknpm run audit:prod(0 vulnerabilities)Safety
CHANGELOG.md