Repository navigation
中文说明 / Chinese release notes: 1.5.0_CN.md
Version 1.5.0
Release Date: November 17, 2026
Overview
Version 1.5.0 adds task delegation between CLIs managed by the same daemon. Codex can ask Claude Code to review a change, or start an independent session for a separate task. Task status, results, and approval requests appear in WeChat, WeCom, or Telegram, where you can follow the work and respond when needed.
The release also adds /pin and /unpin to keep a default window for remote messages while preserving commands that specify another destination, such as /2 <prompt>. Bridge modes now adjust as windows close, restoring /open when other CLI types have exited.
CLI collaboration and workers
Delegate tasks and receive results
Delegated tasks run in the background and queue while the receiving CLI is busy. The caller can continue working; results return as a new turn when the task finishes. Results that the caller has already retrieved are not delivered again. Task exchanges, approval requests, and questions are mirrored to the operator's chat.
The new cli-bridge MCP server provides eight tools:
| Tool | What it does |
|---|---|
list_agents |
List the daemon's CLI windows and workers, including their workspace and state |
send_to_agent |
Delegate a task to a named CLI and receive a call ID |
get_agent_call |
Check task status and results, or wait for completion or a pending approval or question |
interrupt_agent_call |
Remove a queued task or interrupt a running one |
open_agent |
Start a separate worker with a fresh session |
close_agent |
Close a worker you opened |
new_agent_session |
Start a fresh session in an idle worker you own |
resolve_agent_approval |
Respond to permission requests from a task you delegated, subject to the approval rules below |
Automatic tool configuration
- Claude Code launched by the bridge receives the tools automatically.
- Codex receives them when the bridge starts and manages its app-server.
- Attaching an existing Codex session through
$codex-bridgedoes not automatically change that session's MCP configuration. - OpenCode and Pi can receive tasks through the daemon. Tools for initiating calls are not configured automatically for these CLIs.
For manually configured MCP clients, the package includes the cli-bridge-mcp command, which serves MCP over standard input and output (stdio). Start the daemon before using it. Set CLI_BRIDGE_AGENT_BUS=0 to disable automatic tool configuration when launching a CLI.
Independent worker sessions
Workers provide a fresh session for an independent task without changing the bridge mode or active window of your existing sessions. Codex workers run in the background by default, with an option to open a visible window. Other CLI workers use visible terminal windows.
Each caller can keep up to four workers open. Only the CLI that created a worker can close it or reset its session, and its workers close when that CLI exits. Existing sessions remain unchanged.
Approval handling
Collaboration tools do not require an additional MCP approval by default. The receiving CLI's own permission settings still apply. With CLI_BRIDGE_STRICT_APPROVAL=1, collaboration tool calls also follow the CLI's approval settings, and the bridge starts with automatic approval disabled.
A caller can confirm only requests permitted by the shared automatic approval rule. High-risk permission requests raised by the receiving CLI require the operator's confirmation; callers may still deny or abort them where supported. Pi permission requests always require the operator. If both the operator and the caller respond, the first valid decision takes effect.
Pin the default window
After /pin, messages and controls without an explicit destination continue to use the pinned window, even when you switch windows locally. Commands such as /2 <prompt> can still address another session.
| Command or message | Behavior |
|---|---|
/pin |
Keep the current window as the default target; repeating it keeps an existing valid pin |
Plain text or a control such as /stop without a destination |
Use the pinned window |
/2 <prompt>, /codex <prompt>, or a bound emoji command |
Send the message to the specified destination without changing the pin |
/1, /2, /cd, /open, /all |
Keep their existing switching, opening, and broadcast behavior |
/unpin |
Follow the active window again |
Each bridge can pin one window. The pin expires when you remove it, close the window, or restart the daemon. If the pinned window closes, the next message without a destination is not forwarded: the bridge clears the pin and asks you to select a window and resend the message. A new window does not inherit the old pin, even if it reuses the same number.
Codex /resume also uses the target window's workspace and instance, preventing pinned or numbered commands from resuming a different session.
Thanks to TS / ww358723647 for the pinning contribution in PR #53.
Automatic bridge mode adjustment
As windows close, the bridge selects the mode appropriate for those that remain:
- One remaining window returns to single-bridge mode. Replies no longer carry a source prefix, and
/opencan add another window. - Several windows of one CLI in one directory use numbered multi-instance mode.
- Different CLI types with one window each in one directory use multi-CLI mode.
- Several working directories retain workspace, CLI, and instance commands. If only one directory remains but still contains both different CLI types and multiple instances of a type, those commands stay available until one of the simpler modes applies.
Mode changes preserve existing window numbers. When the active window closes, the bridge selects a remaining window. Visible windows opened from the chat are also removed from the bridge when they close, while the resident daemon stays running. Existing Codex sessions connected through attach mode retain their original lifecycle.
Compatibility and upgrade
Codex compatibility is verified against the protocol capabilities required by the bridge. The bridge no longer defines a fixed supported version range. Attaching an existing Codex session still requires the shared daemon available in version 0.162 or later. Node.js requirements remain >=22.13.0, or >=22.19.0 for Pi.
All three package names provide the same version and commands. Choose one installation command:
npm install -g cli-chat-bridge@1.5.0
# Or, for either existing package name:
npm install -g cli-wechat-bridge@1.5.0
npm install -g @unlinearity/cli-wechat-bridge@1.5.0Uninstall the current package before switching names to avoid command conflicts. After upgrading, stop and restart the daemon and its CLI windows to load the updated code and MCP configuration. Credentials and saved sessions require no migration. Pinned windows, pending collaboration tasks, and worker ownership are not restored after a daemon restart.
Full Changelog: 1.4.1...1.5.0
Full Changelog: 1.4.1...1.5.0