Adding a cloud engine

Local models handle most things. For the occasional request that needs a bigger model, you can add a cloud provider as one more engine — and anz33 keeps it firmly opt-in.

Two switches, both off

Cloud requires both:

1. A remote is configured (anz33 remote add …), and
2. allow_cloud is true.

Adding a remote does not start sending anything. Until the second switch is on, a request can be addressed to a cloud model and anz33 will still refuse to send it. This is deliberate: one accidental setting should not be enough to move your data off the machine.

Adding one

anz33 remote add anthropic
anz33 remote add openai --models gpt-4o-mini

The Anthropic preset knows its current model names. The OpenAI preset asks you to name models with --models, because their names change often enough that a built-in list would be wrong within months.

anz33 remote list
anz33 remote remove openai

Your key is never stored

anz33 records which environment variable holds your key, not the key. Config files get copied into backups, shared in screenshots and synced to other machines; keys should not travel with them.

export ANTHROPIC_API_KEY=sk-ant-...
export OPENAI_API_KEY=sk-...

To make that permanent, add the line to ~/.zshrc (macOS), ~/.bashrc (Linux), or set it in System → Environment Variables on Windows. If the variable is missing when a request arrives, that remote is treated as unavailable — not as an error to interrupt you with.

Turning cloud on

From the dashboard, flip Allow cloud. Or edit ~/.anz33/config.json:

"allow_cloud": true

Both routes are recorded in the audit log with the previous value, so there is always an answer to "when did this change, and from what?".

Cloud plus privacy rules

The two work together, and the rules win. A request matching a local-only rule cannot go to a cloud engine even with cloud allowed and even if the app asked for a cloud model by name. So a normal setup looks like:

• Cloud allowed, for the hard questions.
• A local-only rule on anything to do with money, health, clients or family names.
• The kill switch ready for when you would rather nothing left at all.

anz33 policy add clients --keyword acme "patient records" --action local_only

Watching what actually left

anz33 audit

Every request that went to a cloud engine, when, and to which provider. The dashboard shows the same thing in colour, with cloud in its own shade so the proportion is obvious at a glance.