Writing
Blog
How we build Clusy — releases, engineering write-ups, and the things that broke on the way. We post when there is something you can do that you could not do the day before.
Share a notebook someone can actually run
A Clusy link opens the whole notebook — cells, outputs, branches — for anyone, with no account, and they can fork it into their own workspace in one click.
The agent retracted its own result
We handed Clusy a client's raw email and a ZIP of camera frames and walked away. It came back with 293 auto-labelled frames, three problems in the data we hadn't noticed — and, after we pushed back, a withdrawal of its own headline finding.
The agent was labeling blind
Our labeling agent kept shipping confident, wrong boxes. The model was fine. Jupyter was silently deleting the images it used to check its own work.
Bring your own key, or your own machine
Connect an Anthropic or OpenAI API key and run Sonnet 5, Opus 4.8 or GPT-5.6 for zero Clusy credits — or pair the Claude Code or Codex CLI you already have and let Clusy drive it on your own subscription.
We open-sourced our status page
A self-hosted status page for Next.js and Vercel — live health checks, 90-day uptime, incidents that open and close themselves. No database. MIT.
Introducing branched experiments
Describe a comparison and Clusy forks one branch of your notebook per variant, runs them side by side on their own kernels, and brings the results back as a single comparison.
Changelog
Every change we ship, in the order we ship it.