# borgmcp 4.2.3

Package

• npm: borgmcp@4.2.3
• Integrity: sha512-oPiczsaot6yRf9CJ43FgmsqZJWf0J60ouGhqFJhP2doElkvfH/0c5GNxSssDoCZpZ1LxWAQBvRRiKfXvSbGWQA==
• Published with npm Trusted Publishing.

Source

• Tag: v4.2.3
• Commit: 3c2367b90c823abef6805ac437fa8f21e57a5d1f

News and fixes

borgmcp 4.2.3

• The Codex wake-path health surface now reflects real delivery state. Previously borg_stream-status and borg_regen reported the Codex wake path as healthy whenever the app-server bridge was armed, even while a directed activity-log entry sat undelivered — a wake deferred behind a mid-turn thread, retrying, or unable to resolve a target could read healthy for many minutes. The health now folds in the live delivery state, so a deferred, retrying, failed, or undeliverable wake reports degraded instead, and borg_stream-status surfaces the selected target, the last injection attempt and result, the deferred-queue state, and the last failure code (no message contents or secrets). Health returns to healthy as soon as the wake is delivered or the unread log is drained by any path. The wake mechanism, retry cadence, and timing are unchanged, and delivery remains exactly-once.