codex-kimi-bridge v0.4.0

codex-kimi-bridge 0.4.0

Highlights

• Run Kimi as a native Codex Desktop kimi_frontend subagent while keeping Desktop-owned task IDs, status, panel visibility, and final-result delivery.
• Accept Responses agent_message input and normalize validated agent routing into Kimi Chat Completions messages.
• Omit opaque OpenAI provider-private encrypted_content without attempting to decrypt, guess, log, or forward it.
• Capture the user's visible delegated task with trusted UserPromptSubmit and PreToolUse hooks before cross-provider private wrapping.
• Bind every delegated task to the intended child with a locally signed, expiring CKB1 envelope and fail closed before contacting Kimi when verification is unavailable or invalid.
• Match Codex Desktop Multi-agent v2's flattened collaborationspawn_agent hook name together with the documented compatibility forms.
• Emit standard Responses assistant phases so terminal child text is classified as final_answer and tool progress as commentary.
• Preserve support for top-level and namespaced function and custom tools, including descendant spawn_agent calls.
• Ship the updated manage-codex-kimi-bridge skill, bilingual installation guides, safe agent template, and three macOS startup choices.

Verified compatibility

Rust and Node offline tests cover task capture, hook merge and removal, signature verification, tampering, expiry, recipient binding, empty-payload failure, opaque provider-state filtering, namespace translation, and marked recursive handoff. A user-authorized real Codex Desktop Multi-agent v2 test created one native kimi_frontend task with fork_turns = "none" and returned KIMI_BRIDGE_V2_FINAL_OK exactly through the normal final-result channel without a retry.

Security and installation

The bridge listens on 127.0.0.1 by default and does not log request bodies, API keys, authorization headers, reasoning content, or internal turn IDs. Handoff envelopes authenticate local source and integrity; they are not encryption. Visible tasks are stored temporarily with user-only permissions and must never contain credentials or secrets.

The macOS binaries are ad-hoc signed but not Apple-notarized. Verify the attached SHA-256 checksums before installation. The Rust single binary remains the default; the separately named Node package is a fallback only.

codex-kimi-bridge v0.3.0

codex-kimi-bridge 0.3.0

Highlights

• Translate Codex Responses namespace containers whose children are function or custom tools.
• Flatten namespaced tools to collision-safe Kimi Chat function names of at most 64 characters.
• Restore the original namespace + name in non-streaming responses, streaming events, and later tool-call history.
• Preserve native Codex collaboration routing so a Kimi subagent can invoke spawn_agent; descendant requests use the same stateless translation path.
• Keep recursion depth, concurrency, lifecycle, UI, permissions, and sandbox policy under Codex Desktop rather than adding bridge-specific limits.
• Remove the role-unsupported model_supports_reasoning_summaries field from the bundled kimi_frontend template.
• Disable unsupported hosted tools in the safe frontend-role template while retaining multi_agent and multi_agent_v2.
• Extend Rust, Node, and shared compatibility coverage for namespaced functions, namespaced custom tools, history replay, split streaming names, long names, and collisions.
• Version the separately named Node fallback as codex-kimi-bridge-node 0.2.0 for the matching protocol update.

Compatibility boundary

Top-level function and custom tools remain supported. A namespace may contain function and custom children. Other hosted Responses tool types are rejected explicitly and are never dropped silently.

The bridge does not impose extra recursion or concurrency limits. Actual scheduling and any global thread limits remain controlled by Codex Desktop.

No live Kimi request is required for the offline compatibility tests.

Security and installation

The macOS binaries are ad-hoc signed but not Apple-notarized. Verify SHA-256 before bypassing a Gatekeeper warning. The bridge listens on 127.0.0.1 by default and does not log request bodies, credentials, or reasoning content.

codex-kimi-bridge 0.2.0-alpha.2

codex-kimi-bridge 0.2.0-alpha.2

This prerelease makes the Rust implementation the default distribution and moves all built artifacts to a versioned, immutable GitHub Release.

Highlights

• Universal macOS installation kit for Apple Silicon and Intel Macs
• Standalone architecture-specific Rust packages
• Three startup choices: Codex-managed on demand, visible Terminal launcher, or macOS LaunchAgent
• Companion manage-codex-kimi-bridge Skill and complete bilingual setup guides
• Kimi Code membership profiles plus documented Kimi API Open Platform configuration
• Multi-agent v2 setup and a complete kimi_frontend subagent example
• Separately named Node.js fallback package: codex-kimi-bridge-node

Release integrity

The tag, source, binaries, checksums, and release assets are tied to this version. Published assets are never replaced. If anything needs correction, a new version will be released.

Verify the recommended kit with INSTALL-KIT-SHA256.txt, or verify every packaged artifact with SHA256SUMS.txt.

Alpha notice

The macOS binaries are ad-hoc signed but not Apple-notarized. Verify SHA-256 before bypassing a Gatekeeper warning. The bridge listens on 127.0.0.1 by default and does not log request bodies, credentials, or reasoning content.

No live Kimi request is made by the build or release workflow.