mirror of
https://github.com/binaricat/Netcatty.git
synced 2026-11-20 15:19:16 +00:00
* fix(sftp): follow terminal cwd on macOS/BSD remotes and first open The "follow terminal directory" probe read the interactive shell's cwd only via /proc, which does not exist on macOS/BSD remotes, so getSessionPwd fell back to the home directory (or failed) and the SFTP panel never tracked the terminal. Add an lsof fallback (read_shell_cwd) so the probe works on non-Linux remotes; Linux keeps using /proc. Also fix the first open: while the panel is closed the per-command cwd probe does not run, so activeTerminalCwd can be stale (login home) even after the terminal cd-ed elsewhere. On that stale value the follow sync saw currentPath === terminalCwd and did nothing, leaving the panel at home. Force one fresh backend probe when the panel first becomes visible for a connected remote, and re-sync on reopen. Fixes #2335 Co-authored-by: Cursor Agent <cursor-agent@cursor.com> * fix(sftp): keep first-open follow from snapping back to stale cwd Addresses PR review: the first-open resync navigated to the freshly probed terminal cwd but left the stale `activeTerminalCwd` cache (login home) in place. Because the one-shot ref was already set, a later dependency change that re-runs the normal follow sync (e.g. closing an editor toggles hasActiveWork) would navigate the pane back to that stale home. Mark the stale cached cwd as already handled before navigating so the normal sync no-ops until the live cwd catches up; invalidateInFlightFollowSync clears the guard once activeTerminalCwd actually changes, letting follow resume. Co-authored-by: Cursor Agent <cursor-agent@cursor.com> * fix(sftp): re-check follow eligibility before first-open navigation Addresses PR review: the first-open resync awaited a fresh terminal-cwd probe but only re-validated the connection afterward. If the panel was hidden or interactive work started (editor/dialog) while the probe was in flight, it still navigated, moving the pane while the follow feature's own visible/work guards say it should be paused. Add a live followStillEligible() check (generation, follow enabled/ allowed, visible, no active work, same connection) that gates both the post-probe continuation and the navigateTo call via shouldApply, matching the normal follow path. Reset the one-shot guard when bailing mid-probe so the resync can retry once follow is eligible again. Co-authored-by: Cursor Agent <cursor-agent@cursor.com> * test(host-details): align auth row assertion with unified row height The HostDetailsSection row was unified to `flex h-12 ... px-3` (#2378) but HostDetailsConnectionSections.test still expected the old `min-h-12 ... px-3 py-2` class, failing lint-and-test on main. Update the regex to match the shipped markup. Co-authored-by: Cursor Agent <cursor-agent@cursor.com> * fix(sftp): harden terminal cwd resync --------- Co-authored-by: Cursor Agent <cursor-agent@cursor.com> Co-authored-by: bincxz <16399091+binaricat@users.noreply.github.com>