Cloud|

AI providers without a data-protection commitment

Upgrade notes for the third AI provider data boundary, restricted.

1 min read Updated 2026-11-04 #ai#providers#upgrades

AI providers can use a third data boundary, restricted, next to private and hosted. Its models serve only application server code that names a model ID; people never use them. See Choose the data boundary.

Existing providers are not migrated: they keep hosted or private, and their models, grants and assignments stay unchanged. The AI migration only widens the ai.providers.data_boundary check to accept restricted. No new service or environment variable is required.

Choose the boundary when you create the provider. A provider never changes to or from restricted afterwards; create a new provider instead. Such a provider accepts only chat models, gives them no chat access and cannot fill a class, the image tool, the audio tool or live dictation.

Clients that read providers or the AI overview must accept the new dataBoundary value.

Connect a coding agent

The Cloud skill provides compact working instructions. MCP supplies exact current documentation when details matter.

CLI command
bunx skills add https://docs.example.com

This command installs the working instructions published by this website in the selected coding agent.

For exact, current details, also connect the MCP server through one of the agent tabs.

Installation uses the open-source Vercel Skills CLI.

The skill and MCP complement each other: the skill describes workflows, while MCP supplies current documentation.