vnsh

vnsh

One workspace all your AI agents can read and write

•

•

•

•

•

Right now you paste the same context into Claude Code, then Cursor, then Slack.

vnsh gives that context one address instead. Drop it once and get a link; every

agent and every person you hand it to opens the same living document, and can

change it. Encrypted in your browser before upload, so vnsh never sees it, and

deleted 24 hours after the last edit.

kubectl logs pod/app | vn
# https://vnsh.dev/w/k2p9xf...#w=...   edit link — read and write
# https://vnsh.dev/w/k2p9xf...#r=...   view-only — read, never write

Why this and not a pastebin

A pastebin gives you a snapshot. A workspace has a stable address and a version,

so the next agent writes back to the same place instead of starting a new one.

Two properties make that safe to share:

• The server cannot read it. Content is encrypted client-side and the key

rides in the URL fragment, which HTTP never transmits. What the server stores

is ciphertext and a SHA-256 of a write token — not the token. That is checkable

from outside: forge a token and you get a 403.

• Two agents cannot silently clobber each other. Writes are conditional on

the version you read. An unconditional write is refused outright; a stale one

gets a 412 telling you to re-read and merge. Measured in production with five

concurrent writers: one succeeded, four were told, nothing was lost.

Get started

For an agent — the point of the thing

Paste this into Claude Code, Cursor, OpenHands, Cline, Windsurf, Zed — anything

that speaks MCP:

Set up vnsh workspaces — one link to hand work between people and agents: https://vnsh.dev/llms.txt

It reads the protocol, installs the MCP server, and writes a standing rule into

its own instruction file so it keeps using workspaces afterwards. By hand

instead:

claude mcp add vnsh -- npx -y vnsh-mcp@1.8.2

The server exposes `vnsh_artifact_create`, `vnsh_artifact_list`,

`vnsh_artifact_read`, `vnsh_artifact_update`, `vnsh_workspace_create`, `vnsh_workspace_read`,

`vnsh_workspace_update`, `vnsh_workspace_history`, `vnsh_workspace_restore`,

`vnsh_workspace_renew` and `vnsh_workspace_open`, plus

`vnsh_share`, `vnsh_share_file` and `vnsh_read` for one-shot content.

From the terminal

npx vnsh                      # or: npm i -g vnsh
                              # or: curl -sL vnsh.dev/i | sh   (one-shot links only)

vn ./report.html              # create a workspace from a file
git diff | vn                 # or from stdin
vn read " ·
     ·
     ·