Skip to main content
This guide is for Oh My Pi (omp), not OpenAI Codex CLI. OMP reads custom provider definitions from ~/.omp/agent/models.yml.

Prerequisites

Setup

1

Create the OMP provider configuration

Create OMP’s configuration directory, then open the model configuration file:
Add the following configuration:
Save the file in nano with Ctrl+O, press Enter, then exit with Ctrl+X.The important fields are:Model IDs are examples only. Use the exact model IDs currently shown on the A2Agent Models page. The model IDs above are examples and may change.
2

Verify that OMP loaded the provider

Run:
The verified omp models find a2agent result is:These values describe the A2Agent models currently returned by OMP’s model lookup. Keep the models.yml metadata aligned with the current result, and re-run the command after A2Agent or OMP updates.
3

Start OMP with an A2Agent model

Move into the project you want OMP to work on:
Start OMP with a specific A2Agent model:
You can also start OMP normally and use the in-session model picker:
Then select one of the a2agent/... entries.For a minimal connection test, ask OMP:
If OMP replies and identifies the selected a2agent/... model, the connection is working.

Troubleshooting

Verify all of the following:
  • The value is an A2Agent API key, not an OpenAI key.
  • apiKey: A2AGENT_API_KEY matches the environment-variable name exactly.
  • authHeader: true is present under the a2agent provider.
  • The key is active in the A2Agent dashboard.
Check the configuration path and YAML syntax:
Also verify that a2agent is not disabled in OMP’s effective settings:
Remove a2agent from disabledProviders if it appears there. A disabled provider remains unavailable even when its key and configuration are correct.
Model IDs are case-sensitive. Copy the model ID exactly from the A2Agent Models page, update ~/.omp/agent/models.yml, then run:
Do not use a display name in id. For example, use kimi-k2.7-code, not Kimi K2.7 Code.