{"id":30004517,"url":"https://github.com/inhesrom/remote-ssh.nvim","last_synced_at":"2026-01-24T23:02:26.250Z","repository":{"id":253014395,"uuid":"842197783","full_name":"inhesrom/remote-ssh.nvim","owner":"inhesrom","description":null,"archived":false,"fork":false,"pushed_at":"2026-01-24T06:01:33.000Z","size":1887,"stargazers_count":94,"open_issues_count":5,"forks_count":5,"subscribers_count":1,"default_branch":"master","last_synced_at":"2026-01-24T16:04:45.989Z","etag":null,"topics":["neovim-plugin"],"latest_commit_sha":null,"homepage":"","language":"Lua","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/inhesrom.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2024-08-13T21:52:24.000Z","updated_at":"2026-01-24T01:08:30.000Z","dependencies_parsed_at":"2026-01-12T12:03:34.461Z","dependency_job_id":null,"html_url":"https://github.com/inhesrom/remote-ssh.nvim","commit_stats":null,"previous_names":["ihersom/remote-ssh-nvim","inhesrom/remote-ssh.nvim"],"tags_count":20,"template":false,"template_full_name":null,"purl":"pkg:github/inhesrom/remote-ssh.nvim","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/inhesrom%2Fremote-ssh.nvim","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/inhesrom%2Fremote-ssh.nvim/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/inhesrom%2Fremote-ssh.nvim/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/inhesrom%2Fremote-ssh.nvim/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/inhesrom","download_url":"https://codeload.github.com/inhesrom/remote-ssh.nvim/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/inhesrom%2Fremote-ssh.nvim/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28738979,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-01-24T22:12:27.248Z","status":"ssl_error","status_checked_at":"2026-01-24T22:12:10.529Z","response_time":89,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.6:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["neovim-plugin"],"created_at":"2025-08-05T07:02:37.598Z","updated_at":"2026-01-24T23:02:26.220Z","avatar_url":"https://github.com/inhesrom.png","language":"Lua","readme":"# 🕹️ Remote SSH\n\nEdit remote files in Neovim with full LSP and TreeSitter support. This plugin runs language servers directly on remote machines while keeping your editing experience completely local, giving you the best of both worlds: responsive editing with full language features.\n\n\u003e [!NOTE]\n\u003e **Why this approach wins:** You get instant keystrokes and cursor movement (local editing) combined with accurate code intelligence that understands your entire remote project (remote LSP). No more choosing between responsiveness and functionality.\n\n## 🔄 How it works\n\n**The key insight:** Instead of running language servers locally (which lack remote project context) or editing remotely (which has network latency), this plugin runs language servers on the remote machine while keeping file editing completely local.\n\n```\nLocal Neovim ←→ SSH ←→ Remote Language Server\n(fast editing)       (full project context)\n```\n\nHere's what happens when you open a remote file:\n\n1. **Fetch once:** Download the remote file to a local buffer for instant editing\n2. **Connect LSP:** Start the language server on the remote machine with full project access\n3. **Bridge communication:** Translate LSP messages between your local Neovim and remote server\n4. **Save asynchronously:** File changes sync back to the remote machine in the background\n5. **Enable TreeSitter:** Syntax highlighting works immediately on the local buffer\n\nThis gives you zero-latency editing with full LSP features like code completion, go-to-definition, and error checking.\n\n## 🚀 Quick Start\n\n### Prerequisites\n- Passwordless SSH access to your remote server: `ssh user@host` (should work without password)\n- Plugin installed and configured (see Installation section below)\n\n### Steps\n1. **Open a remote file:**\n   ```vim\n   :RemoteOpen rsync://user@host//path/to/file.cpp\n   ```\n\n2. **Or browse remote directories:**\n   ```vim\n   :RemoteTreeBrowser rsync://user@host//path/to/folder/\n   ```\n   Use `j/k` to navigate, `Enter` to open files, `q` to quit.\n\n3. **Verify it works:**\n   - You should see syntax highlighting immediately\n   - LSP features (completion, hover, go-to-definition) should work within seconds\n   - File saves happen automatically in the background\n\n4. **Run TUI applications remotely:**\n   ```vim\n   :RemoteTui htop                  \" System monitor\n   :RemoteTui lazygit               \" Git interface (https://github.com/jesseduffield/lazygit)\n   :RemoteTui \"tail -f app.log\"     \" Log monitoring\n   ```\n   Use `Ctrl+H` to hide sessions, `:RemoteTui` (no args) to restore them.\n\nThat's it! The plugin handles the rest automatically.\n\n![RemoteTreeBrowser With Open Remote Buffers](./images/term.png)\n\n## ✨ Features\n\n### 🎯 Core Features\n- **🧠 Full LSP Support** - Code completion, go-to-definition, hover documentation, and error checking work seamlessly\n- **⚡ Zero-latency Editing** - All keystrokes and cursor movements happen instantly on local buffers\n- **🎨 TreeSitter Syntax Highlighting** - Immediate syntax highlighting without network delays\n- **💾 Smart Auto-save** - Files sync to remote machines asynchronously without blocking your workflow\n\n### 🔧 Advanced Features\n- **👁️ File Change Detection** - Automatically detects when remote files are modified by others with conflict resolution\n- **📁 Remote File Explorer** - Tree-based directory browsing with familiar navigation\n- **🔍 Enhanced Search** - Telescope integration for searching remote buffers and file history\n- **📚 Session History** - Track and quickly reopen recently used remote files and directories\n- **📊 Interactive Log Viewer** - View and filter plugin logs with rich diagnostic context for troubleshooting\n\n### 🖥️ Language Server Support\nReady-to-use configurations for popular language servers:\n\n**✅ Fully Supported \u0026 Tested:**\n- **C/C++** (clangd) - Code completion, diagnostics, go-to-definition\n- **Python** (pylsp) - Full IntelliSense with linting and formatting\n- **Rust** (rust-analyzer) - Advanced Rust language features\n- **Lua** (lua_ls) - Neovim configuration and scripting support\n- **CMake** (cmake-language-server) - Build system integration\n- **XML** (lemminx) - Markup language support\n\n**🟡 Available But Not Tested:**\n- **Zig** (zls), **Go** (gopls), **Java** (jdtls)\n- **JavaScript/TypeScript** (tsserver), **C#** (omnisharp)\n- **Python** (pyright), **Bash** (bashls)\n\u003e [!NOTE]\n\u003e If you find that desired LSP is not listed here, try testing it out, if it works (or not), open a GitHub issue and we can get it added to this list with the correct status\n\n### 🛠️ Technical Features\n- **Automatic Server Management** - Language servers start automatically on remote machines\n- **Smart Path Translation** - Seamless handling of local vs remote file paths for LSP\n- **Robust Error Recovery** - Graceful handling of network issues and connection problems\n\n## 📜 Requirements\n\n### Local machine 💻\n\n- Neovim \u003e= 0.11.0\n- [nvim-lspconfig](https://github.com/neovim/nvim-lspconfig)\n- OpenSSH client\n- Python 3\n- rsync\n\n### Remote machine ☁️\n\n- SSH server\n- Language servers for your programming languages\n- Python 3\n- rsync\n- find (for directory browsing)\n- grep (for remote file searching)\n\n### 💻 Platform Support\n\n| Platform | Support |\n|----------|----------|\n| Linux    | ✅ Full |\n| macOS    | ✅ Full |\n| Windows  | 🟡 WSL recommended |\n\n## 📥 Installation\n\nUsing [lazy.nvim](https://github.com/folke/lazy.nvim)\n\n```lua\n{\n    \"inhesrom/remote-ssh.nvim\",\n    branch = \"master\",\n    dependencies = {\n        \"inhesrom/telescope-remote-buffer\", --See https://github.com/inhesrom/telescope-remote-buffer for features\n        \"nvim-telescope/telescope.nvim\",\n        \"nvim-lua/plenary.nvim\",\n        \"neovim/nvim-lspconfig\",\n        -- nvim-notify is recommended, but not necessarily required into order to get notifcations during operations - https://github.com/rcarriga/nvim-notify\n        \"rcarriga/nvim-notify\",\n    },\n    config = function ()\n        require('telescope-remote-buffer').setup(\n            -- Default keymaps to open telescope and search open buffers including \"remote\" open buffers\n            --fzf = \"\u003cleader\u003efz\",\n            --match = \"\u003cleader\u003egb\",\n            --oldfiles = \"\u003cleader\u003erb\"\n        )\n\n        -- setup lsp_config here or import from part of neovim config that sets up LSP\n\n        require('remote-ssh').setup({\n            on_attach = lsp_config.on_attach,\n            capabilities = lsp_config.capabilities,\n            filetype_to_server = lsp_config.filetype_to_server\n        })\n    end\n}\n```\n\nUsing [packer.nvim](https://github.com/wbthomason/packer.nvim)\n\n```lua\nuse {\n    'inhesrom/remote-ssh.nvim',\n    branch = \"master\",\n    requires = {\n        \"inhesrom/telescope-remote-buffer\",\n        \"nvim-telescope/telescope.nvim\",\n        \"nvim-lua/plenary.nvim\",\n        'neovim/nvim-lspconfig',\n    },\n    config = function()\n        require('telescope-remote-buffer').setup()\n\n        -- setup lsp_config here or import from part of neovim config that sets up LSP\n\n        require('remote-ssh').setup({\n            on_attach = lsp_config.on_attach,\n            capabilities = lsp_config.capabilities,\n            filetype_to_server = lsp_config.filetype_to_server\n        })\n    end\n}\n```\n\n## 🔧 Setup Prerequisites\n\n### SSH Key Configuration (Required)\n\nFor seamless remote development, you need passwordless SSH access to your remote servers:\n\n```bash\n# Generate SSH key if you don't have one\nssh-keygen -t ed25519 -C \"your_email@example.com\"\n\n# Copy key to remote server\nssh-copy-id user@remote-server\n\n# Test passwordless connection\nssh user@remote-server\n```\n\n### LSP Configuration Setup\n\nYou'll need to configure LSP servers for the plugin to work properly. Here's a basic setup:\n\n1. **Create an LSP utility file** (e.g., `lsp_util.lua`):\n\n```lua\n-- lsp_util.lua\nlocal M = {}\n\n-- LSP on_attach function with key mappings\nM.on_attach = function(client, bufnr)\n    local nmap = function(keys, func, desc)\n        vim.keymap.set('n', keys, func, { buffer = bufnr, desc = desc })\n    end\n\n    -- Key mappings\n    nmap('gd', require('telescope.builtin').lsp_definitions, '[G]oto [D]efinition')\n    nmap('gr', require('telescope.builtin').lsp_references, '[G]oto [R]eferences')\n    nmap('gI', require('telescope.builtin').lsp_implementations, '[G]oto [I]mplementation')\n    nmap('K', vim.lsp.buf.hover, 'Hover Documentation')\n    nmap('\u003cleader\u003ern', vim.lsp.buf.rename, '[R]e[n]ame')\n    nmap('\u003cleader\u003eca', vim.lsp.buf.code_action, '[C]ode [A]ction')\nend\n\n-- LSP capabilities\nlocal capabilities = vim.lsp.protocol.make_client_capabilities()\nM.capabilities = require('cmp_nvim_lsp').default_capabilities(capabilities)\n\n-- Server definitions\nM.servers = {\n    clangd = {},            -- C/C++\n    rust_analyzer = {},     -- Rust\n    pylsp = {},             -- Python\n    lua_ls = {},            -- Lua\n    -- Add more servers as needed\n}\n\n-- Generate filetype to server mapping\nM.filetype_to_server = {}\nfor server_name, _ in pairs(M.servers) do\n    local filetypes = require('lspconfig')[server_name].document_config.default_config.filetypes or {}\n    for _, ft in ipairs(filetypes) do\n        M.filetype_to_server[ft] = server_name\n    end\nend\n\nreturn M\n```\n\n2. **Use Mason for automatic local LSP management/installation**:\n\u003e [!NOTE]\n\u003e You will need to manually ensure that the corresponding remote LSP is installed on the remote host\n\n```lua\n-- In your plugin configuration\n{\n    'williamboman/mason.nvim',\n    dependencies = { 'williamboman/mason-lspconfig.nvim' },\n    config = function()\n        require('mason').setup()\n        require('mason-lspconfig').setup({\n            ensure_installed = vim.tbl_keys(require('lsp_util').servers),\n        })\n    end\n}\n```\n\n## 🌐 Remote Server Setup\n\n### Language Server Installation\n\nInstall the required language servers on your remote development machines:\n\n#### Python (pylsp)\n```bash\n# On remote server\npip3 install python-lsp-server[all]\n# Optional: for better performance\npip3 install python-lsp-ruff  # Fast linting\n```\n\n#### C/C++ (clangd)\n```bash\n# Ubuntu/Debian\nsudo apt install clangd\n\n# CentOS/RHEL/Rocky\nsudo dnf install clang-tools-extra\n\n# macOS\nbrew install llvm\n\n# Arch Linux\nsudo pacman -S clang\n```\n\n#### Rust (rust-analyzer)\n```bash\n# Install via rustup (recommended)\nrustup component add rust-analyzer\n\n# Or via package manager\n# Ubuntu 22.04+: sudo apt install rust-analyzer\n# macOS: brew install rust-analyzer\n# Arch: sudo pacman -S rust-analyzer\n```\n\n#### Lua (lua-language-server)\n```bash\n# Ubuntu/Debian (if available in repos)\nsudo apt install lua-language-server\n\n# macOS\nbrew install lua-language-server\n\n# Or install manually from releases:\n# https://github.com/LuaLS/lua-language-server/releases\n```\n\n#### Java (jdtls)\n```bash\n# Install Java first\nsudo apt install openjdk-17-jdk  # Ubuntu\nbrew install openjdk@17          # macOS\n\n# jdtls will be automatically downloaded by Mason\n```\n\n#### CMake (cmake-language-server)\n```bash\n# Install via pip\npip3 install cmake-language-server\n\n# Or via package manager\nsudo apt install cmake-language-server  # Ubuntu 22.04+\n```\n\n### Remote System Requirements\n\nEnsure your remote systems have the following:\n\n```bash\n# Check Python 3 availability\npython3 --version\n\n# Check rsync availability\nrsync --version\n\n# Verify SSH server is running\nsystemctl status ssh  # Ubuntu/Debian\nsystemctl status sshd # CentOS/RHEL\n\n# Test SSH access\nssh user@remote-server \"echo 'SSH working'\"\n```\n\n## ⚙️ Configuration\n\nHere's a default configuration with comments explaining each option:\n\n```lua\nrequire('remote-ssh').setup({\n    -- Optional: Custom on_attach function for LSP clients\n    on_attach = function(client, bufnr)\n        -- Your LSP keybindings and setup\n    end,\n\n    -- Optional: Custom capabilities for LSP clients\n    capabilities = vim.lsp.protocol.make_client_capabilities(),\n\n    -- Custom mapping from filetype to LSP server name\n    filetype_to_server = {\n        -- Example: Use pylsp for Python (default and recommended)\n        python = \"pylsp\",\n        -- More customizations...\n    },\n\n    -- Custom server configurations\n    server_configs = {\n        -- Custom config for clangd\n        clangd = {\n            filetypes = { \"c\", \"cpp\", \"objc\", \"objcpp\" },\n            root_patterns = { \".git\", \"compile_commands.json\" },\n            init_options = {\n                usePlaceholders = true,\n                completeUnimported = true\n            }\n        },\n        -- More server configs...\n    },\n\n    -- Async write configuration\n    async_write_opts = {\n        timeout = 30,         -- Timeout in seconds for write operations\n        debug = false,        -- Enable debug logging\n        log_level = vim.log.levels.INFO,\n        autosave = true,      -- Enable automatic saving on text changes (default: true)\n                              -- Set to false to disable auto-save while keeping manual saves (:w) working\n        save_debounce_ms = 3000, -- Delay before initiating auto-save to handle rapid editing (default: 3000)\n\n        -- Logging configuration\n        logging = {\n            max_entries = 1000,      -- Maximum number of log entries to store in memory\n            include_context = true,  -- Include contextual data (URLs, exit codes, etc.) in logs\n            viewer = {\n                height = 15,         -- Height of log viewer split in lines\n                auto_scroll = true,  -- Auto-scroll to bottom when new logs arrive\n                position = \"bottom\"  -- Position of split (bottom/top)\n            }\n        }\n    }\n})\n```\n\n### Autosave Configuration\n\nThe plugin includes an intelligent autosave feature that automatically saves remote files as you edit them. This feature is enabled by default but can be customized or disabled:\n\n**Enable autosave (default behavior):**\n```lua\nrequire('remote-ssh').setup({\n    async_write_opts = {\n        autosave = true,        -- Auto-save on text changes\n        save_debounce_ms = 3000 -- Wait 3 seconds after editing before saving\n    }\n})\n```\n\n**Disable autosave while keeping manual saves working:**\n```lua\nrequire('remote-ssh').setup({\n    async_write_opts = {\n        autosave = false  -- Disable auto-save, but `:w` still works\n    }\n})\n```\n\n**Note:** Manual saves (`:w`, `:write`) always work regardless of the autosave setting. When autosave is disabled, you'll need to manually save your changes using `:w` or similar commands.\n\n### Logging Configuration\n\nThe plugin includes a comprehensive logging system with an interactive log viewer. Logs are stored in a ring buffer (memory only) and can be viewed with `:RemoteSSHLog`.\n\n**Default configuration:**\n```lua\nrequire('remote-ssh').setup({\n    async_write_opts = {\n        logging = {\n            max_entries = 1000,      -- Store up to 1000 log entries\n            include_context = true,  -- Include diagnostic context (recommended)\n            viewer = {\n                height = 15,         -- Log viewer height in lines\n                auto_scroll = true,  -- Auto-scroll to newest logs\n                position = \"bottom\"  -- Open at bottom of screen\n            }\n        }\n    }\n})\n```\n\n**View logs:**\n```vim\n:RemoteSSHLog           \" Open interactive log viewer\n:RemoteSSHLogClear      \" Clear all stored logs\n:RemoteSSHLogFilter ERROR  \" Filter by log level\n```\n\n**Log viewer keybindings:**\n- `1` - Show ERROR only\n- `2` - Show WARN and above\n- `3` - Show INFO and above\n- `4` - Show all (DEBUG+)\n- `0` - Clear filter\n- `r` - Refresh\n- `C` - Clear all logs\n- `g` - Toggle auto-scroll\n- `q` - Close viewer\n\n**Notification behavior:**\n- **ERROR** and **WARN**: Show as notifications + stored in log buffer (by default)\n- **INFO** and **DEBUG**: Only stored in log buffer (view with `:RemoteSSHLog`)\n- **Background operations**: Errors from background tasks (like directory warming) are logged but don't show notifications\n- This prevents notification spam from both debug mode and background operations\n\n**💡 Pro tip**: Set `debug = true` and `log_level = vim.log.levels.DEBUG` to see detailed SSH commands and operations in the log viewer without getting notification spam.\n\n### RemoteTui Configuration\n\nThe plugin provides configurable options for RemoteTui sessions, including keybinds, window behavior, and appearance.\n\n**Default configuration:**\n```lua\nrequire('remote-ssh').setup({\n    remote_tui_opts = {\n        keymaps = {\n            hide_session = \"\u003cC-h\u003e\"  -- Keymap to hide TUI session (terminal mode)\n        },\n        window = {\n            type = \"float\",         -- \"float\" or \"split\"\n            width = 0.9,           -- Percentage of screen width (for float)\n            height = 0.9,          -- Percentage of screen height (for float)\n            border = \"rounded\"     -- Border style for floating windows\n        },\n        picker = {\n            width = 0.6,           -- Session picker width\n            height = 0.6           -- Session picker height\n        }\n    }\n})\n```\n\n**Customize hide keybind:**\n```lua\nrequire('remote-ssh').setup({\n    remote_tui_opts = {\n        keymaps = {\n            hide_session = \"\u003cC-x\u003e\"  -- Use Ctrl+X instead of Ctrl+H\n        }\n    }\n})\n```\n\n**Disable hide keybind:**\n```lua\nrequire('remote-ssh').setup({\n    remote_tui_opts = {\n        keymaps = {\n            hide_session = \"\"  -- Empty string disables the keybind\n        }\n    }\n})\n```\n\n**💡 Pro tip**: If the default `Ctrl+H` conflicts with other plugins, customize it to a different key combination that fits your workflow.\n\n## 🎥 Examples\n\n### Opening and editing remote files\n\n```bash\n# In your terminal\nnvim rsync://user@remote-host/path/to/file.cpp\n```\n\nOr from within Neovim:\n\n```vim\n:e rsync://user@remote-host/path/to/file.cpp\n```\n\n### Using the RemoteOpen command\n\n```vim\n:RemoteOpen rsync://user@remote-host/path/to/file.cpp\n```\n\n### Browsing remote directories\n\n```vim\n:RemoteTreeBrowser rsync://user@remote-host/path/to/directory\n```\n\n### Enhanced telescope integration\n\nWith telescope-remote-buffer, you get additional commands for managing remote buffers:\n\n**Default keymaps** (configurable during setup as shown above):\n- `\u003cleader\u003efz` - Fuzzy search remote buffers\n- `\u003cleader\u003egb` - Browse remote buffers\n- `\u003cleader\u003erb` - Browse remote oldfiles\n\n## 👁️ Remote File Watching\n\nThe plugin includes an intelligent file watching system that monitors remote files for changes made by other users or processes. This helps prevent conflicts and keeps your local buffer synchronized with the remote file state.\n\n### How it Works\n\n1. **Automatic Detection**: When you open a remote file, the file watcher automatically starts monitoring it\n2. **Change Detection**: Uses SSH to periodically check the remote file's modification time (mtime)\n3. **Smart Conflict Resolution**: Distinguishes between changes from your own saves vs. external changes\n4. **Conflict Handling**: When conflicts are detected, you'll be notified and can choose how to resolve them\n\n### Conflict Resolution Strategies\n\n- **No Conflict**: Remote file hasn't changed since your last interaction\n- **Safe to Pull**: Remote file changed, but you have no unsaved local changes - automatically pulls the remote content\n- **Conflict Detected**: Both local and remote files have changes - requires manual resolution\n\n### File Watcher Configuration\n\nYou can configure the file watcher behavior for each buffer, if you find the defaults are not working for you:\n\n```vim\n\" Set poll interval to 10 seconds\n:RemoteWatchConfigure poll_interval 10000\n\n\" Enable auto-refresh (automatically pull non-conflicting changes)\n:RemoteWatchConfigure auto_refresh true\n\n\" Disable file watching for current buffer\n:RemoteWatchConfigure enabled false\n```\n\n### SSH Config Alias Support\n\nThe file watcher supports SSH config aliases, allowing you to use simplified hostnames:\n\n```bash\n# ~/.ssh/config\nHost myserver\n    HostName server.example.com\n    User myuser\n    Port 2222\n```\n\nThen use in Neovim:\n```vim\n:RemoteOpen rsync://myserver-alias//path/to/file.cpp\n```\n\nNote the double slash (`//`) format which is automatically detected and handled.\n\n## 📚 Remote Session History\n\nThe plugin includes a comprehensive session history feature that tracks all your remote file and directory access, providing quick navigation to recently used items.\n\n### Features\n\n- **🎨 File Type Icons**: Shows proper file type icons with colors (using nvim-web-devicons if available)\n- **📌 Pin Favorites**: Pin frequently used sessions to keep them at the top\n- **🔍 Smart Filtering**: Filter sessions by filename or hostname\n- **💾 Persistent Storage**: History persists across Neovim sessions\n- **📁 Mixed Content**: Tracks both individual files and directory browsing sessions\n- **⚡ Fast Navigation**: Quickly jump to any previously accessed remote location\n\n### Usage\n\n```vim\n:RemoteHistory\n```\n\nOpens a floating window with your session history where you can:\n\n- **Navigate**: Use `j/k` or arrow keys to move through sessions\n- **Open**: Press `Enter` or `Space` to open the selected session\n- **Pin/Unpin**: Press `p` to pin or unpin sessions\n- **Filter**: Press `/` to enter filter mode, then type to search\n- **Exit**: Press `q` or `Esc` to close the picker\n\n### Display Format\n\nEach session shows: `[PIN] [TIME] [HOST] [ICON] [PATH] [(pinned)]`\n\nExample:\n```\n▶ 📌 12/04 14:30 myserver  /home/user/config.lua (pinned)\n   12/04 14:25 myserver 📁 /home/user/project\n   12/04 14:20 devbox 🐍 /app/main.py\n   12/04 14:15 myserver 📝 /home/user/README.md\n```\n\n### Automatic Tracking\n\nSessions are automatically tracked when you:\n- Open remote files using `:RemoteOpen` or `:e rsync://...`\n- Browse remote directories using `:RemoteTreeBrowser`\n- Use any command that opens remote content\n\n### Configuration\n\n- **Storage**: Sessions saved to `~/.local/share/nvim/remote-ssh-sessions.json`\n- **History Limit**: Default 100 entries (configurable)\n- **Window Size**: Dynamically sized to fit content (minimum 60x10, maximum available screen space)\n- **Auto-save**: Changes saved immediately and on Neovim exit\n\n## 🖥️ Remote TUI Session Management\n\n**Benefits**: Run and manage multiple TUI applications (htop, lazygit, yazi, even nvim) on remote machines with session persistence and instant switching. Hide/restore sessions without losing state, perfect for multitasking across different remote tools.\n\nThe plugin includes a powerful TUI session management system that lets you run terminal applications on remote servers with full session control - think tmux-like functionality integrated directly into Neovim.\n\n### Features\n\n- **🎯 Session Multiplexing**: Run multiple TUI apps per remote host simultaneously\n- **⚡ Hide/Restore**: Use `Ctrl+H` to hide sessions, restore instantly from picker\n- **🎨 Visual Session Picker**: Colorful interface showing app, host, directory, and timestamp\n- **💾 State Preservation**: Hidden sessions maintain their full state and scrollback\n- **🗑️ Session Cleanup**: Delete unwanted sessions with confirmation\n\n### Usage\n\n**Create a TUI session:**\n```vim\n:RemoteTui htop              \" Run htop on current remote host\n:RemoteTui lazygit           \" Run lazygit for git operations\n:RemoteTui \"tail -f app.log\" \" Monitor log files\n```\n\n**Manage sessions:**\n- **Hide current session**: Press `Ctrl+H` while in any TUI session\n- **Open session picker**: Run `:RemoteTui` (no arguments)\n- **Navigate picker**: Use `j/k` or arrow keys to select sessions\n- **Restore session**: Press `Enter` or `Space` on selected session\n- **Delete session**: Press `d` then `y` to confirm deletion\n\n### Session Picker Interface\n\nThe picker shows sessions in this format: `[TIME] APP @ HOST:DIRECTORY`\n\nExample display:\n```\n▶ [12/25 14:30] htop @ myserver.com:~/projects\n  [12/25 14:25] lazygit @ devbox:~/repo\n  [12/25 14:20] tail @ production:/var/log\n```\n\n### Connection Handling\n\n**With remote buffer open**: Automatically uses the current buffer's connection info\n**Without remote buffer**: Prompts for connection details:\n- Enter `user@host` format (e.g., `ubuntu@myserver.com`)\n- Specify remote directory (defaults to `~`)\n\n### Common Workflows\n\n```vim\n\" Monitor system resources\n:RemoteTui htop\n\n\" Work with git (hide when done)\n:RemoteTui lazygit\n\u003cCtrl+H\u003e\n\n\" Check logs while coding\n:RemoteTui \"tail -f /var/log/app.log\"\n\u003cCtrl+H\u003e\n\n\" Switch between sessions\n:RemoteTui\n\" Use picker to restore any session\n```\n\n**💡 Pro tip**: Each remote host can run multiple concurrent TUI sessions. Use descriptive commands like `:RemoteTui \"htop -d 1\"` to distinguish similar tools with different options.\n\n## 🤖 Available commands\n\n| Primary Commands          | What does it do?                                                            |\n| ------------------------- | --------------------------------------------------------------------------- |\n| `:RemoteOpen`             | Open a remote file with scp:// or rsync:// protocol                         |\n| `:RemoteTreeBrowser`       | Browse a remote directory with tree-based file explorer                     |\n| `:RemoteTreeBrowserHide`       | Hide the remote file browser                     |\n| `:RemoteTreeBrowserShow`       | Show the remote file browser                     |\n| `:RemoteTui [app]`        | Run TUI application on remote host (with args) or show session picker (no args) |\n| `:RemoteHistory`          | Open remote session history picker with pinned items and filtering          |\n| `:RemoteGrep`             | Search for text in remote files using grep                                  |\n| `:RemoteRefresh`          | Refresh a remote buffer by re-fetching its content                          |\n| `:RemoteRefreshAll`       | Refresh all remote buffers                                                  |\n\n| Remote History Commands   | What does it do?                                                            |\n| ------------------------- | --------------------------------------------------------------------------- |\n| `:RemoteHistory`          | Open session history picker with pinned items and filtering                 |\n| `:RemoteHistoryClear`     | Clear remote session history                                                |\n| `:RemoteHistoryClearPinned` | Clear pinned remote sessions                                              |\n| `:RemoteHistoryStats`     | Show remote session history statistics                                      |\n\n| File Watcher Commands     | What does it do?                                                            |\n| ------------------------- | --------------------------------------------------------------------------- |\n| `:RemoteWatchStart`       | Start file watching for current buffer (monitors remote changes)            |\n| `:RemoteWatchStop`        | Stop file watching for current buffer                                       |\n| `:RemoteWatchStatus`      | Show file watching status for current buffer                                |\n| `:RemoteWatchRefresh`     | Force refresh from remote (overwrite local changes)                         |\n| `:RemoteWatchConfigure`   | Configure file watcher settings (enabled, poll_interval, auto_refresh)      |\n| `:RemoteWatchDebug`       | Debug file watcher SSH connection and commands                              |\n\n| Debug Commands            | What does it do?                                                            |\n| ------------------------- | --------------------------------------------------------------------------- |\n| `:RemoteLspStart`         | Manually start LSP for the current remote buffer                            |\n| `:RemoteLspStop`          | Stop all remote LSP servers and kill remote processes                       |\n| `:RemoteLspRestart`       | Restart LSP server for the current buffer                                   |\n| `:RemoteLspSetRoot`       | Manually set the root directory for the remote LSP server, override automatic discovery                            |\n| `:RemoteLspServers`       | List available remote LSP servers                                           |\n| `:RemoteLspDebug`         | Print debug information about remote LSP clients                            |\n| `:RemoteLspDebugTraffic`  | Enable/disable LSP traffic debugging                                        |\n| `:RemoteFileStatus`       | Show status of remote file operations                                       |\n| `:AsyncWriteCancel`       | Cancel ongoing asynchronous write operation                                 |\n| `:AsyncWriteStatus`       | Show status of active asynchronous write operations                         |\n| `:AsyncWriteForceComplete`| Force complete a stuck write operation                                      |\n| `:AsyncWriteDebug`        | Toggle debugging for async write operations                                 |\n| `:AsyncWriteLogLevel`     | Set the logging level (DEBUG, INFO, WARN, ERROR)                            |\n| `:AsyncWriteReregister`   | Reregister buffer-specific autocommands for current buffer                  |\n| `:RemoteDependencyCheck`  | Check all plugin dependencies (local tools, Neovim, Lua modules, SSH hosts) |\n| `:RemoteDependencyQuickCheck` | Quick dependency status overview with summary                           |\n| `:RemoteSSHLog`           | Open log viewer to see all plugin logs with filtering and context           |\n| `:RemoteSSHLogClear`      | Clear all stored log entries                                                |\n| `:RemoteSSHLogFilter`     | Filter log viewer by level (ERROR, WARN, INFO, DEBUG)                       |\n| `:TSRemoteHighlight`      | Manually enable TreeSitter highlighting for remote buffers                  |\n\n## 🔍 Dependency Checking\n\nThe plugin includes a comprehensive dependency checking system to help diagnose setup issues and ensure all required components are properly installed and configured.\n\n### Quick Status Check\n\nFor a rapid overview of your system status:\n\n```vim\n:RemoteDependencyQuickCheck\n```\n\nThis provides a simple ✅/⚠️/❌ status indicator and tells you if critical dependencies are missing.\n\n### Comprehensive Dependency Check\n\nFor detailed diagnostics and troubleshooting:\n\n```vim\n:RemoteDependencyCheck\n```\n\nThis performs a thorough check of:\n\n**Local Machine:**\n- ✅ **System Tools**: `ssh`, `scp`, `rsync`, `python3`, `stat`\n- ✅ **Neovim Version**: \u003e= 0.10.0 requirement\n- ✅ **Lua Dependencies**: `plenary.nvim`, `nvim-lspconfig`, `telescope.nvim` (optional), `nvim-notify` (optional)\n\n**Remote Hosts:**\n- 🔗 **SSH Connectivity**: Tests passwordless SSH access and response times\n- 🛠️ **Remote Tools**: `python3`, `rsync`, `find`, `grep`, `stat`, `ls`\n- 📡 **Auto-discovery**: Automatically finds hosts from `~/.ssh/config`\n\n### Host-Specific Checking\n\nYou can check specific hosts instead of auto-discovery:\n\n```vim\n\" Single host\n:RemoteDependencyCheck myserver\n\n\" Multiple hosts\n:RemoteDependencyCheck server1,server2,server3\n```\n\n### Understanding the Output\n\nThe dependency checker provides color-coded results:\n\n- ✅ **Green**: Component is properly installed and working\n- ⚠️ **Yellow**: Optional component missing or minor issues\n- ❌ **Red**: Critical dependency missing - plugin won't work properly\n\nEach failed dependency includes:\n- Detailed error messages\n- Version information where available\n- Specific recommendations for fixing the issue\n\n### Common Issues Detected\n\nThe dependency checker will identify issues like:\n- Missing `rsync` (prevents RemoteOpen from working)\n- SSH connectivity problems (timeouts, authentication failures)\n- Missing Neovim plugins (`plenary.nvim`, `nvim-lspconfig`)\n- Outdated Neovim version\n- Missing remote tools needed for directory browsing\n- SSH configuration problems\n\n**💡 Pro tip**: Run `:RemoteDependencyCheck` after initial setup to ensure everything is configured correctly, and whenever you encounter issues with RemoteOpen or RemoteTreeBrowser.\n\n## 🐛 Troubleshooting\n\n### First Steps\n\nBefore diving into specific troubleshooting steps, always start with the dependency checker:\n\n```vim\n:RemoteDependencyCheck\n```\n\nThis will identify most common setup issues including missing dependencies, SSH configuration problems, and plugin installation issues.\n\n### View Plugin Logs\n\nFor diagnosing failures and understanding what's happening behind the scenes, use the log viewer:\n\n```vim\n:RemoteSSHLog\n```\n\nThe log viewer provides:\n- **Color-coded log levels**: ERROR (red), WARN (yellow), INFO (blue), DEBUG (gray)\n- **Rich context**: URLs, exit codes, SSH commands, and job IDs\n- **Filtering**: Press `1` for errors only, `2` for warnings+, `3` for info+, `4` for all\n- **Interactive navigation**: Use `j/k` to scroll, `r` to refresh, `C` to clear logs, `q` to quit\n\n**Example workflow**:\n1. Encounter an issue (file won't open, tree browser fails, etc.)\n2. Open log viewer: `:RemoteSSHLog`\n3. Filter to errors: Press `1`\n4. Review the error context (SSH command, exit code, stderr)\n5. Use the diagnostic information to fix the issue\n\n**💡 Pro tip**: Keep the log viewer open in a split while working to see real-time errors and warnings.\n\n### Common Issues\n\n#### LSP Server Not Starting\n\n**Symptoms**: No LSP features (completion, hover, etc.) in remote files\n\n**Solutions**:\n1. **Check if language server is installed on remote**:\n   ```bash\n   ssh user@server \"which clangd\"  # Example for clangd\n   ssh user@server \"which rust-analyzer\"  # Example for rust-analyzer\n   ```\n\n2. **Verify Mason installation locally**:\n   ```vim\n   :Mason\n   :MasonLog\n   ```\n\n3. **Check LSP client status**:\n   ```vim\n   :LspInfo\n   :RemoteLspDebug\n   ```\n\n4. **Enable LSP debug logging**:\n   ```vim\n   :RemoteLspDebugTraffic on\n   :LspLog\n   ```\n\n#### SSH Connection Issues\n\n**Symptoms**: \"Connection refused\", \"Permission denied\", or timeout errors\n\n**Solutions**:\n1. **Test basic SSH connectivity**:\n   ```bash\n   ssh user@server\n   ```\n\n2. **Check SSH key authentication**:\n   ```bash\n   ssh-add -l  # List loaded keys\n   ssh user@server \"echo SSH key auth working\"\n   ```\n\n3. **Verify SSH config**:\n   ```bash\n   # Add to ~/.ssh/config\n   Host myserver\n       HostName server.example.com\n       User myuser\n       IdentityFile ~/.ssh/id_ed25519\n   ```\n\n4. **Check remote SSH server status**:\n   ```bash\n   ssh user@server \"systemctl status sshd\"\n   ```\n\n#### Remote File Access Issues\n\n**Symptoms**: Files won't open, save, or refresh\n\n**Solutions**:\n1. **View detailed error logs**:\n   ```vim\n   :RemoteSSHLog\n   ```\n   Press `1` to filter errors only and see SSH command failures, exit codes, and stderr.\n\n2. **Check file permissions**:\n   ```bash\n   ssh user@server \"ls -la /path/to/file\"\n   ```\n\n3. **Verify rsync availability**:\n   ```bash\n   ssh user@server \"rsync --version\"\n   ```\n\n4. **Test file operations manually**:\n   ```bash\n   rsync user@server:/path/to/file /tmp/test-file\n   ```\n\n5. **Check async write status**:\n   ```vim\n   :AsyncWriteStatus\n   :RemoteFileStatus\n   ```\n\n#### Python/Proxy Issues\n\n**Symptoms**: \"Python not found\" or proxy connection errors\n\n**Solutions**:\n1. **Check Python 3 on remote**:\n   ```bash\n   ssh user@server \"python3 --version\"\n   ssh user@server \"which python3\"\n   ```\n\n2. **Verify proxy script permissions**:\n   ```bash\n   ls -la ~/.local/share/nvim/lazy/remote-ssh.nvim/lua/remote-lsp/proxy.py\n   ```\n\n3. **Check proxy logs**:\n   ```bash\n   ls -la ~/.cache/nvim/remote_lsp_logs/\n   ```\n\n#### Completion Not Working\n\n**Symptoms**: No autocomplete suggestions in remote files\n\n**Solutions**:\n1. **Check nvim-cmp configuration**:\n   ```vim\n   :lua print(vim.inspect(require('cmp').get_config()))\n   ```\n\n2. **Verify LSP client attachment**:\n   ```vim\n   :LspInfo\n   ```\n\n3. **Check LSP server capabilities**:\n   ```vim\n   :lua print(vim.inspect(vim.lsp.get_clients()[1].server_capabilities))\n   ```\n\n#### File Watcher Issues\n\n**Symptoms**: File watcher shows \"not a remote buffer\" or doesn't detect changes\n\n**Solutions**:\n1. **Check if file watcher is running**:\n   ```vim\n   :RemoteWatchStatus\n   ```\n\n2. **Test SSH connection manually**:\n   ```vim\n   :RemoteWatchDebug\n   ```\n\n3. **Verify SSH config alias setup**:\n   ```bash\n   # Test SSH config alias\n   ssh myserver \"echo 'SSH alias working'\"\n   ```\n\n4. **Check file watcher logs**:\n   ```vim\n   :AsyncWriteDebug  # Enable debug logging\n   :AsyncWriteLogLevel DEBUG\n   ```\n\n5. **Restart file watcher**:\n   ```vim\n   :RemoteWatchStop\n   :RemoteWatchStart\n   ```\n\n**Symptoms**: File watcher causing UI blocking or performance issues\n\n**Solutions**:\n1. **Increase poll interval**:\n   ```vim\n   :RemoteWatchConfigure poll_interval 10000  # 10 seconds\n   ```\n\n2. **Check for SSH connection multiplexing**:\n   ```bash\n   # Add to ~/.ssh/config\n   Host *\n       ControlMaster auto\n       ControlPath ~/.ssh/control-%r@%h:%p\n       ControlPersist 10m\n   ```\n\n### Debug Commands Reference\n\n```vim\n# LSP Debugging\n:RemoteLspDebug           # Show remote LSP client information\n:RemoteLspServers         # List available LSP servers\n:RemoteLspDebugTraffic on # Enable LSP traffic debugging\n:LspInfo                  # Show LSP client information\n:LspLog                   # View LSP logs\n\n# File Operation Debugging\n:RemoteFileStatus         # Show remote file operation status\n:AsyncWriteStatus         # Show async write operation status\n:AsyncWriteDebug          # Toggle async write debugging\n\n# File Watcher Debugging\n:RemoteWatchStatus        # Show file watcher status for current buffer\n:RemoteWatchDebug         # Test SSH connection and debug file watcher\n:RemoteWatchStart         # Start file watching for current buffer\n:RemoteWatchStop          # Stop file watching for current buffer\n\n# Dependency Checking\n:RemoteDependencyCheck    # Comprehensive dependency check with detailed report\n:RemoteDependencyQuickCheck  # Quick dependency status check\n\n# General Debugging\n:checkhealth              # General Neovim health check\n:Mason                    # Open Mason UI for server management\n:MasonLog                 # View Mason installation logs\n```\n\n### Performance Tips\n\n1. **Use SSH connection multiplexing**:\n   ```bash\n   # Add to ~/.ssh/config\n   Host *\n       ControlMaster auto\n       ControlPath ~/.ssh/control-%r@%h:%p\n       ControlPersist 10m\n   ```\n\n2. **Configure SSH keep-alive**:\n   ```bash\n   # Add to ~/.ssh/config\n   Host *\n       ServerAliveInterval 60\n       ServerAliveCountMax 3\n   ```\n\n3. **Optimize rsync transfers**:\n   ```bash\n   # For large files, consider compression\n   Host myserver\n       Compression yes\n   ```\n\n## ⚠️ Caveats\n\n- Language servers must be installed on the remote machine\n- SSH access to the remote machine is required\n- Performance depends on network connection quality\n- For very large projects, initial LSP startup may take longer\n\n## 📝 Tips for best experience\n\n1. **SSH Config**: Using SSH config file entries can simplify working with remote hosts\n2. **Language Servers**: Ensure language servers are properly installed on remote systems\n3. **Project Structure**: For best results, work with proper project structures that language servers can recognize\n4. **Network**: A stable network connection improves the overall experience\n\n## FAQ\n\n### Why use this plugin instead of just mounting remote directories locally?\n\nWhile mounting remote directories (via SSHFS, etc.) is a valid approach, it has several drawbacks:\n- Network latency affects every file operation\n- Syncing large projects can be time-consuming\n- Language servers running locally might not have access to the full project context\n\nThis plugin runs language servers directly on the remote machine where your code lives, providing a more responsive experience with full access to project context.\n\n### How does this differ from Neovim's built-in remote file editing?\n\nNeovim's built-in remote file editing doesn't provide LSP support. This plugin extends the built-in functionality by:\n1. Enabling LSP features for remote files\n2. Providing asynchronous file saving\n3. Handling the complexities of remote path translation for LSP\n4. Adding TreeSitter support for syntax highlighting\n5. Providing commands for browsing and searching remote directories\n\n## Comparison to other Remote Neovim Plugins\n1. **remote-nvim.nvim** (https://github.com/amitds1997/remote-nvim.nvim) - The most VS Code Remote SSH-like solution:\n   * Automatically installs and launches Neovim on remote machines\n   * Launches headless server on remote and connects TUI locally\n   * Can copy over and sync your local Neovim configuration to remote\n   * Supports SSH (password, key, ssh_config) and devcontainers\n   * **Limitations**: Plugin has not yet reached maturity with breaking changes expected\n   * Network latency inherent to the headless server + TUI approach\n   * Remote server may not be able to access generic internet content in some controlled developement environments\n\n2. **distant.nvim** (https://github.com/chipsenkbeil/distant.nvim) - Theoretically addresses latency:\n   * Alpha stage software in rapid development and may break or change frequently\n   * Requires distant 0.20.x binary installation on both local and remote machines\n   * Requires neovim 0.8+\n   * **Limitations**: Limited documentation and setup complexity; experimental status makes it unreliable for production use\n\n3. **This remote-ssh.nvim** (https://github.com/inhesrom/remote-ssh.nvim):\n   * Uses SSH for all file operations\n   * Syncs buffer contents locally to eliminate editing lag\n   * Only requires language server installation on remote (supports clangd for C++, pylsp for Python)\n   * Includes tree-based remote file browser (`:RemoteTreeBrowser`)\n   * Focused on simplicity and immediate usability\n   * **Limitations**: Plugin has not yet reached maturity with breaking changes expected\n\nThe key trade-off is between feature completeness (remote-nvim.nvim) and responsiveness (this plugin's local buffer approach).\n\n## 🔧 Development\n\nWant to contribute to remote-ssh.nvim? The Docker test container provides a complete local development environment, allowing you to test and develop plugin features without needing a separate remote server. This environment includes pre-configured language servers, test projects, and sample files to validate all plugin functionality.\n\n### Setting Up the Development Environment\n\n#### Prerequisites\n- Docker installed and running\n- SSH client available locally\n\n#### Step 1: Build and Start Container\n\n```bash\n# Make the build script executable\nchmod +x build-docker.sh\n\n# Build and start the container\n./build-docker.sh full\n\n# Or use Docker Compose directly\ndocker-compose up -d --build\n```\n\n#### Step 2: Set Up Passwordless SSH\n\n```bash\n# Copy your SSH key to the container (password: testpassword)\nssh-copy-id testuser@localhost\n\n# Or use the automated setup script\n./setup-ssh-keys.sh\n\n# Test the connection (should not prompt for password)\nssh testuser@localhost\n```\n\n#### Step 3: Test the Plugin\n\nOpen Neovim and try these commands:\n\n```vim\n\" Open a C++ test file with LSP support\n:RemoteOpen rsync://testuser@localhost//home/testuser/test-files/main.cpp\n\n\" Or browse the test directory\n:RemoteTreeBrowser rsync://testuser@localhost//home/testuser/test-files/\n\n\" Try a real-world project (LLVM)\n:RemoteOpen rsync://testuser@localhost//home/testuser/repos/llvm-project/clang/lib/Basic/Targets.cpp\n\n\" Test TUI session management\n:RemoteTui htop\n```\n\n### What's Included in the Container\n\n- **Language Servers**: clangd (C++), pylsp (Python), rust-analyzer (Rust)\n- **Test Projects**:\n  - **C++**: LLVM, Catch2, nlohmann/json\n  - **Python**: Django, Flask, FastAPI\n  - **Rust**: Tokio, Serde, Clap\n- **Simple Test Files**: `/home/testuser/test-files/` (main.cpp, main.py, main.rs)\n- **Pre-configured SSH**: User `testuser`, passwordless access after key setup\n\n### Managing the Container\n\n```bash\n# Check container status\n./build-docker.sh status\n\n# Connect to container via SSH\n./build-docker.sh connect\n\n# View container logs\n./build-docker.sh logs\n\n# Stop container\n./build-docker.sh stop\n\n# Restart container\n./build-docker.sh restart\n\n# Clean up everything\n./build-docker.sh clean\n```\n\n### Testing Plugin Features\n\nOnce you have remote files open, verify these features work correctly:\n\n- **Code Completion**: Type in test files and trigger completion (`Ctrl+Space` or configured trigger)\n- **Go to Definition**: Use `gd` or configured keybinding to jump to definitions\n- **Hover Documentation**: Press `K` to see type information and documentation\n- **Diagnostics**: Introduce syntax errors to verify error checking works\n- **File Watching**: Modify files externally (via SSH) and verify conflict detection\n- **Remote Tree Browser**: Navigate directories and open files\n- **TUI Session Management**: Hide/restore sessions with `Ctrl+H` and `:RemoteTui`\n\n### Connection Details\n\n- **SSH Host**: `localhost`\n- **SSH Port**: `22` (default)\n- **SSH User**: `testuser`\n- **SSH Password**: `testpassword` (only needed before SSH key setup)\n- **Test Repositories**: `/home/testuser/repos/`\n- **Simple Test Files**: `/home/testuser/test-files/`\n\n### Troubleshooting\n\n**Container won't start:**\n```bash\n# Check if port 22 is already in use\nlsof -i :22\n\n# If port 22 is taken, modify docker-compose.yml to use a different port:\nports:\n  - \"2222:22\"  # Use port 2222 instead\n```\n\n**SSH key setup fails:**\n```bash\n# Try manual key copy\ncat ~/.ssh/id_rsa.pub | ssh testuser@localhost \"mkdir -p ~/.ssh \u0026\u0026 cat \u003e\u003e ~/.ssh/authorized_keys\"\n\n# Or generate a new key specifically for Docker testing\nssh-keygen -t ed25519 -f ~/.ssh/id_docker_test\nssh-copy-id -i ~/.ssh/id_docker_test testuser@localhost\n```\n\n**LSP features not working:**\n```bash\n# Connect to container and verify language servers are installed\nssh testuser@localhost\nclangd --version\npylsp --version\nrust-analyzer --version\n```\n\n### Additional Resources\n\n- **Full Documentation**: See [`docs/DOCKER_TESTING.md`](docs/DOCKER_TESTING.md) for comprehensive container details\n- **Next Steps**: After testing, review the [Contributing](#-contributing) section below for guidelines on submitting changes\n\n## 🤝 Contributing\n\nContributions are welcome! Please read [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines.\n\n- Report bugs via GitHub Issues\n- Submit feature requests\n- Contribute code via Pull Requests\n- Improve documentation\n\n## Buy Me a Coffee\nIf you feel so inclined, out of appreciation for this work, send a coffee my way!\n[Buy Me a Coffee Link](https://coff.ee/inhesrom)\n\n## 📄 License\n\nThis project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.\n","funding_links":[],"categories":["Remote Development"],"sub_categories":["Indent"],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Finhesrom%2Fremote-ssh.nvim","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Finhesrom%2Fremote-ssh.nvim","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Finhesrom%2Fremote-ssh.nvim/lists"}