amp

Agent Mesh Protocol — a pure-Rust library family for messaging across a WireGuard-secured mesh of agent-operable services.

AMP follows the AmigaOS ARexx convention: every service in the mesh exposes a named, addressable port; any peer can send it a command, call it for a reply, or subscribe to its event topics. The broker (cosmix-noded, in cos) routes messages between peers; everything inside the mesh is trusted on a per-WireGuard-subnet basis. amp is the protocol library that lets a service participate.

Crates

Crate	What it is
cosmix-lib-amp	Wire format. AmpMessage request/reply/event types, serialisation independent of target. The native feature adds Unix-socket helpers used by the broker; client code typically leaves the default features on.
cosmix-lib-client	NodedClient — broker WebSocket client. Native (tokio + tokio-tungstenite) and wasm32 (gloo-net) targets. Caller supplies the broker URL.
cosmix-lib-props-core	SPEC 07 property read surface — PropTree, PropPath, PropValue by default; the dispatch_props AMP-wire handler and publish::* event builders gated behind the opt-in amp feature. Paired with the substrate-side cosmix-lib-props-store in cos.

amp deliberately holds the protocol layer only — no storage, no TLS, no config-file loading, no auto-resolve of broker URLs. Anything substrate-shaped lives in cos.

Building

amp builds standalone — no sibling checkouts required.

git clone https://github.com/markc/amp ~/.amp
cd ~/.amp/src && cargo build --workspace

Tests:

cd ~/.amp/src && cargo test --workspace

Lints:

cd ~/.amp/src && cargo clippy --workspace --all-targets -- -D warnings

Using as a library

amp is not on crates.io yet. Cargo's git dependency form has no sub-directory selector and this workspace lives under src/, so depend on it via path-deps to a sibling checkout:

git clone https://github.com/markc/amp ~/.amp

[dependencies]
cosmix-lib-amp    = { path = "../../amp/src/crates/cosmix-lib-amp" }
cosmix-lib-client = { path = "../../amp/src/crates/cosmix-lib-client" }

(Once the crates publish, depend via version: cosmix-lib-amp = "0.1" etc.)

Minimal NodedClient usage:

use cosmix_client::NodedClient;
use serde_json::json;

#[tokio::main]
async fn main() -> anyhow::Result<()> {
    let client = NodedClient::connect("my-service", "ws://localhost:4200/ws").await?;
    let pong = client.call("noded", "noded.ping", json!(null)).await?;
    println!("pong: {pong}");
    Ok(())
}

examples/test_noded.rs under cosmix-lib-client/ is a manual broker-acceptance harness — run it against a live cosmix-noded to exercise the wire end-to-end.

Where the broker comes from

amp ships the client and protocol — not the broker. The reference broker (cosmix-noded) lives in cos. A bare-system amp consumer can still serialise / deserialise AmpMessage values without a broker present; NodedClient::connect is the call that requires one.

Related projects

• mix — ARexx-flavoured scripting language with send / address / emit / on … do as first-class keywords, built on amp.
• cos — the cosmix daemon family: broker, mail, web, DNS, knowledge indexer, display compositor. Consumer of amp; ships the broker.

License

MIT. See LICENSE.