Claude Code · Cursor · OpenHands · Cline · Zed

One workspace all your agents can read and write.

Name: vnsh
Author: vnsh

Right now you paste the same context into Claude Code, then Cursor, then Slack. Drop it here once instead and get a link. Everyone opens the same living document — and can change it. Encrypted in your browser, so vnsh never sees it. Gone 24 hours after the last edit.

The key rides in the URL fragment, which is never sent to a server — so the workspace is hosted by a party that can never read it.

Try it

Make one right now

No account, no install. It encrypts before anything leaves this tab.

Drop a file or paste text

try ⌘V right now

Skip the encryption so agents can just fetch it. An encrypted link needs a key and something to run the decryption, so an agent with only fetch gets nothing from one until you set it up. This trades that away: a plain page at a plain URL — and vnsh can read it too.

1You get back an edit link and a view-only link.
2Anyone holding the edit link can change the document — agents included.
3It deletes itself 24 hours after the last edit.

> Encrypting...

✓ Workspace created

◯ 24h after last edit

Edit link

read + change

View-only link

read, never write

Now hand it to an agent. Paste the edit link into Claude Code or Cursor and ask it to add to the document — or

The whole point

Or never do it by hand again

Paste this one line into any agent. That’s the entire setup.

1It reads llms.txt and installs the vnsh MCP server itself.
2It asks whether to add a standing rule to this project's instruction file — CLAUDE.md, .cursorrules, whichever it uses. Your call.
3From then on it hands work off through workspaces without being asked, and opens any vnsh link you paste.

Claude Code · Cursor · OpenHands · Cline · Windsurf · Zed — anything that speaks MCP.

Rather do it by hand

Claude Code — writes the MCP config for you:

$ curl -sL vnsh.dev/claude | sh

Or register the server only:

$ claude mcp add vnsh -- npx -y vnsh-mcp

Anything else takes the standard MCP JSON:

"vnsh": { "command": "npx", "args": ["-y", "vnsh-mcp"] }

Use it from the terminal

$ npx vnsh

$ kubectl logs pod/app | vn

Pipe anything to vn; read one back with vn read "URL".

Chrome extension

Encrypted sharing from any page: ⌘D bundles a screenshot, console errors and the URL into one link. Hover any vnsh link for an inline preview.

Install extension

Why you can hand it a private log

vnsh can’t read it

Encrypted in your browser before upload. The key lives in the URL fragment, which is never transmitted. The server only ever holds opaque bytes.

AES-256-GCM · HKDF-SHA256

It deletes itself

24 hours after the last edit, the content is gone, and every edit restarts that clock — a workspace written to daily stays alive. What remains either way is ordinary request metadata: times, sizes, addresses. Never the content.

24H TTL · RENEWED ON WRITE

You can check all of this

The worker, the CLI and the MCP server are MIT-licensed and readable. The crypto is 200 lines; the server is a dumb pipe by design.

MIT · GITHUB.COM/RAULLENCHAI/VNSH

Two things we won’t oversell. Handing someone a link hands the key to whatever reads it — including that agent’s model provider. And the encryption runs in code this server sends you, so a future version of that code could keep your key: browser-delivered encryption protects you from a breach and a subpoena, not from vnsh deciding to change. Reproducible from the source above, and the 24-hour clock is what keeps either blast radius small.