Repository navigation
Agent Messaging Server 0.1.3
·
8 commits
to main
since this release
A patch release of the Agent Messaging Server: the server and the A2A gateway, for the core profile of Agent Messaging 0.7.0, on NATS JetStream or on RabbitMQ with Postgres.
Images
docker pull ghcr.io/jeffrschneider/agent-messaging-server:0.1.3
docker pull ghcr.io/jeffrschneider/agent-messaging-a2a-gateway:0.1.3Both are linux/amd64, built from this tag and tested by the release workflow (first-run from an empty volume, NATS on what it wrote, the server, a live revocation, the A2A gateway connecting).
What changed since 0.1.2
- A new door for the admission roster (EXT-6 §7):
GETandPUT /v1/rosters/<owner key>. A roster is stored only when it is signed by the key it is stored under, so no login is needed and the operator cannot forge one. An agent's own client can now keep its roster on the server, where a guarded inbox enforces it. Before, the server kept rosters only through its admin API (#10). - The admission service relays
describeandknockwhatever the roster says, as §10.14 and EXT-6 §9.3 require. Before, a describe from a sender the roster blocked was dropped (#10). - A server with no environment file names no naming service. Before, its rooms service and its name checks asked AgentMesh's naming service about the server's own agents by default. Set
PAN_REGISTRARto use a naming service (#10). - The server and the gateway run SDK 0.60.0.
The TypeScript SDK
SDK 0.60.0 is its own release, sdk-v0.60.0, with its tarball and SHA-256. It gives an agent its own door (knock, the waiting list, admit, block, an inbox), answers and asks describe, and has no built-in addresses. It is also at https://storage.googleapis.com/agentmesh-releases/agent-messaging-0.60.0.tgz (SHA-256 5d51d8d34e19b2fed0fdd715b0a078d991f5dc2d715a8096ce38348256b32291).