How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

vscode-extension - Skill - OpenSmartRoute

Name: vscode-extension
Author: cbs-consulting

Imported from cbs-consulting/virtual-key-mapper (vscode-extension/AGENTS.md). Install upstream with npx skills add cbs-consulting/virtual-key-mapper --skill vscode-extension. Copyright stays with the author.

Agent instructions: VS Code extensions

The repository-wide rules in the root AGENTS.md apply here too. This file adds what is specific to the two extensions.

The two extensions

Folder	ID	Runs	Does
`vscode-extension/`	`cbs-consulting.vkm`	where the workspace is (local or remote)	Gateway models in Copilot Chat, the labels status bar, and in remote windows the relay socket (`src/agent.ts`) that the CLI's `forwarded` sign-in asks for credentials
`vscode-extension/local/`	`cbs-consulting.vkm-host`	always on the local machine (`extensionKind: ui`)	Answers relay requests with the local CLI and its OS vault (`src/handler.ts`)

The extensions know no gateway. Credentials, endpoints and label headers come only from the CLI's JSON outputs (token --json, profile show --json, repo show --json), typed in src/cli.ts. Do not hard-code header names, URL paths or label formats here. If the extension needs something new, add it to the CLI's JSON first.

The relay protocol (one JSON line per connection, described at the top of src/agent.ts) is shared with src/virtual_key_mapper/auth/forwarded.py. Change both sides together, and keep the host extension returning only short-lived access tokens and nonsecret profile details: no refresh token ever reaches a remote window.

Code layout and style

Modules that need no vscode import (gateway.ts, protocol.ts, credentials.ts, labels.ts, local/src/handler.ts) stay free of it, so they are tested in plain Node. Put new logic there and keep extension.ts and provider.ts thin.
TypeScript is strict with noUnusedLocals. Each file starts with a comment saying what it does.
No runtime dependencies: the packages are built with --no-dependencies. Dev dependencies are pinned exactly.

Commands

cd vscode-extension
npm ci --ignore-scripts
npm test                     # unit tests (node --test), includes the relay against the real CLI when Python can import it
npm run test:host            # a real VS Code extension host with a fake CLI and gateway (downloads VS Code; Linux: xvfb-run -a)
cd local && npm test         # the host extension, using the main folder's TypeScript

test/interop.test.ts runs the relay against the Python CLI (VKM_TEST_PYTHON, default python3). It skips on Windows and when the CLI cannot be imported, so install the package first (pip install -e ..) or the relay goes untested.

The version in both package.json files and package-lock.json must match pyproject.toml. Do not change it outside a release.

Install vscode-extension and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "cbs-consulting-virtual-key-mapper-vscode-extension", "kind": "skill", "name": "vscode-extension", "description": "The repository-wide rules in the [root AGENTS.md](../AGENTS.md) apply here too. This file adds what is specific to the two extensions.", "publisher": "cbs-consulting", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "The repository-wide rules in the [root AGENTS.md](../AGENTS.md) apply here too. This file adds what is specific to the two extensions." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/cbs-consulting/virtual-key-mapper", "path": "vscode-extension/AGENTS.md", "ref": "98eccbd1bc8f9783739f0e1587b6facc49a93f96", "url": "https://github.com/cbs-consulting/virtual-key-mapper/blob/98eccbd1bc8f9783739f0e1587b6facc49a93f96/vscode-extension/AGENTS.md", "key": "cbs-consulting/virtual-key-mapper/vscode-extension/AGENTS.md" } }, "instructions": "# Agent instructions: VS Code extensions\n\nThe repository-wide rules in the [root AGENTS.md](../AGENTS.md) apply here too. This file adds\nwhat is specific to the two extensions.\n\n## The two extensions\n\n| Folder | ID | Runs | Does |\n| --- | --- | --- | --- |\n| `vscode-extension/` | `cbs-consulting.vkm` | where the workspace is (local or remote) | Gateway models in Copilot Chat, the labels status bar, and in remote windows the relay socket (`src/agent.ts`) that the CLI's `forwarded` sign-in asks for credentials |\n| `vscode-extension/local/` | `cbs-consulting.vkm-host` | always on the local machin", "cost": { "context_tokens": 656 } }

vscode-extension

About

Agent instructions: VS Code extensions

The two extensions

Code layout and style

Commands

Install vscode-extension and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews