Ilker ManapandClaude Opus 5.5
b986ea180d
- server init run again on a machine already set up is not refused its memory (the docs fix a certificate with --host so), and judges count only when one will be installed (judgeComes: not without a mirror, nor from a bundle without it). - A server's sealed secrets that it no longer reads are removed when it is put or deleted; replacing a credential replaces every header it was sent, rather than adding one beside the old. - llmgw.gatewayUrl is a machine setting and restricted in untrusted workspaces: a cloned repository's settings cannot send a sign-in to another gateway. - The bandwidth buffer is at least eight times the CPU's last cache and at most a quarter of free memory, else nothing is measured until there is room; a registration carries the figure measured so far. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
llmgw for VS Code
The models your llmgw gateway serves, in VS Code: in the chat's model picker, in agent mode, and in any extension that asks VS Code for a language model. Nothing goes anywhere but the gateway you connect it to.
Connecting
- llmgw: Sign In from the command palette. It opens your gateway's account page; sign in there and choose Make a key and the configuration with VS Code as the tool. The page hands the key back to VS Code.
- Or llmgw: Enter API Key and paste a key from that page.
The gateway's address is the llmgw.gatewayUrl setting. An extension
downloaded from a gateway has that gateway's address in it already.
The key is kept in VS Code's secret storage. llmgw: Sign Out forgets it; revoke it on the account page to stop it working.
Which models
Every chat model the key may use. Agent mode acts only through tool calls,
so it needs a model the gateway's catalog says makes them; set
llmgw.showModelsWithoutTools to false to see only those.
Completion as you type is not part of what VS Code lets a model provider offer; for that, use an extension such as Continue against the same gateway.