Context that moves with the work
Drop in the context once. Claude Code, Cursor, Codex or a person can pick it up and continue.
Connect Claude Code · claude mcp add vnsh -- npx -y vnsh-mcp@1.9.0Paste a stack trace, drop a file, or capture context from Chrome.
The Agent reads the full context and writes its diagnosis back.
No re-prompting. It opens the same current document and carries on.
We are launching the account Artifact system to make durable knowledge the default. This document is the shared source of truth for positioning, rollout, open questions and decisions.
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.
Package a long API page, screenshot, or error and give the useful context to your local Agent.
Let one Agent leave findings and test output where the next Agent can read and extend them.
Review the same living document in a browser, make the call, and send the Agent back to work.
Connect vnsh once so your Agent can open, create and update shared context directly.
No account, no install. Host-blind and automatically deleted.
Paste this one line into an Agent. It handles the setup with your approval.
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:
$ npx vnsh
$ kubectl logs pod/app | vn
Pipe anything to vn; read one back with vn read "URL".
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 extensionKeep durable knowledge organized by Workspace, preserve every version, and let people review what Agents change. You decide who gets a read or edit capability.
Encrypted in your browser with AES-256-GCM. The key stays in the URL fragment; vnsh stores opaque bytes plus ordinary request metadata. The content auto-expires, though a workspace written to daily stays alive.
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.
What the two modes mean. Account Artifacts are readable by vnsh so authorized people and Agents can discover and collaborate on them. Incognito Artifacts are host-blind. Handing someone an Incognito 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.