Tooling
AMP
Real-time communication layer for autonomous agents, deployable on Quilt infrastructure as an isolated service runtime.
AMP is a production-oriented Agent Mail Protocol implementation in Rust.
On Quilt, it fits as a deployable communication service: a real application runtime with its own protocol surface, state model, and operational behavior, hosted inside isolated Quilt infrastructure.
GitHub: saint0x/amp
What AMP Is For
- real-time agent-to-agent messaging
- token-authenticated agent connections
- topic, direct, and broadcast routing
- durable inbox and delivery-state handling
- WebSocket and HTTP-based operational control
- isolated service deployment on Quilt infrastructure
Why It Matters In Quilt
AMP matters because Quilt is not only a place to launch generic containers. It is also the place where communication-heavy application infrastructure can run as a real service.
Quilt gives the platform:
- isolated execution
- OCI-backed environment delivery
- networking and published access primitives
- durable runtime and lifecycle behavior
AMP adds the application layer on top:
- message delivery
- daemon-to-daemon federation
- agent presence and acknowledgements
- runtime inspection and metrics
- a CLI centered on
serve,msg,agent,topic,inspect, andruntime
Mental Model
Think of AMP as:
- a communications daemon
- exposing both WebSocket and HTTP surfaces
- with durable or in-memory storage modes
- running inside a Quilt-hosted service environment
That is different from using Quilt as a generic container toolbox or a one-off interactive shell.
Where It Fits
| Need | Better choice |
|---|---|
| Real-time agent messaging service hosted by Quilt | AMP |
| Raw runtime operations and container semantics | Quilt runtime docs |
| Cluster, node, and workload orchestration | quiltc |
Relevant AMP Surface
The upstream AMP project exposes:
- WebSocket ingress at
/ws - health at
/health - peer forwarding at
/v1/peer/messages - agent inspection at
/v1/agents - topic and system inspection endpoints
- SQLite-backed or in-memory storage
Those details matter in Quilt because they determine how the service should be deployed, exposed, and reasoned about once it is running on platform infrastructure.
Native Container Selection
AMP is accessed through Quilt’s normal container create path.
Users select the curated AMP runtime the same way they select other first-class Quilt images: through native container image selection inside Quilt itself, using selectors such as amp.
This page keeps the focus on AMP itself. The important point is that AMP belongs in the Quilt tooling model as a direct runtime surface, not as a separate launcher lane.