{"id":"vscode-open-remote","repo":"panrafal/paseo-plugins","url":"https://github.com/panrafal/paseo-plugins/tree/main/vscode-open-remote","name":"vscode-open-remote","description":"Composer pill that opens a remote agent's working directory in VS Code, Cursor, or vscode.dev on tablet.","categories":["productivity"],"platforms":[],"caveats":["Hidden on phones. Tablets need a VS Code tunnel whose name matches the Paseo host","Install on each remote daemon; a local install also adds pills there"],"images":["https://raw.githubusercontent.com/panrafal/paseo-plugins/004c6a80c6aa8e76bb563694c3eee5c2c0b0466f/vscode-open-remote/images/vscode-open-remote-pill.png","https://raw.githubusercontent.com/panrafal/paseo-plugins/004c6a80c6aa8e76bb563694c3eee5c2c0b0466f/vscode-open-remote/images/vscode-open-remote-settings.png"],"themes":[],"health":{"manifestValid":true,"hasReadme":true,"hasLicense":true,"hasTests":false,"hasTypecheckScript":true,"updatedRecently":true},"scannedAt":"2026-10-15T12:35:06.376Z","addedAt":"2026-09-10T11:29:03+03:00","path":"vscode-open-remote","version":"0.1.0","security":{"status":"failed","blockingFindings":1,"advisoryFindings":0,"scannedAt":"2026-10-15T12:14:24.405Z","commit":"004c6a80c6aa8e76bb563694c3eee5c2c0b0466f"},"author":"panrafal","license":"MIT","paseoVersionRequirement":">=0.7.2-0","descriptionNodes":[{"type":"text","text":"Composer pill that opens a remote agent's working directory in VS Code, Cursor, or vscode.dev on tablet."}],"caveatNodes":[[{"type":"text","text":"Hidden on phones. Tablets need a VS Code tunnel whose name matches the Paseo host"}],[{"type":"text","text":"Install on each remote daemon; a local install also adds pills there"}]],"manifest":{"id":"vscode-open-remote","requirements":{"paseo":">=0.7.2-0"}},"repoMeta":{"stars":6,"defaultBranch":"main","pushedAt":"2026-10-15T04:33:35Z"},"owner":{"login":"panrafal","avatarUrl":"https://avatars.githubusercontent.com/u/1268900?v=4"},"installNotesHtml":"

Install this plugin on each remote Paseo daemon whose agents should get the pill. Plugin\ncontributions are daemon-scoped; the current Paseo plugin API does not expose whether an installation\nis local to a particular client, so installing it on a local daemon will also add pills there.

\n
paseo plugin add panrafal/paseo-plugins:vscode-open-remote\n
\n

From a checkout:

\n
npm install\nnpm run typecheck\npaseo plugin install /absolute/path/to/paseo-plugins/vscode-open-remote\npaseo plugin ls\n
\n

After editing:

\n
npm run typecheck\npaseo plugin reload vscode-open-remote\npaseo plugin logs vscode-open-remote\n
\n

The desktop machine needs VS Code's Remote - SSH extension or Cursor's Remote SSH support, and the\nPaseo host name must resolve through the desktop machine's SSH configuration.

","limitationsNotesHtml":"","readmeText":"# vscode-open-remote\n\nPaseo plugin that adds an **Editor** composer pill to every active agent on the daemon where\nthe plugin is installed. Pressing it opens the agent's current working directory — the project\ndirectory or its worktree — through the Paseo host name.\n\n![Editor pill](./images/vscode-open-remote-pill.png)\n![Remote editor settings](./images/vscode-open-remote-settings.png)\n\nDesktop links use one of these prefixes:\n\n| Editor | URL |\n| --- | --- |\n| VS Code (default) | `vscode://vscode-remote/ssh-remote+` |\n| Cursor | `cursor://vscode-remote/ssh-remote+` |\n| Custom | `` |\n\nOpen **Settings → Plugins → vscode-open-remote → Remote editor** to select VS Code, Cursor,\nor an arbitrary URI prefix. **Configure remote editor** in the Command Center opens the same\nnative settings screen (requires Paseo’s `addSettingsScreen`, `openSettings`, and\n`@getpaseo/plugin/client/ui` APIs). The setting is stored under\n`$PASEO_HOME/plugin-data/vscode-open-remote/settings.json` on that daemon and shared by its clients.\nExisting saved choices are preserved.\nPaseo owns the settings navigation, scrolling, responsive layout, and theme.\n\nPaseo's native opener only accepts HTTP(S), so desktop editor protocols use a short-lived protocol\nwindow. The plugin closes it automatically after handing the URL to VS Code, Cursor, or the chosen\ncustom editor.\n\nThe pill is hidden on phones (mobile devices whose shortest screen side is under 600 logical\npixels). On tablets, it instead opens:\n\n```text\nhttps://vscode.dev/tunnel/\n```\n\nVS Code for the Web cannot connect over Remote SSH. A [VS Code Remote Tunnel](https://code.visualstudio.com/docs/remote/tunnels)\nmust already be running on the daemon machine, and its tunnel name must match the host name configured\nin Paseo.\n\n## Limitations\n\n- The pill is hidden on phones. Tablets open vscode.dev and need a tunnel whose name matches the\n Paseo host.\n- Install it on each **remote** daemon you care about. The plugin API cannot hide the pill on a\n local daemon, so a local install also adds pills there.\n- Desktop opening needs VS Code Remote - SSH or Cursor Remote SSH, and the Paseo host name must\n resolve in the desktop machine's SSH config.\n\n## Install\n\nInstall this plugin on each **remote** Paseo daemon whose agents should get the pill. Plugin\ncontributions are daemon-scoped; the current Paseo plugin API does not expose whether an installation\nis local to a particular client, so installing it on a local daemon will also add pills there.\n\n```bash\npaseo plugin add panrafal/paseo-plugins:vscode-open-remote\n```\n\nFrom a checkout:\n\n```bash\nnpm install\nnpm run typecheck\npaseo plugin install /absolute/path/to/paseo-plugins/vscode-open-remote\npaseo plugin ls\n```\n\nAfter editing:\n\n```bash\nnpm run typecheck\npaseo plugin reload vscode-open-remote\npaseo plugin logs vscode-open-remote\n```\n\nThe desktop machine needs VS Code's Remote - SSH extension or Cursor's Remote SSH support, and the\nPaseo host name must resolve through the desktop machine's SSH configuration.\n"}