opencodex mit Homebrew Cask installieren

Projektlinks

• Homepage
• Repository
• Paketmanager-Seite

Befehle und Aliase

In der lokalen Paketdatenbank wurden keine Executable-Aliase gefunden.

Projektgeschichte

OpenCodex was created as a local universal-provider proxy for AI coding agents. Its scope expanded to translate between OpenAI Responses, OpenAI-compatible, and Anthropic-style interfaces while preserving streaming, tool calls, reasoning data, and images.

Later development added provider presets, OAuth login, model combinations, account pooling, sub-agent routing, sidecars for search and vision, a management dashboard, desktop packaging, and explicit integrations for multiple coding clients.

Adoptionsgeschichte

OpenCodex broadened from a Codex-oriented local proxy into a gateway supporting Codex CLI, Codex App and SDK workflows, Claude Code, Claude Desktop, Grok Build, and other compatible clients. It is distributed as a desktop application, standalone executable, and npm-installed command-line tool.

The project maintains provider presets, adapters, client integrations, and a dashboard so users can change model backends while retaining their preferred coding-agent interface.

Wie es verwendet wird

Users run the initialization wizard, select a provider and model, supply an API key or OAuth login, and optionally let OpenCodex inject its local endpoint into Codex configuration. The proxy can then be started as a foreground command or managed background service.

Advanced workflows route different models or tasks to different providers, define failover or weighted combinations, expose routed models to sub-agents, and inspect live requests through the dashboard. Stopping or ejecting the integration restores native Codex routing.

Warum Paket-Nerds sich dafür interessieren

OpenCodex exemplifies the rapidly growing package layer between AI coding agents and model providers. It turns protocol translation, provider authentication, model discovery, routing, failover, and account selection into a locally managed service.

Its reversible edits to Codex configuration and catalogs are especially relevant to package maintainers: starting the proxy integrates it with existing clients, while stop, restore, and eject operations remove generated routing state without deleting the user's native configuration.

Zeitleiste

• Initial project: OpenCodex provided a local provider proxy for Codex workflows.
• Subsequent development: Support expanded to Claude Code, desktop clients, provider OAuth, routing combinations, account pools, sidecars, and managed sub-agent catalogs.

Related projects

• OpenAI Codex is a primary client whose configuration and model catalog OpenCodex can manage reversibly.
• Claude Code is another officially documented client and can route its inference traffic through OpenCodex.
• Provider services and local model servers sit upstream of OpenCodex through built-in or custom adapters.

Quellen

• https://github.com/lidge-jun/opencodex#readme
• https://opencodex.me/
• https://opencodex.me/getting-started/quickstart/
• https://opencodex.me/guides/codex-integration/
• https://opencodex.me/reference/client-support/