CloudVerse AgentryConfigure 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 Commands
InstallMarketplace: AuthUses Agentry device login. Tokens and workload runtime keys are stored in VS Code secret storage.
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 BehaviorThe connector writes a non-secret workspace manifest at Supported OpenAI-compatible clients route through Agentry when they use:
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 recordAgentry 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. |