Tools

Continue.dev

Set up Continue.dev with Cognitivers, then verify your connection.

Connects directly

Open source assistant for VS Code and JetBrains, configured with YAML.

Checked Official documentation (opens in a new tab)

1. Before you begin

Configuration location

~/.continue/config.yaml

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.

Continue.dev · yaml
name: cognitivers
version: 1.0.0
models:
  - name: Cog Pro
    provider: openai
    model: cog-pro
    apiBase: https://api.cognitivers.com/v1
    apiKey: ${{ secrets.COGNITIVERS_API_KEY }}
    roles: [chat, edit, apply, summarize]
    defaultCompletionOptions:
      contextLength: 262144
    capabilities: [tool_use]
  - name: Cog Fast
    provider: openai
    model: cog-fast
    apiBase: https://api.cognitivers.com/v1
    apiKey: ${{ secrets.COGNITIVERS_API_KEY }}
    roles: [chat, autocomplete, edit]
    capabilities: [tool_use]

Compatibility notes

  • capabilities must list tool_use explicitly. Capability detection fails on unfamiliar model names, and without tool_use there is no agent mode.
  • Do not enable useLegacyCompletionsEndpoint: this API serves chat completions, not the legacy completions endpoint.
  • Roles decide which jobs a model serves: chat, autocomplete, embed, rerank, edit, apply, summarize.

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
Verification prompt · English
You are working in a repository where I have configured Continue.dev 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. Confirm that agent mode works, which requires the tool_use capability to be declared explicitly. If tools are not offered to the model, describe what the client sent.

If the check fails, use the reported status code in the error reference and review the compatibility notes above.


Browse all integrations · API quickstart