Discover and explore top open-source AI tools and projects—updated daily.
quailyquailyAI agent messaging tool with P2P and E2EE
Top 99.3% on SourcePulse
Aqua provides a secure, peer-to-peer messaging protocol and CLI tool designed for AI agents, enabling robust communication across networks. It addresses the need for reliable, end-to-end encrypted message exchange between distributed AI entities, offering features like identity verification and durable storage, thereby facilitating complex agent interactions and workflows.
How It Works
Aqua operates on a decentralized, peer-to-peer architecture, leveraging libp2p for networking. Core functionalities include end-to-end encryption for message confidentiality, identity verification to ensure message authenticity, and durable message storage via inbox/outbox mechanisms. It supports Circuit Relay v2, allowing agents to connect even behind NATs or firewalls, and provides a simple Command Line Interface (CLI) for node management, contact handling, and message sending. This approach prioritizes security, reliability, and cross-network interoperability for AI agent communication.
Quick Start & Requirements
Installation is available via a pre-built binary script or by building from source using Go.
curl -fsSL -o /tmp/install.sh https://raw.githubusercontent.com/quailyquaily/aqua/refs/heads/master/scripts/install.sh; sudo bash /tmp/install.shgo install github.com/quailyquaily/aqua/cmd/aqua@latestaqua id, aqua serve, aqua contacts add, aqua send, and aqua inbox list. Relay mode configuration is also detailed for enhanced connectivity.Highlighted Details
Maintenance & Community
No specific details regarding maintainers, community channels (e.g., Discord, Slack), sponsorships, or roadmaps were found in the provided documentation.
Licensing & Compatibility
The license type and any associated compatibility notes for commercial use or closed-source linking are not explicitly stated in the provided README.
Limitations & Caveats
The project details an extensive list of common connection and protocol errors, suggesting potential complexities in network setup, configuration, and inter-agent communication. Features like group E2EE are listed under "Next Steps," indicating ongoing development and potential for evolving API stability. The reliance on specific network configurations and the detailed error handling imply that achieving stable, reliable communication may require significant troubleshooting.
2 weeks ago
Inactive