Tools

Cline

Set up Cline with Cognitivers, then verify your connection.

Connects directly

VS Code agent extension with a generic OpenAI Compatible provider and a verify button.

Checked Official documentation (opens in a new tab)

1. Before you begin

Configuration location

Extension settings, stored in ~/.cline/data/settings/providers.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.

Cline · bash
# In the extension settings panel:
#   API Provider:  OpenAI Compatible
#   Base URL:      https://api.cognitivers.com/v1
#   API Key:       sk-cog-...
#   Model ID:      cog-pro
#
# Use the Verify button to test the connection before starting a task.

Compatibility notes

  • Cline has no embedding surface, so cog-embed has no use here.
  • Unlike Roo Code it falls back to XML tool calling, so it degrades instead of failing if native tool calls are imperfect.

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 Cline 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. Use the extension's own Verify button first and tell me what it reported.

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


Browse all integrations · API quickstart