Share a notebook someone can actually run

Sharing a result usually means sharing a picture of one. You paste a chart into Slack, or a screenshot into a doc, and the thing that produced it — the code, the data, the six things you tried first — stays on your machine. The reader can look at your conclusion. They cannot check it, and they cannot start from it.

A Clusy share link opens the notebook itself: every cell, every output, every branch you kept. No account, no sign-up wall. And a Fork button that drops the whole thing into the reader's own workspace, running, where they can change a parameter and see what happens.

What the link carries

Hit Share and you get a short clusy.io/s/… link. Behind it is the notebook as it stands: the code, the outputs as they were produced, and the branches — so if you ran three variants, the reader sees three variants, not just the one you liked.

Pasted into Slack, X or LinkedIn, the link unfurls with a real preview card: the notebook's title, its author, how many cells and experiments it contains, and a cover image lifted from the notebook's own first image output. Your actual plot, in other words — not a grey box with a logo in it.

Fork is the point

A read-only notebook is a nicer screenshot. The reason to share a notebook rather than a picture of one is that the reader can run it.

Forking copies the notebook into their workspace with its cells and structure intact. They can change a hyperparameter and re-run, swap the dataset for theirs, or take a branch you abandoned and push it further. What you shared stops being an artifact and becomes a starting point.

If you want the work discoverable rather than just linkable, publishing to the Hub gives it a public page and puts it on a portfolio under your name.

Visibility

Three states, and the difference matters:

• Private — only you.
• Unlisted — anyone with the link can open it. It is not listed anywhere and it is not indexed. This is the default when you create a share link.
• Public — listed on the Hub, indexed, and shown on your portfolio.

A shared notebook is a snapshot, not a live mirror: it does not keep updating as you keep working. Revoke a link and it stops resolving.

What we fixed to make this usable

Two things were quietly wrong, and both are worth naming because they are exactly the kind of bug that makes a feature technically present and practically useless.

Long shared notebooks went blank as you scrolled. The read-only viewer rendered every code cell as a full CodeMirror editor, and CodeMirror virtualizes against the window — so it happily decided most of your cells were offscreen and stopped painting them. A reader scrolling a long lab hit stretches of empty page. Code cells in the viewer are now plain rendered text, which is all a reader needed anyway.

And Hub links did not open when signed out, which is a remarkable thing to discover about a feature whose entire purpose is being sent to people who do not have an account. The public routes were mounted outside the auth guard correctly, but a layout inside them fetched the signed-in profile unconditionally and threw. Fixed.

Availability

Sharing is live for everyone.

What's next

Comments on a shared notebook, so a reader can push back on a specific cell rather than in a reply somewhere else.