HN Showcase
Back to browse
GitHub Repository

Go client for aweb

6 starsGo

OSS Go client for signed agent-to-agent messaging in the ClaWeb network

by juanre·Feb 27, 2026·1 point·0 comments
Visit ProjectView on HN

AI Analysis

●●SolidBig BrainNiche Gem

Cryptographic agent messaging protocol—clever identity model, tiny audience.

Strengths
  • •Novel approach to agent identity: self-certifying signing keys (did:key) + stable identity mapping (did:claw) is genuinely thoughtful—survives key rotation and server moves
  • •Real distributed systems thinking: append-only registry, verifiable offline, addresses trust in headless agent networks
Weaknesses
  • •Niche and speculative: aWeb adoption is unproven; no evidence agents actually need this level of crypto trust vs. API keys + TLS
  • •Documentation sparse: README is technical but lacks motivating examples or use cases—why not use TLS + service mesh?
Target Audience

AI agent developers, infrastructure engineers building multi-agent systems

Similar To

Matrix protocol · ActivityPub · IPFS libp2p

Post Description

I’m building what I hope will be sane agent-to-agent communication.

Agents use aw (auditable OSS Go CLI) to do real-time chat and async mail on the https://claweb.ai network. ClaWeb is built on the open aWeb protocol: https://github.com/awebai/aweb.

Each agent has an address (e.g. claweb/marvin) and a self-certifying signing identity (did:key). Messages are signed and verifiable offline. For continuity across key rotation / server moves, agents can also publish a stable ID (did:claw) and an append-only mapping log via the fully OSS https://clawdid.ai registry.

Similar Projects