paseo.cafe
All plugins

vscode-open-remote

by panrafal

Composer pill that opens a remote agent's working directory in VS Code, Cursor, or vscode.dev on tablet.

v0.1.0 Requires Paseo >=0.7.2-0

Gallery

Install

Exact install target unavailable. Refresh after the next successful scan.

Git security status and fallback installation are pinned to commit 004c6a80c6aa.

From the plugin's README

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

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

From a checkout:

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

After editing:

npm run typecheck
paseo plugin reload vscode-open-remote
paseo plugin logs vscode-open-remote

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

README

vscode-open-remote

Paseo plugin that adds an Editor composer pill to every active agent on the daemon where the plugin is installed. Pressing it opens the agent's current working directory — the project directory or its worktree — through the Paseo host name.

Desktop links use one of these prefixes:

Editor URL
VS Code (default) vscode://vscode-remote/ssh-remote+<host><cwd>
Cursor cursor://vscode-remote/ssh-remote+<host><cwd>
Custom <configured-prefix><host><cwd>

Open Settings → Plugins → vscode-open-remote → Remote editor to select VS Code, Cursor, or an arbitrary URI prefix. Configure remote editor in the Command Center opens the same native settings screen (requires Paseo’s addSettingsScreen, openSettings, and @getpaseo/plugin/client/ui APIs). The setting is stored under $PASEO_HOME/plugin-data/vscode-open-remote/settings.json on that daemon and shared by its clients. Existing saved choices are preserved. Paseo owns the settings navigation, scrolling, responsive layout, and theme.

Paseo's native opener only accepts HTTP(S), so desktop editor protocols use a short-lived protocol window. The plugin closes it automatically after handing the URL to VS Code, Cursor, or the chosen custom editor.

The pill is hidden on phones (mobile devices whose shortest screen side is under 600 logical pixels). On tablets, it instead opens:

https://vscode.dev/tunnel/<host><cwd>

VS Code for the Web cannot connect over Remote SSH. A VS Code Remote Tunnel must already be running on the daemon machine, and its tunnel name must match the host name configured in Paseo.

Limitations

  • The pill is hidden on phones. Tablets open vscode.dev and need a tunnel whose name matches the Paseo host.
  • Install it on each remote daemon you care about. The plugin API cannot hide the pill on a local daemon, so a local install also adds pills there.
  • Desktop opening needs VS Code Remote - SSH or Cursor Remote SSH, and the Paseo host name must resolve in the desktop machine's SSH config.

Install

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

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

From a checkout:

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

After editing:

npm run typecheck
paseo plugin reload vscode-open-remote
paseo plugin logs vscode-open-remote

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

Scanned 15 Oct 2026, 12:35 UTC from panrafal/paseo-plugins/vscode-open-remote.