What version of the VS Code extension are you using?
0.4.0
Which IDE are you using?
VS Code
What platform is your computer?
Linux 6.15.7-200.fc42.x86_64 x86_64 unknown
What steps can reproduce the bug?
When using a Multi-root Workspace, codex is unable to locate files in any folder other than the first. The image shows the extension is able to resolve the relative file paths (see the highlighted links to my_script), but codex does not see the file. If you grant Full Access to the Agent, it can sometimes navigate the file system and find the script, but that's a slow and unreliable mechanism considering the extension has already identified the correct file.
What is the expected behavior?
The extension should submit the full path of the current active file instead of submitting a relative path that codex does not understand.
What do you see instead?
Codex is unable to find the active file.
Additional information
These are related: #471 , #2797 and are discussing support for multiple folders. That is also a nice enhancement and would be needed for full multi-root workspace support. However, given that codex is currently limited to a single folder, it is a bug that the vscode extension is sending relative paths that codex does not understand.
What version of the VS Code extension are you using?
0.4.0
Which IDE are you using?
VS Code
What platform is your computer?
Linux 6.15.7-200.fc42.x86_64 x86_64 unknown
What steps can reproduce the bug?
When using a Multi-root Workspace, codex is unable to locate files in any folder other than the first. The image shows the extension is able to resolve the relative file paths (see the highlighted links to
my_script), but codex does not see the file. If you grant Full Access to the Agent, it can sometimes navigate the file system and find the script, but that's a slow and unreliable mechanism considering the extension has already identified the correct file.What is the expected behavior?
The extension should submit the full path of the current active file instead of submitting a relative path that codex does not understand.
What do you see instead?
Codex is unable to find the active file.
Additional information
These are related: #471 , #2797 and are discussing support for multiple folders. That is also a nice enhancement and would be needed for full multi-root workspace support. However, given that codex is currently limited to a single folder, it is a bug that the vscode extension is sending relative paths that codex does not understand.