codex-kimi-bridge v0.4.1

codex-kimi-bridge 0.4.1

Highlights

• Protect long-running native Kimi subagents from opaque cross-provider follow-ups.
• Register each successfully signed Kimi target locally for six hours, bound to the parent Codex session and child task name.
• Deny send_message and followup_task before delivery only when they target a Kimi child registered by that same parent session; ordinary non-Kimi agent communication remains unchanged.
• Report a later opaque MESSAGE as unsupported_cross_provider_followup instead of the misleading initial-handoff error missing_handoff_envelope.
• Keep the safe operating path explicit: send the full task in the initial visible [KIMI_TASK], create a uniquely named kimi_frontend child with fork_turns = "none", then use only wait_agent and automatic final-result delivery.
• Update the Rust default, Node fallback, hook matcher, management Skill, bilingual guides, security policy, tests, and release gate together.

Compatibility and validation

Rust and Node offline tests cover signed initial handoff, target registration, all known flattened and separator-based collaboration tool names, targeted follow-up denial, untouched non-Kimi targets, registration expiry, dedicated follow-up error classification, opaque-provider-state omission, and the existing Responses/tool compatibility suite. The immutable GitHub workflow reruns formatting, all Rust/Node tests, cross-implementation protocol parity, both macOS builds, packaging, and asset digest verification.

Version 0.4.0 already passed the user-authorized native Desktop initial-handoff/final-result check. The optional 0.4.1 long-task guard check is documented separately and must not run without explicit user consent because its initial child creation contacts Kimi and consumes quota.

Security and upgrade notes

The bridge still never decrypts, guesses, logs, or forwards OpenAI provider-private encrypted_content. Target records contain only a session ID, task name, and timestamps; filenames are SHA-256 hashes, files use user-only permissions, registrations expire after six hours, and stale records are removed after 24 hours.

Upgrading the binary is not enough: rerun codex-kimi-bridge hooks install, fully restart Codex Desktop, open /hooks, and review/trust the updated UserPromptSubmit and PreToolUse commands. The updated matcher is what blocks unsafe follow-ups before they reach a running Kimi child.