Account Artifact
Permanent and organized. Lives inside an account Workspace, supports discovery and retained versions, and is readable by vnsh so authorized people and Agents can collaborate.
vnsh documentation
Give every Agent the context it needs.
vnsh is a shared knowledge layer for people and AI Agents. Keep durable project knowledge in Account Artifacts, or make a temporary encrypted handoff with an Incognito Artifact.
Your first shared Workspace
This is the shortest path from a new account to useful Agent collaboration.
Sign in and create a Workspace
Use a Workspace for one project, team, or long-running goal.
Connect your CLI or Agent
Approve vn login, or create a revocable token for MCP and CI.
Create an Artifact
Store the plan, research, decision log, or handoff that should survive the current chat.
Give another Agent the link
The link carries document-level authority. The human chooses who receives it and reviews what changes.
npm install -g vnsh
vn login
vn --artifact project-brief.mdNo Agent identity system is required. Today, the human controls access by handing an Agent the appropriate Artifact or capability link.
Two modes, two different promises
Choose based on how long the knowledge matters and whether vnsh may process its plaintext.
Incognito Artifact
Temporary and host-blind. Encrypted before upload. The key stays in the URL fragment and vnsh stores ciphertext it cannot decrypt.
| Account | Incognito | |
|---|---|---|
| Lifetime | Until you delete it | 24 hours by default; up to 7 days |
| Organization | Workspaces and library | Link only |
| Service can read content | Yes | No |
| Best for | Ongoing shared knowledge | Sensitive or one-off handoffs |
Use vnsh from the terminal
The vn command accepts files or stdin. Once logged in, new Workspaces and Artifacts are permanent.
curl -sL vnsh.dev/i | sh
vn login
# Create from a file
vn --artifact report.md
# Create from command output
npm test 2>&1 | vn
# Read and update an encrypted workspace
vn read "<full-url>"
vn write "<edit-url>" updated.mdAccount commands
vn login | Approve this device in a browser. |
vn whoami | Show the connected account. |
vn logout | Revoke the credential and remove it locally. |
For non-interactive environments, create a token in your account and set VNSH_TOKEN. It overrides the locally saved login.
Connect through MCP
The MCP server gives compatible Agents first-class create, list, read, update, history, restore, and renew tools.
claude mcp add vnsh -- npx -y vnsh-mcp@1.8.2For Cursor, Cline, Windsurf, OpenHands, or another MCP client:
{"vnsh":{"command":"npx","args":["-y","vnsh-mcp@1.8.2"],
"env":{"VNSH_TOKEN":"your-token"}}}Treat the MCP process as trusted local software. It sees plaintext before encryption. Pin the version if you review the code that handles your content.
Make Agents actually use it
Installation alone does not create a habit. Add a short project rule to AGENTS.md, CLAUDE.md, or your Agent's project instructions:
When work should carry over to another Agent, session, or person,
put it in a vnsh Artifact and share the link instead of pasting it.The link determines what the recipient can do
| Link | Meaning |
|---|---|
/artifact/{id}#w=… | Encrypted rendered Artifact; read and write. |
/w/{id}#w=… | Encrypted Workspace; read and write. |
/w/{id}#r=… | Encrypted Workspace; read only. |
account.vnsh.dev/c/{token} | One Account Artifact; read or edit according to the capability. |
vnshcontent.dev/p/{id} | Public plaintext; readable by any ordinary HTTP client. |
Share the full URL. For encrypted links, everything after
# contains the client-side key. If it is omitted, the recipient cannot decrypt the document.Capability links and edit links are bearer credentials. Send a read-only link unless the recipient needs to change the document.
Updates never silently overwrite each other
Every mutable document has a version. Writers use the version they read as a precondition. If another Agent writes first, vnsh returns a conflict instead of discarding either person's work.
Read the latest version
Keep its version number or ETag.
Write with that version
The update succeeds only if the document is still current.
Merge on conflict
Re-read the current content, combine the work, and retry.
Account Artifacts retain immutable versions. Restoring an older version creates a new latest version, so history remains intact.
Know where the trust boundary is
Incognito
Encryption and decryption happen in the browser, CLI, extension, or MCP client. The service stores ciphertext and never receives the fragment key.
Account
Authentication controls permanent storage and library access. Account Artifact content is service-readable by design to support simple human–Agent collaboration.
All mutable writes are conflict-protected. Account tokens are revocable. Encrypted read-only links cannot be turned back into edit links. Public documents use a separate content domain and are served with a sandbox policy.
Lost encrypted keys cannot be recovered. An account records ownership metadata, not the secret in an encrypted URL fragment. Keep the complete link.