The Cloaky public beta has ended

The v0.2 beta is closed. Cloaky Base, free and open source on Venice's private tier, becomes the product everyone can run. Cloaky Pro goes heads-down on what the beta taught us.

The public beta of Cloaky ran from v0.2.0 on August 12 to v0.2.10 on September 11, on macOS and Linux. It is now closed. This post says what the beta was, what we took from it, and what comes next.

What the beta was

Eleven releases in a month. Each one shipped the whole workbench: every engine, every provider, local models, direct provider keys, Venice, fleet, bots and squads. Anyone could download it and run it on real work. People on both platforms did, and they wrote back. The feedback was specific, generous, and there was more of it than we expected. Thank you for it.

What we took from it

The part people kept naming was the route. The engine, the provider and the privacy tier in view at the point where the work happens: that is what people said they liked, and what they asked us to protect.

The feedback also pointed somewhere most of the current tooling is not looking. Reading it together, a few ideas kept surfacing about what an agent workbench should be doing for the person running it, ideas we think are breakthroughs and that almost nobody is building toward right now. They need time, quiet, and a small group of people who will use them on real work before we say more.

The split

Cloaky becomes two products.

Cloaky Base is free and open source. Every session runs on Venice’s private tier. Five engines, all on Venice models: Claude Code, OpenCode, Codex, Kimi Code and Grok Build. Nothing routes anywhere you did not turn on.

This is where we want to contribute first, because it is where it matters to us: Venice, and private tooling that puts ownership and agency back in the hands of the person doing the work. Base is that, made into a whole product, in the open, for everyone.

Cloaky Pro is the full workbench: every engine, including Cursor and Prime Agent; local models through Ollama and LM Studio; direct providers; fleet, bots and squads. Pro is going heads-down for three months of private build on the ideas above. We will describe them when they exist, not before.

What happens to the beta

The beta downloads and the beta release page go private. An installed beta keeps working, but it will not receive updates.

If you ran the beta and told us what you found, that is the reason the split looks the way it does.

How to get Pro

Pro has no public download during the private build. If you want it, email hello@cloaky.dev and say what you would do with it. A person reads every message, and we are choosing a small group to build with.

That group is the user study: a private net of people who help us build Pro, and who get Pro for it.

What’s next for Base

The source will be on GitHub under cloakydev/cloaky. The first release is v0.1.1. The number restarts because it is a new line, not a downgrade of the beta. Downloads will be on this site the day it ships, and the changelog picks up from there.