Releases: a2al/A2AL
v0.2.8
v0.2.7
Changelog
- 50a8475 feat(daemon/dht): parallel bootstrap, early ICE listener, and async NAT probe
- c5deec2 feat(daemon/dht): signal bootstrap fallback via hub proxy, FIND_NODE/FIND_VALUE routing fix, and faithful reply-to-sender
- d0f0acf feat(dht): replication NAT-endpoint prefetch, recovery notify, health-aware dial feedback, and daemon network-change handling
- 1457a6e feat(host): node-level transport pool and shared ICE connection reuse
- 7d58926 feat(natsense): per-IP symmetric NAT detection, cold-start consensus, and same-socket STUN prober
- 08cbb57 feat: MCP Registry publish workflow, server.json, glama.json, logo, and llms-install doc
- d84a53d refactor(dht): lazy hearsay verification, simplified routing maintenance, UPnP conflict detection, and retry scheduler
v0.2.6
Changelog
- 69df756 feat(dht): Anchor/Live peer addressing, inbound path learning, and reachability profile gating
- 1bc7221 feat(dht): ICE-aware sendplan, M6 routing, gap-fill replication, and punch improvements
- 144d4b0 feat(dht): IPv6 dual-slot routing, hub candidates, health-aware peer selection; daemon IPv6 signal hub and protocol updates
- 321b95b feat(net): IPv6 dual-stack transport, STUN/candidate improvements, hub discovery, and ICE/punch refinements
v0.2.5
Demo binaries (latest)
Pre-built binaries for demo1-node through demo6-swarm.
Replace every go run . in examples/<demo>/ with the corresponding binary name.
Compatibility: The demos in this release require a2ald v0.1.8 or later.
| File | Platform |
|---|---|
a2al-demos-linux-amd64.tar.gz |
Linux x86-64 |
a2al-demos-linux-arm64.tar.gz |
Linux ARM64 |
a2al-demos-darwin-amd64.tar.gz |
macOS x86-64 |
a2al-demos-darwin-arm64.tar.gz |
macOS Apple Silicon |
a2al-demos-windows-amd64.zip |
Windows x86-64 |
Built from commit 5c50667 · 26042770415
v0.2.4
Changelog
- 5964299 feat(daemon): system service support, data-dir locking, event bus, deploy configs, and auto-update subsystem
- bb37477 feat(mailbox): persistent mailbox with QUIC push, store, and subscription; protocol codec and DHT store improvements
- cfb14aa feat(mcp): stdio transparent proxy; improve daemon service, routing, and config; update docs
- 2927dce feat(webui): updater UI panel and service_tcp improvements; fix signaling reg-ack race
v0.2.3
Changelog
- 3af53aa feat(identity): encrypted export/import with envelope package and Web UI vault
- 7743e86 feat(webui): restructure identity import modal and improve local/remote connection gate UI
- 11a0ba1 feat: sovereign record signing, improved MCP tool descriptions, and node info / vault Web UI
- b1da005 fix: add clock-skew tolerance to delegation/record expiry; ICE-first routing for high-CPL DHT peers
v0.2.2
What's New
TURN Relay Support
Nodes behind extreme NAT (symmetric NAT, CGNAT) can now establish connections
via TURN relay. Relay usage is enabled by default and can be disabled per-node
(disable_relay = true in config) or per-call via the API, for users who
require strict peer-to-peer connectivity.
Improved NAT Traversal
- Synchronized hole punching for CGNAT traversal
- Endpoint cache to reuse previously successful paths
v0.2.1
Release Note
Significantly improved connectivity when both peers are on IPv6.
Changelog
v0.2.0
Major Milestone
A2AL has completed the full loop — from generating and publishing an AID to accessing any AID from anywhere in the world.
What's New
- Universal Gateway: Access any AID's services via
http://127.0.0.1:xxx/aid/{aid}/...locally, with native support for HTTP, MCP, and A2A protocols. - Peer-to-Peer Encrypted Tunnel: Establish an encrypted tunnel to any AID under any network condition, supporting SSH, RDP, and all TCP-based services.
- Universal URL Access (coming soon): Access any AID via a standard URL, compatible with all HTTP clients.
Getting Started
- Download and run
a2ald - Generate your own private, exclusive AID in one click
- Bind your service address to the AID — supports Agent services as well as general services like SSH and RDP
You can now connect to your AID and use your services or Agents from anywhere in the world.
Optional: To expose a service publicly, publish a Capability by filling in fewer than 5 parameters. Others can then discover your service through the Capability — no prior knowledge of your AID required.
No domain, no cloud service, no permission from anyone. Enjoy!