ClipSafe for VS Code 1.1: What Changed

Version 1.1 rewrites the connection between the extension and the desktop app, so sending a snippet tells you what actually happened.

The ClipSafe extension for VS Code has one job. You select code, you press a shortcut, and the snippet shows up in your ClipSafe history. Version 1.0 did that, but it was optimistic about it. It wrote the snippet to the local pipe and reported success as soon as any bytes came back, without reading them. A snippet the app rejected and a snippet it saved looked exactly the same from the editor.

Version 1.1 replaces that with a real conversation. The extension reads the reply, checks it, and only then says the snippet was saved.

What was wrong in 1.0

  • Every failure was reported as "ClipSafe is not running", including cases where the app was running and had refused the payload.
  • There was no timeout. If the app accepted the connection and then stopped answering, the command waited forever and did nothing.
  • The app's reply was thrown away, so a rejected snippet was indistinguishable from a stored one.

What 1.1 does instead

  • Reads the reply and matches it to the request, so a send is only confirmed when ClipSafe confirmed it.
  • Gives up after four seconds with a clear message instead of hanging.
  • Retries once when the app is restarting and its pipe is briefly unavailable. It never retries after a snippet was delivered, so you do not get duplicates.
  • Keeps four cases apart: app not running, no reply, snippet rejected, and an unexpected reply.

Things you will notice while using it

  • A status bar item shows whether ClipSafe is reachable and which protocol version it speaks. Click it, or run ClipSafe: Check Connection, to check on demand.
  • The command is in the editor right click menu whenever you have a selection.
  • Several cursors send as one snippet, so a single keystroke stays a single history entry.
  • Selections above 200 KB ask before they are sent. The threshold is the clipsafe.maxSnippetSizeKb setting.
  • clipsafe.notifyOnSuccess turns the success notification off if you would rather not see it.
  • Everything is logged to the ClipSafe output channel, including byte counts, round trip times and the details of a failure.

Unchanged

Sending is still local. The extension talks to the desktop app over a named pipe on your own machine. Nothing is uploaded, there is no account and no telemetry, and the snippet lands in the same local database as everything else you copy.

The shortcut is still Ctrl + Shift + Alt + S. The extension needs Windows, because that is where the desktop app runs. Snippets arrive tagged with code and their file language, and their source reads VSCode/workspace-name, the same way it did before.

Version 1.1 is on the VS Code Marketplace now. The extension page covers setup, the two settings and what each error message means.