Verified Bilingual Learning Guide

One interface. Different AI models.

OpenCodex is a local proxy layer that lets Codex, Claude Code, and related clients reach multiple providers through one port. This guide uses upstream documentation for specifications and real dashboard screenshots for interface evidence, moving from setup to auditable verification.

PowerShell · Windows 11
PS> npm install -g @bitkyc08/opencodex
PS> ocx init
PS> ocx start
PS> ocx gui

proxy     online
endpoint  http://localhost:10100
workflow  inspect → route → verify
40+built-in providers
10100current default port
Node 18+Windows requirement
0client patches required

01 · Concept

What problem does OpenCodex solve?

AI development clients are often tied to one model family or API format. OpenCodex accepts Codex Responses API or Claude Messages API traffic and translates streaming, tool calls, reasoning markers, and images for the selected provider. It controls where a request goes; it does not replace task design or human validation.

CLIENT

User interface

Codex CLI, Codex App, SDK, Claude Code, and other existing work surfaces.

LOCAL PROXY

OpenCodex

Protocol translation, model catalog, provider routing, account pool, logs, and usage.

PROVIDERS

Model layer

Anthropic, Google, xAI, Kimi, Ollama, OpenRouter, Azure, and compatible custom endpoints.

Model routing

Use provider/model for explicit routing. A bare model name uses the default provider or name-based matching.

Session affinity

Existing sessions remain on their account; new sessions can select an eligible healthy account based on quota state.

Observability

Use Logs, Usage, and actual output tests. An “Online” badge alone is not evidence of task completion.

02 · Quickstart

How do you complete the first Windows setup?

The current upstream version is installed from npm and requires Node.js 18 or later on Windows x64. The package bundles the Bun runtime. If npm blocks lifecycle scripts, follow the current README instead of reusing legacy Go, Docker, or port 8080 instructions.

Install the package

Use a user-owned Node/npm environment with a writable global prefix.

npm install -g @bitkyc08/opencodex

Initialize and start

ocx init injects the Codex provider and offers autostart options. ocx stop restores native Codex configuration.

ocx init
ocx start
ocx gui

Inspect the model catalog

A catalog response only proves that the proxy answered. Run one small task and verify Logs as well.

Invoke-RestMethod http://localhost:10100/v1/models

Add the first provider

Choose a built-in provider or a custom OpenAI-compatible endpoint. Enable private-network access only for a known local or LAN service.

03 · Interface Evidence

What should you inspect in the Web Dashboard?

These local screenshots were captured on July 28, 2026 and checked for exposed API keys, tokens, or cookies. The interface may change with upstream releases. Click an image to enlarge it.

04 · Routing

How should you select a provider and model?

The goal is not to connect the largest possible catalog. Match task requirements, data risk, model capability, and validation cost. Use explicit provider/model selectors for important work, then confirm the route in Logs.

codex -m "anthropic/claude-opus-5" "Explain this stack trace"
codex -m "google/gemini-3-pro" "Write unit tests for auth.ts"
codex -m "ollama/llama3" "Refactor this function"
CLOUD

Cloud providers

Useful for demanding tasks, but review cost, data policies, region availability, and terms of service.

LOCAL

Ollama / LM Studio

Inference can stay local, but tool support, context length, hardware use, and output quality still require testing.

CUSTOM

Compatible endpoints

Appropriate for self-hosted or organizational services. Never hard-code credentials in course materials or repositories.

05 · Learning Workflow

How does setup become a learning process?

The course does not end when the proxy starts. Learners observe, form a routing hypothesis, execute, inspect evidence, and reflect. This builds transferable troubleshooting skills when the interface or upstream version changes.

PRACTICE A

Same task, different models

Define acceptance criteria for a low-risk refactoring task. Compare a cloud model and a local model on correctness, tool calls, latency, and token use rather than writing style alone.

PRACTICE B

Create a diagnosable failure

Use a nonexistent model name or disable a provider. Observe /v1/models, Logs, and the error code, then turn the diagnosis into a reusable checklist.

Minimum acceptance checklist

  • Instructions match current upstream docs
  • Logs show the expected provider and model
  • No credentials are exposed in the UI or output
  • Output passes the test defined before execution
  • Cost, latency, and failures are recorded
  • Native settings can be restored with ocx stop
Data safety: A proxy does not automatically make a third-party provider private. For personal data, confidential records, or unpublished research, select local processing, redact data, or stop transmission according to governance requirements.

06 · Sources

What evidence supports this guide?

The supplied NotebookLM notebook combines six sources. This site adds local interface screenshots captured on July 28, 2026. Technical specifications come primarily from the official documentation and GitHub repository; media and videos provide supplementary learning context.

  1. Official OpenCodex documentation
    https://opencodex.me/
  2. Upstream GitHub repository
    lidge-jun/opencodex
  3. NotebookLM: OpenCodex: Universal Proxy for AI Coding Tools
    Supplied NotebookLM notebook
  4. 53AI feature article
    Codex can finally switch models freely
  5. X community introduction
    Original post
  6. Chinese YouTube tutorial
    OpenCodex step-by-step tutorial for arbitrary APIs and local models
  7. Japanese YouTube tutorial
    Universal LLM proxy guide for Codex CLI and Claude Code users

07 · FAQ

Common questions

When instructions disagree, verify the upstream version first, then compare the dashboard, model catalog, and request logs.

Is OpenCodex an official OpenAI product?

No. It is an independent community project and is not endorsed by OpenAI, Anthropic, or other providers. Review each provider's terms before connecting an account.

Why does this guide use port 10100 instead of 8080?

The current official site and GitHub README use localhost:10100. OpenCodex changes quickly, so confirm current upstream documentation instead of copying older tutorials.

Does “Online” mean that a task succeeded?

No. It only shows that the proxy is reachable. Verify the actual provider, model, status code, output artifacts, and task-specific tests.

Does a local model guarantee that no data leaves the computer?

No. Confirm that the actual route is local and that the workflow does not call cloud search, a sidecar, or another external tool. Use Logs and network configuration as evidence.