The Internet for Personal AI Agents.
AI agents are getting smarter every month — but they're brilliant hermits. Your Shadow doesn't know my Shadow exists. Calendars don't talk to each other, inboxes don't coordinate, and humans still do all the social glue: group chats, scheduling threads, swiping.
Shadownet is the missing connective tissue. A local-first, privacy-preserving protocol that lets personal AI agents discover each other, verify they represent real humans, and negotiate on their owners' behalf — without leaking private context to a central server.
- Coordination over capability — we don't build LLMs and we don't build agents; we build the infrastructure that lets them find each other and collaborate.
- Local-first privacy — your agent's memory and context never leave your machine.
- Decentralized identity — agents are bound to humans via DIDs, blocking Sybil attacks without a central authority.
- Human-in-the-loop — every agent ↔ human exchange flows through MCP, fully auditable.
- Sidecar — the per-user node. Holds the Subject's keys, contacts, and message history; exposes MCP tools to the host agent (Hermes, OpenClaw, Claude Desktop, …).
- SNS (Shadow Name Service) — DNS-style name resolution.
mahdi@shadownet.example→ endpoint + public key. - SCA (Shadow Certificate Authority) — issues Verifiable Credentials proving a Shadow represents a unique human (or an organization). Multi-issuer by design; verifiers run their own trust stores.
- A2A profile — agents communicate over Google's Agent-to-Agent protocol; Shadownet adds a thin handshake on top to exchange credentials.
Hubs (themed stranger-matching for Dating, Hiring, Roommates, …) are out of v0.1 scope.
For the full design, start with the protocol overview RFC.
| Repo | Status | What it is |
|---|---|---|
shadownet-specs |
🟢 Active | RFCs, JSON Schemas, worked examples — the protocol itself. |
shadownet-go |
🟢 Active | Go SDK + reference SCA, SNS, and CLI binaries. v0.1 surface complete. |
shadownet-py |
🟢 Active | Python SDK. v0.1 surface complete; consumed by hermes-social and shadownet-cloud. |
hermes-social |
🟢 Active | Sidecar reference implementation. Drop-in for any A2A-capable agent runtime. |
shadownet-conformance |
🌱 Early | Wire-level interop test suite. Runs against any Shadownet implementation. |
shadownet-ts |
🟡 Planned | TypeScript SDK for browser + Node. |
shadownet-cloud |
🟡 Planned | First-provider deployment: signup, Shadowname allocation, multi-tenant Sidecar host. |
The v0.1 protocol is drafted across seven RFCs in shadownet-specs: Overview, Identity, Credentials, SCA, SNS, A2A Profile, and MCP Tools. The Go and Python SDKs both ship the full v0.1 surface and are ready for downstream use. Wire-level conformance, the TypeScript SDK, and the first-provider cloud deployment are next. No public deployment yet — the canonical domain is still being chosen.
If you're a systems architect, cryptography practitioner, or AI infrastructure engineer, the RFCs are the place to weigh in.
Built for the post-browser internet.