Routes in Base and Pro

Cloaky Base runs every session on one route, Venice's private tier. Cloaky Pro adds local models, direct providers, custom profiles, and hybrid sessions.

Cloaky Base: one route

Cloaky Base keeps threads, permissions, subagents, diffs, review, and cost records in one workbench, and there is one place the inference goes. Every session runs on Venice’s private tier. There is no provider ladder to walk and no second account to connect: prompt and response content is not retained after the request under Venice’s private-tier contract, and that contract is the whole privacy story for Base.

It does not remove operational metadata. Venice can still hold account, billing, model, timestamp, token, and IP information.

Set Venice up in Settings → Providers & privacy → Venice. The model picker shows the provider, tier, context window, capabilities, and available cost information for every row, so you choose with the route in view.

Reading the badge

Each session carries a badge naming the route that actually ran. Three words do the work:

• Private — Venice’s private tier, the route every Base session takes. Read it as a provider contract, not as an encryption or anonymity claim.
• Anonymized — a separate Venice tier that protects identity, not prompt secrecy. It carries no retention contract, so do not read one into it.
• E2EE + TEE — available on some Venice models for tool-free turns. A turn that calls structured tools runs on Venice private instead, because the encrypted route does not return tool calls. The badge reports which of the two actually ran.

Cloaky Pro routes

Everything below is Cloaky Pro. Base does not ship these routes; Pro is the full workbench, and each route names the provider and privacy tier the same way Base names Venice.

Local models (Cloaky Pro)

Enable Ollama or LM Studio, then open the local models gallery to find models that support tool use and fit the machine’s available memory.

Local is the strongest privacy boundary because inference terminates on a service you run. Capability and hardware still matter, so choose a model that fits both the task and the machine.

Direct providers (Cloaky Pro)

Connect a Claude subscription, a GLM or Kimi coding plan, or an OpenAI-compatible provider when that route is the right fit. The provider receives the session under its own account and data policy. Cloaky identifies the route without extending Venice’s guarantees to it.

Provider choice is fixed when a session starts. If the provider cannot start, Cloaky stops and explains the next action instead of falling through to a different service.

Custom profiles (Cloaky Pro)

Custom profiles are for providers Cloaky does not configure for you, or for a subscription that needs its own endpoint and model mapping. A profile keeps those choices together so you can switch routes without rebuilding your setup for every session.

Open Settings → Providers & privacy → Custom profiles, then add:

1. A clear profile name. Use the provider and plan, such as “GLM Coding Plan” or “Kimi direct,” so the route is unmistakable in the session picker.
2. The provider’s compatible protocol and base URL. Copy the endpoint from the provider’s current documentation. Coding-plan endpoints can differ from metered API endpoints, even when both accept the same key.
3. The exact model identifier. Model names are provider-defined and case-sensitive. Confirm the current identifier before a long session.
4. A dedicated credential. Keep keys in Cloaky’s credential flow. Never put a key in a profile name, prompt, project file, issue, or support message.

Use Test connection before saving. Cloaky validates the route you entered; it does not silently replace a failed custom provider with Venice or another service.

Existing GLM and Kimi plans (Cloaky Pro)

GLM Coding Plan and Kimi platform accounts are good custom-profile candidates when you already pay for them or need a specific model. They are direct routes: z.ai or Moonshot receives the session under its own account and data policy. Venice’s private-tier terms do not carry across.

Use the endpoint assigned to your plan, not a similar-looking general API URL, and follow the provider’s current setup guide rather than copying an old value from a post or screenshot. Once saved, start a short test session and confirm the provider badge, model, and privacy tier before sharing project context.

Hybrid: hosted planning, local execution (Cloaky Pro)

Hybrid mode lets a hosted model plan, orchestrate, and review while a local model handles delegated work on this machine. The hosted portion follows its provider’s policy; the local portion remains local. Cloaky identifies hybrid sessions and reports when the local route is unavailable.

Before sensitive work

• Confirm the provider and tier in the model picker.
• Read Private as a provider contract, not an encryption or anonymity claim.
• Read Anonymized as identity protection, not prompt secrecy.
• Remember that approved web, search, MCP, and shell tools can access the network independently of model inference.
• Keep provider credentials out of prompts, issues, and support conversations.

Asking for Pro

Cloaky Pro is in a private three-month build with no public download. Email hello@cloaky.dev with what you would do with it. The user study group gets Pro.