CloudVerse Agentry

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.

Get started

On first activation, Agentry opens a dismissible Get Started guide. Reopen it anytime with Agentry: Get Started or the sidebar button. Sign in, approve in your browser, select CloudVerse Agentry / Agentry Governed Auto in VS Code Chat, and run Test route. The test sends a small billed request. A folder is optional.

The sidebar shows your personal recorded spend and provider-reported tokens across Agentry-routed tools, grouped by served provider/model. Choose Today, This month, or Last 30 days (UTC). Recorded spend uses runtime settlement pricing; provider-billed spend remains unavailable until reconciled. Missing measurements and pending settlements are not zero. Shared or unattributed traffic is outside provable personal coverage.

Budget details apply to the active authorized workload, including finalized spend, reserved exposure, remaining allowance, enforcement mode, and reset date. They are not a single allowance for every tool. A routing error keeps its diagnostic and offers Retry route; setup success alone does not prove the model route works.

Commands

• Agentry: Connect Workspace
• Agentry: Enable Governed VS Code Models
• Agentry: Configure Supported AI Tools
• Agentry: Configure Claude Code Routing
• Agentry: Configure Codex Routing
• Agentry: Configure Runtime Routing
• Agentry: Open Agentry-routed Terminal
• Agentry: Show Connection Status
• Agentry: Open Last Route Proof (the current command label)
• Agentry: Open Last Spend Proof (the current command label)
• Agentry: Test Gateway Chat
• Agentry: Test Gateway Embeddings
• Agentry: Test Gateway Streaming
• Agentry: Copy Gateway SDK Env

Install

Marketplace:

• cloudverse-aix.aix-coding

Auth

Uses Agentry device login. Tokens and workload runtime keys are stored in VS Code secret storage.

1. Run Agentry: Connect Workspace or select the CloudVerse Agentry model in VS Code Chat.
2. Approve the Agentry login in your browser if prompted.
3. Use CloudVerse Agentry / Agentry Governed Auto from the VS Code Chat model picker.
4. Open a folder only when you want repo/workspace attribution.
5. For supported local tools, run Agentry: Configure Runtime Routing, launch from Agentry: Open Agentry-routed Terminal, or configure them with Agentry: 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/v1
• OPENAI_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.

VS Code Chat prerequisite

Agentry sign-in and VS Code Chat sign-in are separate. Open Chat and, if prompted, sign in to GitHub to enable Chat/Copilot and review its terms. Then select CloudVerse Agentry / Agentry Governed Auto. A successful Agentry route test verifies the gateway, not this Chat prerequisite.

If a request reaches its per-call cost limit, start a new chat with less context or select fewer tools. Reconnecting does not change a budget.