Install

Download Cloaky Base for macOS or Linux, add your Venice key, choose an engine, and start your first session.

Early software notice. Cloaky Base is a new line and not finished. Downloading, installing, connecting a provider, and approving agent actions can cause data loss, unexpected changes, privacy exposure, security issues, or provider charges. Keep backups and use the app only on work you can afford to risk. Read the Terms of Use and Safety & responsible use before installing.

Download Cloaky Base

Cloaky Base is free and open source. It runs on macOS and Linux, and every session runs on Venice’s private tier.

Early software. Download and use at your own risk. Keep backups, review permissions, and read the Terms and Safety guide before opening a build.

First launch on macOS

Open the .dmg, drag the app into Applications, and eject the disk image. The workbench and its server are inside the app; there is no separate terminal setup. Cloaky Base needs macOS 13 (Ventura) or later.

macOS builds are signed with an Apple Developer ID certificate and notarized by Apple, with the notarization ticket stapled to the app. First launch is a plain double-click, with no Gatekeeper approval step. If macOS says the app is damaged or cannot be verified, the download did not complete or did not come from cloaky.dev; delete that copy and download it again.

Install only builds downloaded from cloaky.dev. We do not guarantee that a build is free of malware, defects, or compatibility problems; the Terms of Use carry the full warranty disclaimer and liability limits.

Linux

Linux ships in three formats: an AppImage, a deb package and an rpm package. Open a deb or rpm with your distribution’s package installer. An AppImage needs the executable bit before it will run, so mark the file you downloaded executable with chmod +x and then run it. Your desktop may warn the first time.

Add your Venice key

Venice is the only inference destination in Cloaky Base. There is no second provider to configure and no other account involved: every session runs on Venice’s private tier, where prompt and response content is not retained after the request. Venice can still keep the operational metadata it needs for account, billing, abuse prevention, and reliability.

On first launch the app asks for a Venice API key, and then for a model. Both live in Settings → Providers & privacy → Venice, so you can change them later. The model picker shows the provider, the tier, the context window and the cost for each row, which is where you read the provider and privacy tier for a session before it starts.

The models offered by default are GLM 5.2, Qwen3 Coder, Kimi K2.7 Code and DeepSeek V4 Flash, which also supports E2EE + TEE for tool-free turns. The quick picks are Kimi K3, MiniMax M3 and DeepSeek V4 Flash. Turns that call structured tools run on Venice private, and the session badge reports the route that actually ran.

Choose an engine

Cloaky Base runs five engines, and all five send their model calls to Venice. Engines don’t come inside the app. On first launch, the Choose your engines step installs Claude Code, OpenCode, Codex and Kimi Code with one click, and they download while you finish setup. If one is already installed on your machine, Cloaky can use that copy. Grok Build installs with xAI’s own script from Settings → Engines, where any engine can be added, updated or removed later.

Start your first session

1. Launch Cloaky Base and open a project folder.
2. Add your Venice key in Settings → Providers & privacy → Venice.
3. Choose a model and read its provider and privacy tier in the picker.
4. Pick Claude Code or any other engine you installed.
5. Start a session and describe the work.

The default permission mode is Accept edits: file edits proceed, while shell commands and other consequential actions pause for your approval. Bypassing permissions is always an explicit choice.

From there the workbench is the rest of the app. Review the diff with line comments and commit or push from it; rewind to a restore point when a turn goes wrong; hand work to subagents; set up bots and squads with routines; watch the cost readout as the session runs.

Data and credentials

Cloaky Base stores settings, your Venice key, session and recovery metadata, cost records, command history and drafts on your device. Credentials stay on the device and are not sent to the browser. The engine you run may also keep its own transcripts.

Read Privacy before a sensitive session for what Venice’s private tier does and does not cover.

Updates

Cloaky Base doesn’t update itself yet. Download new versions from this page and replace the app. Settings, sessions and local records live outside the app and stay in place.

If you ran the public beta

The v0.2 public beta is closed. An installed beta build keeps working, but it will not receive any further updates. Cloaky Base installs beside it as a separate app, so you can keep the beta where it is and start Base fresh. The public beta has ended explains what changed and why.

Cloaky Pro

Local models through Ollama and LM Studio, direct providers such as a Claude subscription, an OpenAI-compatible endpoint or a GLM or Kimi coding plan, custom profiles, hybrid hosted planning with local execution, and the Cursor and Prime Agent engines are Cloaky Pro features. Pro is in a private three-month build with no public download.

To ask for it, email hello@cloaky.dev with what you would do with it. The user study group gets Pro. Routes in Base and Pro covers each route in detail.