Tools
Oh my Pi
Set up Oh my Pi with Cognitivers, then verify your connection.
Connects directly
A fork of Pi with the editor wired in. Same schema, YAML, and model roles per task.
1. Before you begin
- Oh my Pi installed and ready to configure.
- A Cognitivers API key. See authentication and key management.
Configuration location
~/.omp/agent/models.yml and ~/.omp/agent/config.yml
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.
# ~/.omp/agent/models.yml
providers:
cognitivers:
baseUrl: https://api.cognitivers.com/v1
api: openai-completions
apiKey: $COGNITIVERS_API_KEY
models:
- id: cog-fast
name: Cog Fast
contextWindow: 262144
maxTokens: 32768
- id: cog-pro
name: Cog Pro
contextWindow: 262144
maxTokens: 32768
# ~/.omp/agent/config.yml
modelRoles:
default: cognitivers/cog-pro
smol: cognitivers/cog-fastCompatibility notes
- Same provider schema as Pi, in YAML: baseUrl, api, apiKey, models.
- run omp models cognitivers to check that the route loads before starting a session.
- Roles let one route serve several jobs: default for normal turns, smol for cheap fan-out.
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 Oh my Pi 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.