Files
DuProcess 569a3e9ce5
ci / test (push) Canceled after 0s
ci / fuzz-smoke (push) Canceled after 0s
ci / macos-client (macos-aarch64, macos-14) (push) Canceled after 0s
ci / macos-client (macos-x86_64, macos-13) (push) Canceled after 0s
ci / windows-client (push) Canceled after 0s
ci / package-release (linux-x86_64, ubuntu-latest, , , ) (push) Canceled after 0s
ci / package-release (macos-aarch64, macos-14, , , ) (push) Canceled after 0s
ci / package-release (macos-x86_64, macos-13, , , ) (push) Canceled after 0s
ci / package-release (windows-aarch64, windows-latest, aarch64, windows, aarch64-pc-windows-msvc) (push) Canceled after 0s
ci / package-release (windows-x86_64, windows-latest, , , ) (push) Canceled after 0s
ci / remote-bench (push) Canceled after 0s
ci / publish-gitea-release (push) Canceled after 0s
Resolve VS Code config paths beside SSH config
2026-07-16 22:41:05 -04:00
..
2026-06-30 19:42:45 -04:00

Dosh Remote

Open VS Code Remote-SSH windows through Dosh.

The extension writes a managed SSH config entry like:

Host dosh-palav
    HostName 127.0.0.1
    HostKeyAlias palav
    ProxyCommand dosh proxy-stdio palav %h %p

VS Code still uses Remote-SSH, so server install, extensions, terminals, and normal SSH behavior stay intact. Dosh carries the SSH TCP byte stream.