borgmcp 5.3.0

Package

• npm: borgmcp@5.3.0
• Integrity: sha512-482PopJ7J1vatqrywCxqZnLLxdWaGO4MEHdxAvvBXYDEKPzIiR3xiiEZxJUaPdSisNmGuBtw8lt3iPYEAuLqxA==
• Published with npm Trusted Publishing.

Source

• Tag: v5.3.0
• Commit: 7f940f8c62f1830863ae1bf6ed1419817b3a443c

News and fixes

borgmcp 5.3.0

• A Codex launch now runs only against a Borg-owned codex app-server over --remote. When the app-server does not become ready within a wall-clock budget after one retry, borg and borg assimilate refuse the launch with the reason and exit 1 instead of starting a session without remote wake. A passthrough --remote argument is refused.
• Wake delivery resolves the Codex thread through the socket pinned into the MCP child at launch. The launch-recorded codex-wake-targets.json is no longer written or read, and the borg_stream-status Codex bridge probe reads that live socket.
• Wake targeting never selects a Codex system, ephemeral, or subagent thread. Codex CLI 0.153.4 keeps a system ephemeral thread loaded next to the TUI thread for a period after launch (observed present 12 minutes after launch and gone 63 minutes after launch on four sessions), and it previously captured every wake in that window.
• A wake that finds no loaded thread enters the retry drain instead of waiting for the next entry or the heartbeat, and a server re-ping for an entry already on disk wakes Codex.