v0.4.0-beta.3 — DeepSeek V4 Flash Public Beta

DeepSeek V4 Flash Public Beta

This prerelease publishes the packaged clean-install External path for DeepSeek V4 Flash on macOS with exact Codex CLI 0.149.0.

What changed

• Adds the accepted Flash clean-install release candidate and production catalog contract.
• Aligns package, installer manifest, IPC client, and security-support metadata on 0.4.0-beta.3.
• Documents one bounded maintainer packaged-artifact E2E with strict installation-scoped runtime evidence.
• Preserves command-backed macOS Keychain authentication and isolated CODEX_HOME behavior.

Safety boundaries

• External execution remains explicit and default-off.
• Provider requests are separately billable and require explicit authorization.
• DeepSeek V4 Pro remains explicit-only; MiniMax and Qwen support boundaries are unchanged.
• Maintainer E2E evidence is not independent-user acceptance, broad compatibility, or official endorsement by OpenAI or any provider.

Validation

• Local tests: 219/219 passed.
• GitHub Actions passed on the merged main commit.
• Codex Security diff scan completed with 0 findings.
• Attached artifact contains 66 files and passed fresh install, dry-run, apply, idempotent reapply, executable syntax, sensitive-pattern, and fixture-exclusion checks.
• No Provider request was made during this release task.

Artifact SHA-256: a8bdc59d56cd9bba626f688a23cf0e2e8f2f1679bfa72fc837c6023c329c81dd

v0.4.0-beta.2

Easier onboarding

• Refined the English and Simplified Chinese first-run path, Quick Start, provider evidence, and project boundaries.
• Makes it clearer that Codex remains the main agent while reviewed provider workers handle only bounded text, code, research synthesis, and local validation tasks.

Read-only pre-install Doctor

• Adds npm run doctor -- --provider <deepseek|minimax|qwen> with PASS, WARN, and BLOCKED results for the local environment, selected provider/model, installation state, permissions, fallback availability, and verify prerequisites.
• Doctor is read-only: it does not modify Codex configuration, install files, call provider APIs, or print credential values.

Structured issue intake

• Adds GitHub Issue Forms for reproducible bug reports, provider compatibility evaluation, and scoped feature requests.
• Keeps provider requests separate from supported or runtime-verified status and directs sensitive security reports to the private process in SECURITY.md.

Security and privacy safeguards

• Issue Forms explicitly prohibit API keys, credentials, private task text, private filesystem paths, and sensitive data.
• Existing Keychain-only credentials, owner-only bridge permissions, atomic redacted archives, and dry-run-by-default write controls remain unchanged.
• No API keys or private configuration are included in this release.

Engineering baseline

• 50/50 automated tests pass locally and in GitHub Actions on macOS with Node.js 20.
• Coverage now includes Doctor read-only behavior, private-path redaction, Issue Form requirements, and repository metadata alignment.

Runtime verification boundaries

• No provider runtime claims were expanded.
• runtimeVerified remains false where live verification has not been performed.
• DeepSeek public-installer runtime verification and real-user acceptance remain pending.

v0.4.0-beta.1 — Codex Third-Party Workers public beta

Codex Third-Party Workers public beta

This beta introduces a reviewed provider-pack layer that lets Codex delegate
bounded tasks to selected third-party model APIs while keeping the main Codex
thread on its OpenAI model, provider, and authentication flow.

Supported delegation is intentionally limited to suitable text, code, research
synthesis, and local-validation tasks. Codex remains responsible for reviewing
and synthesizing the worker result.

Included provider packs

This release includes three built-in provider packs:

• DeepSeek V4 Flash
• MiniMax-M3
• Alibaba Model Studio Qwen3.7-Max

A built-in pack is not automatically a runtime-verified pack.

Runtime-verified providers

MiniMax-M3

Verified with:

• Responses API
• SSE streaming
• two-turn Function Calling
• Codex CLI
• Codex Desktop minimax_worker
• successful task-bridge completion and release

Qwen3.7-Max

Verified with:

• Responses API
• SSE streaming
• automatic Function Calling
• Codex CLI
• Codex Desktop qwen_worker
• successful task-bridge completion and release

Qwen remains text-only in this project. Thinking mode does not accept
tool_choice: required; automatic tool choice was verified.

Public-installer --apply and verify acceptance remain separate pending checks
for a real user environment.

Built-in, runtime validation still pending

DeepSeek V4 Flash

DeepSeek V4 Flash is built in and covered by isolated installer, routing,
catalog, and bridge tests. Public-installer runtime verification is still
pending. DeepSeek V4 Pro is explicitly excluded.

Candidate providers — real API validation required

These providers have relevant official Responses documentation but are not
included or runtime verified:

• StepFun Responses models
• Volcano Ark Responses models

They must pass streaming, Function Calling, Codex subagent execution, failure
fallback, bridge release, and main-thread review before becoming built-in packs.

Partial / gateway candidates

• Baidu Qianfan Responses gateway
• Tencent Cloud TokenHub

Gateway compatibility does not prove that the underlying model vendor's direct
API is compatible.

Currently incompatible direct paths

The following direct provider paths do not currently satisfy this project's
Responses contract:

• Kimi K3 direct API
• Zhipu GLM direct API
• legacy Tencent Hunyuan endpoints
• SiliconFlow direct API

External protocol translators may provide other integration paths, but they are
outside this project's native provider-pack scope.

Verification

• 37/37 isolated local tests passed
• GitHub Actions passed
• Responses, SSE, and Function Calling evidence for MiniMax and Qwen
• Codex CLI and Desktop subagent smoke tests
• owner-only single-slot bridge and redacted archive checks
• secret-safety, personal-path, fixed-UID, and credential-value checks

Security boundaries

• API keys remain in macOS Keychain
• the installer never accepts --api-key
• secrets are never committed to the repository
• dry-run is the default; changes require explicit --apply
• the main ~/.codex/config.toml is not modified
• active bridge files use owner-only permissions
• completed and failed task archives redact task messages and working paths
• browser, desktop, image, audio, video, MCP, and Computer Use delegation are
  outside the supported scope

Users remain responsible for reviewing each provider's privacy, pricing,
data-retention, billing, and regional policies.

Documentation

• English README
• 简体中文 README
• Provider compatibility matrix
• 中文 Provider 兼容性矩阵
• Security policy

This is an unofficial, macOS-only public beta. It is not endorsed by OpenAI,
DeepSeek, MiniMax, or Alibaba Cloud. It does not claim compatibility with every
provider and does not promise a fixed cost-saving percentage.