SSH Folder SyncEnglish · 简体中文 Visually compare and copy files between a directory on the extension host and a directory on an SSH server. Uses MD5 content comparison, explicit sync directions, and per-connection exclusions. Requirements
Before starting, connect from the extension host's terminal with Create a connection
Compare and choose itemsDirectories appear before files; names use natural sorting. The first two information rows identify both endpoints. Hover to see complete paths.
Uncheck a file or folder to exclude it from copying. Unchecking a folder excludes its subtree. Exclusions persist separately for each connection. Excluded files still participate in comparison and directory status. Rechecking a child under an excluded ancestor removes that ancestor exclusion, which can include its other children again; review the displayed checkboxes before syncing. Refresh rescans without copying. Right-click a file present on both sides to open a text diff. The remote side is a temporary snapshot; editing that snapshot does not upload it. Copy filesUse the view's
Before copying, both sides are scanned again using MD5. Identical files and existing directories are skipped. The confirmation shows the source and destination host/path and item count, including missing directories that must be created. Existing destination files are overwritten. Files absent from the source are not deleted from the destination. Direction is explicit; the extension does not decide which version is newer. Progress shows scan and copy stages. Cancel stops further work when possible; completed copies are not rolled back, and cancellation is not an atomic transaction. Avoid changing files from other programs during comparison/copying. History and Remote SSH workspacesThe initial view lists saved connections, ordered by most recent use. Click to compare; right-click to edit, rename, or delete the configuration. Deleting history never deletes synchronized files. Close returns to history; closing during an operation asks to stop it first. Editing can save offline without connecting. History is stored in “Local” means the machine running this extension. In a Remote SSH workspace this may be the remote extension host, rather than your desktop. History is independent in each extension-host environment. Read both endpoint paths in the confirmation before copying. Existing workspace configuration from earlier development versions is migrated once. Troubleshooting
LimitationsNo deletion propagation, automatic watching, merge/conflict resolution, permissions/ownership synchronization, or resume support. Symbolic links are skipped/rejected. Individual SSH operations time out after 120 seconds. Transfers encode whole files as base64 in memory; this version is intended for small to medium directory trees, not huge files or very large repositories. Windows, macOS, and Linux local hosts use the same code; only the user's Kiro/manual environment and automated core tests have been exercised, not a complete cross-platform integration matrix. DevelopmentOpen this folder in VS Code/Kiro and press F5. There are no runtime npm dependencies or compilation steps. Node.js 22+ is recommended for development.
See PUBLISHING.md for release preparation and CHANGELOG.md for changes. Licensed under MIT. |