Orvix for GitHub Copilot Chat
Use Orvix managed and BYOK models directly from the GitHub Copilot Chat model picker in Visual Studio Code.
This extension is a native VS Code LanguageModelChatProvider. It validates a project-scoped Orvix API key, discovers the models available to that project, and streams OpenAI-compatible chat completions directly from https://api.orvix.id/v1 into Copilot Chat.
Highlights
- Direct Orvix integration without a local proxy
- API keys owned by VS Code native provider configuration, keyed by a one-way fingerprint
- Multiple isolated Orvix entries (one per group name) in Manage Language Models
- Live
/models discovery for both orvix/* managed models and unprefixed BYOK models
- Durable per-key catalog snapshots for offline startup
- Streaming text, reasoning output, token usage, images, and function-tool calls
- Agent mode function-tool calls with complete argument validation
- Bounded retries for pre-stream network and gateway failures only
- Orvix Credits and usage tracking with a status-bar balance and quick-pick details
- Bind a browser billing session to one credential reference (API keys are inferencing-only)
- Rupiah account balance, active plans, and top-up history surfaced in the usage quick pick
- Best-effort per-token pricing in the model picker, sourced from live API data or upstream provider rates
- Image generation tool (
orvixImages) using prepaid Image Credits, tracked separately from USD credits
Quick start
- Install the extension. You need VS Code 1.125 or newer and GitHub Copilot Chat.
- Create a project API key with the
ai:invoke scope in the Orvix Platform.
- Open Copilot Chat, select Manage Models, add an Orvix provider entry, and enter the key.
- Choose any model returned for that Orvix project.
Managed model IDs start with orvix/ and spend Orvix Credits. Unprefixed IDs use provider credentials configured in Orvix and are billed by that upstream provider. orvix/auto lets Orvix route each request to a suitable managed model.
To use more than one project or key, add another Orvix entry with a different group name and key. Each entry's credentials and usage are scoped by a one-way fingerprint of its key; model selections are per group and stay stable across rotations. Billing sessions bind to one credential at import time.
This major release uses group-name native entries exclusively. Recreate old entries with the new single-field flow and re-import any billing session. Old entry IDs and unbound sessions are never read or migrated.
Documentation
Unofficial project; not affiliated with Orvix, GitHub, or Microsoft. Orvix and upstream-provider usage limits and charges still apply. Licensed under MIT.
