# borgmcp 4.4.0

Package

• npm: borgmcp@4.4.0
• Integrity: sha512-UZQxXLp1V6QTu6Aq5/KVW+uSKdpyAH6qlx8M2SZ0Lc8J62QUW04LhdgOVT+mPbamU70cO3l8bv6E/Ae2v32++g==
• Published with npm Trusted Publishing.

Source

• Tag: v4.4.0
• Commit: 3d6077e0b13aa68fdc794303c66ebfe9e6cf1a84

News and fixes

borgmcp 4.4.0

• borg_roster now accepts an optional since entry ID or timestamp and marks each connected drone as awake or stale relative to that point. This lets a coordinator check whether recipients have posted after a dispatch instead of inferring wake delivery from activity-log silence (#351).

• OpenCode identity-sensitive handler tests now isolate the inherited agent environment, preventing an ambient BORG_AGENT_KIND value from selecting the wrong runtime path and producing environment-dependent failures (#512).

• OpenCode launch identity confirmation is now bounded. A wedged drone fails after five seconds instead of waiting indefinitely. The failure cause is not currently visible in OpenCode's user interface; #515 tracks that separate diagnostic gap (#511).

• borg update --registry <https-url> now permits an operator to acknowledge an alternate configured npm registry for one invocation. The exact normalized URL remains bound through package lookup, installation, client re-entry, and recovery commands, and the acknowledgement is never persisted. If the configured registry changes after an earlier phase completes, Borg reports the partial state and refuses before any subsequent package mutation; recovery distinguishes restoring the acknowledged registry from deliberately acknowledging the replacement (#177).

• OpenCode wake diagnostics now distinguish HTTP 401, HTTP 404, incompatible-API, timeout, and transient failures. borg_stream-status reports the target session, last injection attempt and result, last accepted entry, and last failure code while preserving independently ordered observations. Per-drone bounded 0600 logs replace the shared unrotated machine-global log, and failures to write those logs are written to stderr rather than silently swallowed. That stderr reaches operators only on harnesses that consume MCP stderr; OpenCode 1.18.19 discards it, with #515 tracking that gap (#5, #8).