Spectra is centered on Claude Code as the primary desktop workflow. It also supports OpenAI provider access for Codex-related model scenarios. The important point is to describe that support truthfully: unified provider access is real, but the deepest desktop install and operations path still centers on Claude Code.
Last updated: 2026-03-30
Teams evaluating provider access need clear product language rather than vague compatibility claims.
A clearer model reduces confusion when teams work across more than one provider.
Keep installation, diagnosis, state visibility, and account context in the same product path.
Provider routing can support multiple model families without implying identical operational depth.
Describe Codex-related access accurately while keeping Claude Code as the deepest current runtime path.
Clarity is especially important when multiple model families are being evaluated in the same workflow.
You want one workspace while still understanding exactly what each provider path means.
You need language that is operationally accurate, not just marketable.
You need to explain the support boundary before standardizing across a team.
You want Codex-related traffic to land on a page that describes the product honestly.
Yes. Spectra supports OpenAI provider access that can cover Codex-related model scenarios inside the same workspace.
Because the deepest desktop installation, diagnosis, versioning, and runtime flow is still primarily centered on Claude Code today.
Because teams need truthful product boundaries to make rollout decisions with confidence.
These pages continue the provider story into team operations, support surfaces, and long-term usage control.