fix(remote-sync): scp-only remote sync — no rsync on remotes#260
Merged
Conversation
Remote Data Sources no longer call rsync, which required rsync on both the dashboard host and every remote. Sync now uses recursive scp over OpenSSH (zero extra packages on remotes), resolves ssh/scp on Windows System32, probes Linux and Windows remotes during connection tests, and strips ANSI from errors. Co-authored-by: Cursor <cursoragent@cursor.com>
github-actions
Bot
added
bug
GUI and desktop launches often inherit the wrong SSH_AUTH_SOCK (or none), so Secure Enclave keys in Secretive work in Terminal but not in CCAM. Resolve the effective IdentityAgent via ssh -G, pass it to ssh/scp, and set HOME plus the Secretive socket in the child environment. Co-authored-by: Cursor <cursoragent@cursor.com>
PATH-first ssh/scp resolution, portable sh/PowerShell/cmd directory probes, Windows C:/ remote_home support, Secretive/agent path expansion from ssh -G, auth-first connection tests, scp -O fallback for legacy servers, and clearer env wiring (HOME/USERPROFILE/SYSTEMROOT) for GUI-launched dashboards. Co-authored-by: Cursor <cursoragent@cursor.com>
Only pass IdentityAgent when ssh -G names a concrete socket (Secretive, 1Password, custom). File-key and ssh-agent users rely on HOME, inherited SSH_AUTH_SOCK, or launchctl discovery — installing Secretive no longer overrides other auth methods. Co-authored-by: Cursor <cursoragent@cursor.com>
Explicit -F ~/.ssh/config, Windows agent pipe, PATH-first ssh, probe ordering by remote OS hint, quoted IdentityAgent paths, blank identity_file handling, ENOENT install hints, and clearer missing-remote-dir errors. Co-authored-by: Cursor <cursoragent@cursor.com>
hoangsonww
force-pushed
the
fix/remote-sync-scp-cross-platform
branch
2 times, most recently
from
July 26, 2026 21:51
6f58161 to
d78b97c
Compare
Pull remote sessions every 15s (was 60s), sync immediately on add/re-enable, and broadcast session_created/updated after each mirror so the dashboard updates without manual Sync. Reconcile status from transcript timestamps, fix WSL test messages and Settings copy, and add remote seed test commands. Co-authored-by: Cursor <cursoragent@cursor.com>
Align all documentation with scp-based remote sync, 15s polling, JSONL-based live status reconciliation, and remote_data.updated WebSocket broadcasts. Co-authored-by: Cursor <cursoragent@cursor.com>
CI tsc failed because remoteDataEvents tests used source: "remote" on import.progress payloads; extend the WS type and tighten the helper cast. Co-authored-by: Cursor <cursoragent@cursor.com>
hoangsonww
force-pushed
the
fix/remote-sync-scp-cross-platform
branch
from
July 26, 2026 21:57
d78b97c to
dde905b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
rsyncentirely for Remote Data Sources — remotes only need a running OpenSSH server (built-in SFTP/scp). No rsync, agents, or dashboard packages on the remote.scpover SSH from the dashboard machine (Linux, macOS, or Windows with OpenSSH Client).ssh.exe/scp.exeunderC:\Windows\System32\OpenSSH\when not on PATH.test -dprobe plus PowerShellTest-Pathfor Windows remotes whenremote_homeis~-rooted.Why
rsyncover SSH requiresrsyncinstalled on both ends. Windows dashboards and many remotes only ship OpenSSH — sync was failing with "rsync is not recognized" even whenssh user@hostworked fine.Test plan
npm run test:server(remote-sources suite)ssh user@hostworks, then Test + Sync now in Settings → Remote Data SourcesPermission deniedcases show a clean message when keys are missing (fix auth withssh user@host+ identity file in settings)Made with Cursor