oxide-mesh 0.3.0

Inter-agent communication for Rust Oxide. Tokio-channel mesh for in-process federation plus a JSON-framed TCP transport for cross-host peers; ties into oxide-k via the message bus.
Documentation

oxide-mesh — Inter-Agent Communication

Lightweight, transport-agnostic peer-to-peer fabric for Rust Oxide agents. Two transports ship today:

  • [local] — in-process tokio::sync::mpsc channels. Used by tests and embedded multi-agent setups where every peer shares the same Tokio runtime.
  • [tcp] — JSON-line framed TCP. Used for cross-process / cross-host peers. The wire format is one [PeerMessage] per line, so it inter- operates with hand-rolled clients (netcat for debugging is fine).

The protocol is intentionally small — five message kinds — and is deliberately not libp2p. Future federated-learning work will pile gossip and CRDT primitives on top of this base layer rather than adopting a whole networking stack.

[MeshModule] exposes the mesh on the oxide-k bus so agents can send broadcasts, direct messages, and task assignments through standard kernel plumbing.