The extension checkout at ~/.agents/extensions/agent-comms sat at v1.24.0 for two months while npm published 3.x, and v1 and v3 cannot interoperate at all (different protocol, port, and identity derivation). Nothing surfaced the drift until someone inspected running process command lines by hand: whoami reports identity and status but never a version, and the extension install tracks a manually-pulled git checkout rather than published releases.
Two cheap fixes, either or both:
- The bridge reports its own version in
whoami and status output, so version drift across a mesh's bridges is visible to every agent and to scripts, rather than discoverable only by inspecting processes.
- The bridge warns when a newer release exists on npm than the one it is running (a version check at startup or on a slow interval, failing soft when offline), so a stale checkout announces itself instead of silently splitting generations.
The extension checkout at ~/.agents/extensions/agent-comms sat at v1.24.0 for two months while npm published 3.x, and v1 and v3 cannot interoperate at all (different protocol, port, and identity derivation). Nothing surfaced the drift until someone inspected running process command lines by hand:
whoamireports identity and status but never a version, and the extension install tracks a manually-pulled git checkout rather than published releases.Two cheap fixes, either or both:
whoamiandstatusoutput, so version drift across a mesh's bridges is visible to every agent and to scripts, rather than discoverable only by inspecting processes.