Configure supported coding-agent and VS Code model traffic to use CloudVerse Agentry with per-developer credentials, spending limits, revocation, and run history.
The extension is not a prompt workbench. It registers Agentry as a VS Code Chat model provider, requests a scoped workload key, configures supported coding-agent gateway settings with consent, and links to route, policy, spend, and attribution records. Opening a folder adds repository attribution; it is not required for sign-in or VS Code Chat routing. Developers who do not install the extension can use npx @cloudverse/agentry-connect instead.
Commands
Agentry: Connect WorkspaceAgentry: Enable Governed VS Code ModelsAgentry: Configure Supported AI ToolsAgentry: Configure Claude Code RoutingAgentry: Configure Codex RoutingAgentry: Configure Runtime RoutingAgentry: Open Agentry-routed TerminalAgentry: Show Connection StatusAgentry: Open Last Route Proof(the current command label)Agentry: Open Last Spend Proof(the current command label)Agentry: Test Gateway ChatAgentry: Test Gateway EmbeddingsAgentry: Test Gateway StreamingAgentry: Copy Gateway SDK Env
Install
Marketplace:
Auth
Uses Agentry device login. Tokens and workload runtime keys are stored in VS Code secret storage.
- Run
Agentry: Connect Workspaceor select the CloudVerse Agentry model in VS Code Chat. - Approve the Agentry login in your browser if prompted.
- Use
CloudVerse Agentry / Agentry Governed Autofrom the VS Code Chat model picker. - Open a folder only when you want repo/workspace attribution.
- For supported local tools, run
Agentry: Configure Runtime Routing, launch fromAgentry: Open Agentry-routed Terminal, or configure them withAgentry: Copy Gateway SDK Env.
Connect workspace is available after sign-in for source attribution, including repository folders opened in VS Code. Import source archive is handled by the hosted Coding Workbench when a readable local folder cannot be attached directly.
Runtime Behavior
The connector writes a non-secret workspace manifest at .vscode/aix-runtime.json and an example env file at .env.aix.example.
Supported OpenAI-compatible clients route through Agentry when they use:
OPENAI_BASE_URL=https://agentry.cloudverse.ai/v1OPENAI_API_KEY=<scoped Agentry workload key>OPENAI_MODEL=agentry/auto
The scoped key is never written to the manifest or example file. It is available to the routed terminal environment and can be copied explicitly by command.
What Agentry can record
Agentry records policy, routing, spend, and attribution only for calls that reach its gateway. VS Code Chat uses Agentry controls only when the selected model is CloudVerse Agentry. GitHub Copilot Chat can use Agentry only where its BYOK or custom-provider settings allow Agentry as the selected model. Agentry cannot silently intercept Copilot traffic. Tools that ignore custom base URLs or bypass the routed terminal also bypass Agentry.