Cloaky
Releases
Docs

Safety & responsible use

Practical boundaries for prompts, permissions, providers, and AI-generated work while Cloaky Base is early software.

Effective date: October 24, 2026. Cloaky is a coding-agent workbench, not a safety guarantee. The app can help you inspect routes and approve consequential actions, but you are still the person responsible for the project, the provider you select, and the commands you allow to run.

Keep a human in the loop

Treat model output as a proposal, not a source of truth. Read diffs, review commands, run tests, check dependency licenses, and verify the result against the original requirement. Do not let Cloaky be the only reviewer for code that handles money, health, identity, safety, security, access control, or other high-impact decisions.

There are four permission modes: Plan (read-only), Approve for me (asks for edits and commands), Accept edits (asks for commands), and Full access (never asks). On a new install, the default permission mode is Accept edits.

In Accept edits and Approve for me, Claude Code, Kimi Code, and Grok Build pause shell commands, web access, and MCP calls for approval. OpenCode and Codex apply their own rules and can run shell commands without asking; the session’s privacy note says so.

Full access can only be chosen in the app window on this computer, when a session starts or as the default in Settings. A session that is already running cannot switch into it, and a session started by a teammate or another device never gets it. Schedules have their own modes, below. Choose Full access deliberately; a model can make a mistake at machine speed.

Know what approval and Undo cover

Approval is a review step, not a sandbox. Once you approve an action, or the mode allows it, it runs with your user’s permissions. Two settings in Settings → General, both off by default, narrow this: Sandbox command execution, and Container isolation, which confines files to the project’s folders but leaves the network open. With either on, shell commands can run without an approval card. Open untrusted projects in a disposable account or virtual machine. Cloaky asks before a repository’s own hooks or MCP servers run at session start.

Undo restores a turn’s file changes, but not every change. A file over the checkpoint size limit has no Undo, and Undo never reverses what a command did outside the project, such as a push, a deploy, or a network call. Keep backups anyway.

Unattended work

Teammates, routines, scheduled tasks, and goals run without you watching. A schedule’s mode is chosen up front: Read-only (the default), Edits, which may change files in the project, or Full access, which runs any tool, including shell commands. A goal stops starting new work at its budget, which can be at most $100.

Protect secrets and sensitive data

  • Keep API keys, passwords, private keys, tokens, and recovery codes out of prompts, issues, screenshots, support messages, and committed files.
  • Do not send personal, confidential, regulated, or third-party data to a provider unless you are authorized and the selected route is appropriate.
  • Cloaky Base always sends inference to Venice. If inference must stay on your machine, Base is not the right tool; Cloaky Pro adds local models. Either way, inspect any network-capable tool you approve.
  • Keep independent backups before allowing an agent to edit or delete files.

In the model picker, a model with no label is on Venice’s private, zero-retention tier; any other tier is labeled, such as Enclave or Identity only. The session’s privacy note warns when a turn ran below the private tier, when an enclave model fell back to sending unencrypted, or when the session runs through an engine’s own CLI. Neither means every network operation stayed with Venice: web access, MCP servers, registries, update checks (off unless you turn them on), and approved shell commands can create separate routes.

Verify providers and downloads

Venice and the tools you connect (Cloaky Pro adds direct providers and local model services) have their own terms, retention policies, pricing, and security properties. Read those terms before connecting an account. Cloaky does not guarantee a third party’s availability, output, retention, or security.

Download Cloaky Base from cloaky.dev and pick the build for your system and architecture. The macOS app is signed and notarized; if macOS says it is damaged or cannot be verified, delete it and download it again. Early builds can contain defects, break compatibility, lose data, or expose security weaknesses. Do not install a build on a machine or in a project where that risk is unacceptable.

Report a security issue

Do not publish credentials, exploit details, or private user data in a public issue. Report it privately through GitHub’s private vulnerability reporting on cloakydev/cloaky, or email hello@cloaky.dev if you cannot use GitHub. Include the affected version, your operating system, the engine, reproduction steps, and a safe contact method. Leave out real API keys, private conversations, and unredacted logs.

We acknowledge reports within 7 days and aim to release a fix or publish an advisory within 90 days. Please do not disclose the issue publicly until a fix is released.

For the contract terms and full risk allocation, read the Terms of Use.