fix(tui-v2): /continue命令导致丢失新会话记录#552
Open
AiHyo wants to merge 1 commit into
Open
Conversation
AiHyo
changed the title
AiHyo
force-pushed
the
fix/tui-v2-continue-preserve-current-log
branch
2 times, most recently
from
8b13183 to
93e79ff
Compare
AiHyo
force-pushed
the
fix/tui-v2-continue-preserve-current-log
branch
from
93e79ff to
dc9c14a
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.
Context
In
tui v2, a newly started conversation disappears from recoverable history after switching to another session with/continue.The active conversation log is stored on
agent.log_path, butreset_conversation()was snapshotting the PID-based fallback path instead. As a result, when/continuereset the current conversation before restoring the selected session, the newly started conversation was not preserved.Fix
Use the agent's active
log_pathwhen snapshotting the current conversation before reset, while keeping the existing PID-based path as the fallback for older callers.Validation
Completed local testing with
tui v2: started a new conversation A, switched to conversation B with/continue, then used/continueagain and confirmed conversation A remained recoverable.