Vnsh

by raullenchai

154 downloads
Not rated
GitHub

About

<p align="center"> <img src="https://vnsh.dev/logo.svg" alt="vnsh logo" width="120" /> </p> <h1 align="center">vnsh</h1> <p align="center"> <strong>The Ephemeral Dropbox for AI</strong> </p> <p align="center"> <a href="https://github.com/raullenchai/vnsh/actions"><img…

Details

Author
raullenchai
Downloads
154
Categories
Developer Tools, File Management, Security, Other

- Host-blind architecture: server stores only encrypted blobs, cannot decrypt
- Automatic vaporization: data disappears after 24 hours
- Client-side AES-256-CBC encryption; decryption keys stay in URL fragment
- Supports screenshots, logs, git diffs, binaries, and debug context
- First-party MCP server for Claude Code
- Self-hostable on Cloudflare Workers with R2 storage

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

  1. Download and install Highlight from highlightai.com/download
  2. Navigate to the plugins tab and select "Add Custom Plugin"
  3. Configure the plugin with the settings below
    Plugin Name Vnsh
    Command (node, npx, python, etc.)

    Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.

  4. Enable "Start Automatically" if you want the plugin to start when Highlight launches

From the repository

Install the MCP server by creating a .mcp.json file in your project root with "command": "npx", "args": ["-y", "vnsh-mcp"]. After restarting Claude Code, you can paste vnsh links for automatic reading, or use the tools vnsh_share (to share text outputs) and vnsh_share_file (to share images, PDFs, binaries). Alternatively, upload via the web, CLI (npx vnsh), a zero-install pipe script, a Chrome extension, or a GitHub Action.

vnsh_read

Reads any vnsh URL: decrypts legacy vnsh.dev/v links locally, or directly fetches a public vnshcontent.dev/p link. Public content is intentionally unencrypted.

vnsh_share

Encrypts text content locally and uploads it to vnsh, returning a shareable URL. Use this when output exceeds ~50 lines or ~2000 characters, when generating complete code files, or when the user wants portable/shareable output. ALWAYS prefer vnsh_share over dumping large content into chat. The content is encrypted before upload - the server only sees encrypted bytes.

vnsh_share_file

Encrypts a local file and uploads it to vnsh, returning a shareable URL. Use this for images, screenshots, PDFs, binaries, or any file that should not be loaded into context. More efficient than vnsh_share for large or binary files.

vnsh_artifact_create

Creates a permanent, service-readable Account Artifact in the signed-in user’s Library. Use this for durable knowledge that the user wants their other Agents to discover and update. Requires VNSH_TOKEN. This is different from an encrypted Incognito workspace: vnsh can read Account Artifact content so authorized Agents can collaborate on it.

vnsh_artifact_list

Lists permanent Account Artifacts available to the connected user. Use this instead of asking the human to paste a link when continuing earlier account knowledge. Requires VNSH_TOKEN.

vnsh_artifact_read

Reads the current content and version of one permanent Account Artifact. Pass the returned version to vnsh_artifact_update so another Agent cannot be overwritten.

vnsh_artifact_update

Creates a new immutable version of an Account Artifact. Requires the base_version returned by vnsh_artifact_read. On conflict, re-read, merge, and retry; never silently overwrite.

vnsh_workspace_create

Creates a shared workspace and returns one link that any agent can read AND write. Use this when work will continue somewhere else: handing a plan, status doc, design, or investigation to another agent or another session, or when the user says they will pick this up in a different tool. Unlike vnsh_share (a one-shot snapshot), a workspace keeps the same URL as its content evolves. Content is encrypted locally; the server never sees the key. Anonymous workspaces expire 24h after the last write (ttl can extend this to a week). With VNSH_TOKEN, new workspaces and artifacts are kept until the account owner deletes them.

vnsh_workspace_renew

Extends the expiry of a vnsh workspace without changing its content. Use this when the user says a link is about to expire, or asks to keep something alive longer. Needs the edit link (a #w= fragment); a view-only #r= link cannot renew. The version is not bumped, so any pending edit still applies.

vnsh_workspace_read

Reads the current content of a workspace: encrypted /w/ links with #w= or #r=, and public /p/ links with no fragment. Use this whenever the user provides such a link — it is how you pick up work another agent left for you. Returns the content and its version number; pass that version to vnsh_workspace_update to write safely.

vnsh_workspace_update

Replaces the content of a vnsh workspace, keeping the same URL. Use this to record progress so far, revise a shared plan, or leave the next agent an updated document. Writes are version-checked: if someone else wrote first, this returns their current content so you can merge it with yours and call this again.

vnsh_workspace_open

Decrypts a vnsh workspace to a local temp file and opens it in the browser. Use this when the user wants to LOOK at a workspace rather than have its content read into context — HTML reports, dashboards, and diagrams render properly this way. Rendering happens locally from file://, so nothing is exposed to any server.

vnsh_workspace_history

Lists the retained versions of a workspace, newest first. Use this before restoring after a bad edit or merge. The current version plus the latest historical versions are retained.

vnsh_workspace_restore

Restores a retained workspace version as a new latest version. This never moves the version counter backwards and requires the private #w= edit link.

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

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

McpServers

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

<p align="center">
vnsh logo
</p>

<h1 align="center">vnsh</h1>

<p align="center">
<strong>The Ephemeral Dropbox for AI</strong>
</p>

<p align="center">
<a href="https://github.com/raullenchai/vnsh/actions">Build Status</a>
<a href="https://www.npmjs.com/package/vnsh">npm vnsh</a>
<a href="https://www.npmjs.com/package/vnsh-mcp">npm vnsh-mcp</a>
<a href="https://github.com/raullenchai/upload-to-vnsh">GitHub Action</a>
<a href="LICENSE">License</a>
</p>

<p align="center">
<a href="https://vnsh.dev">Website</a> •
<a href="#quick-start">Quick Start</a> •
<a href="#how-it-works">How It Works</a> •
<a href="#self-hosting">Self-Hosting</a> •
<a href="#api-reference">API</a>
</p>

---

What is vnsh?

<p align="center">
vnsh demo
</p>

Stop pasting walls of text into Claude. Pipe your logs, diffs, and images into a secure, host-blind URL. The server sees nothing. The data vaporizes in 24 hours.

# Pipe anything to vnsh, get a secure link
git diff | vn

https://vnsh.dev/v/aBcDeFgHiJkL#R_sI4DHZ_6jNq6yqt2ORRDe9QZ5xQB6hIRLWHVFa8v8

Handles any context your AI needs:

- 🖼️ Screenshots — UI bugs, error dialogs, terminal output
- 📜 Logs — 5000+ lines of server errors (too long for copy-paste)
- 🔄 Git Diffs — Complex PR reviews, multi-file changes
- 📦 Binaries — PDFs, CSVs, config files, database dumps
- 🔧 Debug Context — Stack traces, environment dumps, crash reports

Philosophy

> "Built for the ephemeral nature of AI workflows. Once your session is done, the data should be too."

Unlike Dropbox or pastebins, vnsh implements a Host-Blind Architecture with automatic vaporization:

| Layer | What Happens |
|-------|--------------|
| Encryption | AES-256-CBC encryption happens entirely on your device |
| Transport | Decryption keys travel only in the URL fragment (#secret) — never sent to servers |
| Storage | Server stores encrypted binary blobs — host-blind, no access to contents |
| Vaporization | Data vaporizes after 24 hours. No history. No leaks. |

Quick Start

Option 1: Web Upload

Visit vnsh.dev, drag & drop a file, or paste text. Get an encrypted link instantly.

Option 2: CLI Installation

Zero-install (just run it):

echo "hello" | npx vnsh

NPM (global install):

npm install -g vnsh

Shell script (cross-platform: macOS, Linux, WSL, Git Bash):

curl -sL https://vnsh.dev/i | sh

CLI Usage

# Upload a file
vn secrets.env

Pipe from stdin

cat crash.log | vn docker logs app | vn git diff HEAD~5 | vn

Read/decrypt a URL

vn read "https://vnsh.dev/v/aBcDeFgHiJkL#R_sI4DHZ..."

Custom expiry (1-168 hours)

vn --ttl 1 temp-file.txt # expires in 1 hour

Show version and help

vn --version vn --help

Option 3: Claude Code (MCP Integration)

Native to Claude Code. Unlike Dropbox, vnsh has a first-party MCP server. Claude can "see" inside your encrypted links without leaving the terminal.

Create .mcp.json in your project root:

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

Restart Claude Code after adding the config. Now Claude can:
- Read vnsh links automatically when you paste them
- Share large text outputs via vnsh_share tool
- Share files (images, PDFs, binaries) via vnsh_share_file tool

Option 4: Zero-Install (Remote Servers)

No installation needed. Pipe anything from any server with just curl and openssl:

# One-liner: encrypt and upload from any machine
cat error.log | bash <(curl -sL vnsh.dev/pipe)

https://vnsh.dev/v/aBcDeFgHiJkL#R_sI4DHZ_6jNq6yqt2ORRDe9...

Works with any command

kubectl logs pod/crash | bash <(curl -sL vnsh.dev/pipe) docker logs app 2>&1 | bash <(curl -sL vnsh.dev/pipe) journalctl -u nginx --since "1 hour ago" | bash <(curl -sL vnsh.dev/pipe)

Custom TTL (hours)

cat secrets.env | bash <(curl -sL vnsh.dev/pipe?ttl=1)

Perfect for SSH sessions, CI runners, Docker containers — anywhere you can't install tools.

Option 5: Chrome Extension

One-click encrypted debug bundles for AI. Share text, screenshots, and console errors directly from your browser.

- Right-click any selected text → Share via vnsh
- Cmd+Shift+DAI Debug Bundle (screenshot + console errors + selected text + URL, all encrypted)
- Hover over vnsh links on any page → see decrypted preview tooltip

Build from source or install from the Chrome Web Store (pending review):

cd extension && npm install && npm run build

Load dist/ as unpacked extension in chrome://extensions/

See extension/README.md for full documentation.

Option 6: GitHub Action (CI/CD)

Debug CI failures with Claude in one click. When your CI fails, automatically upload logs and post a secure link to your PR.

- name: Debug with vnsh
  if: failure()
  uses: raullenchai/upload-to-vnsh@v1
  with:
    file: test.log
  env:
    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

The action will post a comment to your PR:

> 🔍 Debug with Claude
>
> CI logs uploaded securely. View Logs | Paste link to Claude for instant analysis

See upload-to-vnsh for full documentation.

How It Works

┌──────────────────────────────────────────────────────────────────────────┐
│                              YOUR DEVICE                                  │
│  ┌─────────┐    ┌──────────────┐    ┌─────────────────────────────────┐  │
│  │  Data   │───▶│ AES-256-CBC  │───▶│  Encrypted Blob + URL Fragment  │  │
│  └─────────┘    │  Encryption  │    │  https://vnsh.dev/v/id#k=...    │  │
│                 └──────────────┘    └─────────────────────────────────┘  │
└──────────────────────────────────────────────────────────────────────────┘
                                           │
                           Only encrypted blob sent to server
                           (key stays in URL fragment, never transmitted)
                                           ▼
┌──────────────────────────────────────────────────────────────────────────┐
│                           VNSH SERVER (BLIND)                             │
│                                                                           │
│   Receives: [encrypted binary blob]                                       │
│   Stores:   [encrypted binary blob]                                       │
│   Knows:    upload time, size, expiry                                     │
│   Cannot:   decrypt, identify content type, read keys                     │
│                                                                           │
└──────────────────────────────────────────────────────────────────────────┘

URL Structure (v2 — compact format)

https://vnsh.dev/v/aBcDeFgHiJkL#R_sI4DHZ_6jNq6yqt2ORRDe9QZ5xQB6hIRLWHVFa8v8jYCFqgQIbsRJrtJze_nL5
                  └────────────┘└────────────────────────────────────────────────────────────────────┘
                  12-char ID     64-char base64url secret (key+iv, never sent to server)

The v2 format reduces URL length by ~40% (from ~160 to ~95 characters). Legacy v1 URLs (#k=...&iv=...) are still fully supported.

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.