Until today, aidd only used OpenAI through the Codex CLI. Codex handled communication with OpenAI while aidd managed the process. Today, I added another option: aidd can now call the OpenAI API directly. It can run its own agent loop without needing the CLI. It uses API tokens, so it can be more expensive, but it is useful when the Codex CLI is unavailable or cannot be installed, or when I need API-backed configuration and billing instead of CLI-managed access.
From the outside, it still looks like any other backend. OpenAI shows up in settings and launch controls. The runs go through the same history, result handling, and live console as other providers. Connecting all of those took most of the work.
The first version uses non-streaming Chat Completions and passes through reasoning for compatible models. I ran it through the usual launch and run history instead of stopping with request mocks. The automated tests cover successful responses, malformed replies, and rate limits.
There may be OpenAI-specific behavior that doesn’t fit the common native loop. I’m not sure what those behaviors are yet.