Fix: Use runtime.normalizePath for file tool path resolution in SSH remotes #438
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.
Problem
File editing tools were using Node.js
path.resolve()to resolve relative paths, which uses local filesystem semantics. For SSH runtimes, this caused incorrect path resolution because paths should be resolved relative to the remote filesystem.Solution
Replace
path.resolve()withruntime.normalizePath()which handles path resolution correctly for both local and SSH runtimes.Changes
file_edit_operation.ts,file_edit_insert.ts, andfile_read.tsruntime.normalizePath()is calledpathimportsTesting