Tools
OpenAI Codex CLI
Set up OpenAI Codex CLI with Cognitivers, then verify your connection.
Connects directly
OpenAI's terminal agent and IDE extension. Custom providers are a first-class setting.
1. Before you begin
- OpenAI Codex CLI installed and ready to configure.
- A Cognitivers API key. See authentication and key management.
Configuration location
~/.codex/config.toml
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.
model = "cog-fast"
model_provider = "cognitivers"
[model_providers.cognitivers]
name = "Cognitivers"
base_url = "https://api.cognitivers.com/v1"
env_key = "COGNITIVERS_API_KEY"Compatibility notes
- The reserved provider ids openai, ollama and lmstudio cannot be reused; pick your own id.
- env_key names the environment variable that holds the key. The key itself never goes in the file.
- To redirect only the built-in OpenAI provider at a proxy, openai_base_url is the shorter form. Defining a provider as above is the explicit one.
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 the OpenAI Codex CLI 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.If the check fails, use the reported status code in the error reference and review the compatibility notes above.