Tools
GitHub Copilot in VS Code
Set up GitHub Copilot in VS Code with Cognitivers, then verify your connection.
Connects directly
Custom Endpoint provider. Point it at the base URL and VS Code discovers the models itself.
1. Before you begin
- GitHub Copilot in VS Code installed and ready to configure.
- A Cognitivers API key. See authentication and key management.
Configuration location
chatLanguageModels.json
Need an API key? Request access before running these examples.
2. Configure the connection
Apply the following configuration in the location above. Replace credential placeholders with your own key; keep secrets out of version control.
[
{
"name": "Cognitivers",
"vendor": "customendpoint",
"url": "https://api.cognitivers.com/v1",
"apiKey": "${input:chat.lm.secret.cognitivers}"
}
]Compatibility notes
- Declaring url at provider level makes VS Code ask the endpoint for its model list instead of requiring a models array, which is the least friction of any editor here.
- Requests carry Authorization: Bearer by default.
- It covers chat, agent mode and utility tasks. It does not cover semantic search, inline suggestions or embeddings.
- On Copilot Business and Enterprise an administrator has to enable the bring-your-own-key policy first.
3. Verify the setup
Use this prompt in your configured tool to check authentication, a response and streaming. It reports failures without printing your key.
Open verification prompt
You are working in a repository where I have configured GitHub Copilot in VS Code to use Cognitivers as its model provider.
The API is OpenAI-compatible chat completions.
- Base URL: https://api.cognitivers.com/v1
- Streaming: use the same base URL with stream: true
- Models: cog-fast (agents, pipelines, volume), cog-pro (one hard task), cog-embed (retrieval)
- Authentication: an API key in the Authorization header as "Bearer sk-cog-..."
Do these four things and then stop.
1. Check that the credential is present in my environment and tell me the name of the variable you found it in. Do not print the key itself, not even partially.
2. Send one non-streaming chat completion asking for a single short sentence, using cog-fast. Show me the exact command or code you used and the model's reply.
3. Send the same request with streaming enabled and confirm you received server-sent events, not one buffered body.
4. If any step fails, tell me the exact error, the status code and the request that produced it, then stop. Do not try more than two fixes, and do not change any configuration file without showing me the diff first.
Rules: never write the key into a file that is tracked by git, never print it in full, and if the request works, say so in one line instead of writing a report.
5. This client can discover models from the API. Confirm whether it listed cog-fast and cog-pro by itself, or whether you had to declare them.If the check fails, use the reported status code in the error reference and review the compatibility notes above.