Skip to content

disappearing conversation history occurs When using a remote server (WSL2), #2540

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
isCopyman opened this issue Apr 12, 2025 · 4 comments
Labels
bug Something isn't working Issue - Needs Info Missing details or unclear. Waiting on author to provide more context.

Comments

@isCopyman
Copy link

App Version

v3.11.14

API Provider

OpenRouter

Model Used

gemini2.5pro

Actual vs. Expected Behavior

I am using roocode on Windows. I opened a project on Windows with VSCode and also opened a project in WSL2 (connected via SSH) with VSCode.
At this time, if I create a conversation (task) using the VSCode that opened the Windows project, it will be displayed in the history record. I can also find and open it in the VSCode on Windows.
If I create a conversation (task) using the VSCode that opened the project in WSL2, it will be displayed in the history record. I can also find and open it in the VSCode connected to WSL2.

Bug occurred:
However, if I use the VSCode that opened the Windows project and click on the conversation history created in WSL2, I cannot open it, and this history will disappear. Even if I use the VSCode that opened the project in WSL2, I cannot find this conversation. This conversation just disappears like this. Vice versa, the conversation will also disappear permanently.

Detailed Steps to Reproduce

  1. Use vscode to open a Windows folder and then have a conversation in roocode.
  2. Use vscode ssh to connect to the docker container of wsl2, open a project and then have a conversation in roocode.
  3. Use any vscode, enter the conversation history record, and click on the conversation that occurred in another vscode.
  4. At this time, you will find that the conversation has disappeared.

Relevant API Request Output

Additional Context

No response

@isCopyman isCopyman added the bug Something isn't working label Apr 12, 2025
Copy link

dosubot bot commented Apr 12, 2025

The issue you're experiencing with disappearing conversation history when using VSCode on both Windows and WSL2 might be related to a bug or limitation in Roo Code version 3.11.14. Unfortunately, I couldn't find specific information about this issue in the repository or documentation. It might be beneficial to check if there are any open issues or discussions related to this problem on the Roo Code GitHub repository. If not, consider reporting this behavior as a potential bug for further investigation.

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@kverbyob
Copy link

A previous issue with WSL was fixed in 3.10.0: #1829
I found a similar behavior happens when running Roo inside a Docker container: #1972

Check if you can see any errors in the developer console.

@isCopyman
Copy link
Author

Now roocode has introduced task filtering based on the workspace. I need to recheck this issue. I currently cannot display any tasks unless the option "Show tasks from all workspaces" is checked.

@hannesrudolph
Copy link
Collaborator

Now roocode has introduced task filtering based on the workspace. I need to recheck this issue. I currently cannot display any tasks unless the option "Show tasks from all workspaces" is checked.

@samhvw8 any ideas here?

@hannesrudolph hannesrudolph moved this from New to Issue [Needs Info] in Roo Code Roadmap Apr 15, 2025
@hannesrudolph hannesrudolph added the Issue - Needs Info Missing details or unclear. Waiting on author to provide more context. label Apr 17, 2025
@hannesrudolph hannesrudolph moved this from New to Issue [Needs Info] in Roo Code Roadmap May 20, 2025
@hannesrudolph hannesrudolph moved this from Issue [Needs Info] to TEMP in Roo Code Roadmap Jun 3, 2025
@daniel-lxs daniel-lxs added Issue - Needs Scoping Valid, but needs effort estimate or design input before work can start. and removed Issue - Needs Info Missing details or unclear. Waiting on author to provide more context. labels Jun 3, 2025
@daniel-lxs daniel-lxs moved this from TEMP to Issue [Needs Scoping] in Roo Code Roadmap Jun 3, 2025
@daniel-lxs daniel-lxs moved this from Issue [Needs Scoping] to Issue [Needs Info] in Roo Code Roadmap Jun 3, 2025
@daniel-lxs daniel-lxs added Issue - Needs Info Missing details or unclear. Waiting on author to provide more context. and removed Issue - Needs Scoping Valid, but needs effort estimate or design input before work can start. labels Jun 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Issue - Needs Info Missing details or unclear. Waiting on author to provide more context.
Projects
Status: Issue [Needs Info]
Development

No branches or pull requests

4 participants