Share a Workflow by Link

The File > Share as Link... command turns the workflow on the canvas into one URL. Whoever opens the link sees the same workflow in their own NodeCrypto, with nothing to download and nothing stored on a server.

Create a Link

Build or open the workflow in the active tab. The command is disabled while the canvas is empty.
Choose File > Share as Link.... The dialog shows the link, its length, and a warning about values.
Press Copy and paste the link into a chat, an issue, or a document. If the browser blocks copying, the link is selected so that you can copy it yourself.

The workflow must pass the same design checks as saving: a node with a design error blocks the link, and so does a variable reference that has no value.

What Is in the Link

Included: nodes, wires, node positions and the canvas view, every setting, the values of constant nodes, the values of variables used by the workflow, node memos, and the definitions of any custom nodes it uses.
Variables are written as values. The link carries the value, not the variable name, so the receiver needs no variable registration and your registry names are not revealed.
Not included: the test run values of Workflow Input, run results, and your other variables and settings.
The link is the same data as a saved .ncw file, packed with Deflate and written in a URL-safe form.

When Someone Opens the Link

The app opens the workflow in a new tab (an untouched start tab is replaced) and shows a notice: it came from a link, so review it before running.
Nothing runs automatically. A Script node runs only when the person presses Run, inside the usual script sandbox.
The tab is unsaved and remembers no file. The title is the workflow name from the link.
A damaged, cut-off, too large, or newer-format link is refused with a message and no tab is created.
The link is read when the app starts. Pasting a link into the address bar of an app tab that is already open does not load it: open it in a new tab or reload.

Do Not Put Real Keys in a Link

Values are stored as plain text. The dialog warns about this every time. Use test vectors, never real secret keys.
The part after # is not sent to the NodeCrypto server, and nothing is stored there. But the link itself can remain in your browser history, in the servers of the messenger you paste it into, and in search indexes if you post it publicly.
Anyone who has the link can read every value in it. Sharing is not a way to protect secrets.

Size Limits

Link length	What happens
Up to 8,000 characters	Fine for chats, issues, and documents. Most example workflows are 1,200 to 4,000 characters.
Over 8,000 characters	The dialog warns that some messengers and boards may cut the link. Copying is still allowed.
Over 64,000 characters	No link is made. Save the workflow as an `.ncw` file and send the file instead.

Sharing needs a browser with compression support (Chrome 80, Firefox 113, Safari 16.4 or later). Otherwise the menu item is disabled.

From the Command Line and AI Agents

npx @curealls/nodecrypto share workflow.ncw prints the link of a workflow file or draft. --app <URL> sets another app address.
The MCP expand tool returns a shareUrl next to the saved file path, so an AI agent can hand you a link that opens in your browser. See AI Agent Integration.
Both put values in the link in plain text, like the dialog.