Open Snowman-25 opened 1 month ago
Hi @Snowman-25 , thanks for the writeup here. I just tried using @Open Files
locally and it seems to be working, so I think this may be the root of the issue:
Note, that while I'm running VSCode on my Win11 Computer, my workspace resides on a Unix-Server using the Remote-SSH extension.
Not sure what would be causing that unfortunately since we read files through the IDE to ensure we're pulling from the right filesystem.
Not sure what would be causing that unfortunately since we read files through the IDE to ensure we're pulling from the right filesystem.
Does this imply that unsaved changes/files also aren't visible to @open
?
€dit: I've been testing a bit: If my workspace is local, proper context is given. All open files except for unsaved ones are given as context to the prompt (All 'as-saved-on-disk' versions of the open tabs, to be specific). When the workspace is remote, no remote files are used as context. Local Files (such as config.json) are given.
2nd €dit:
When using @file
, context works correct, even in a remote workspace
Before submitting your bug report
Relevant environment info
Description
@open doesn't send the correct context or sometimes ANY content to the LLM
The Errors about config.json not found in the log output are instances where Continue tried to use config.json as the only context to my prompt, despite having multiple files open and config.json not being the active Tab. Also, the file is existant in that location. Note, that while I'm running VSCode on my Win11 Computer, my workspace resides on a Unix-Server using the Remote-SSH extension.
To reproduce
Log output