agent-yes

Blog & design notes

How agent-yes is built, and where it's going.

Architecture · living map

The agent-yes graph — today & tomorrow

An interactive map of the whole system: one agent → one local fabric → one API handler → many transports → one URL. What's built, what's experimental, and what's next.

Feature

ay callback — let readers message your agent from any web page

A signed, send-only, single-agent capability plus a one-script embed widget: report pages that can talk back, with a required expiry and a revoke kill-switch — never your serve token.

Security

End-to-end encryption for agent-yes share links

How share links stay private even if the signaling relay is compromised: an HKDF key split, AES-256-GCM with per-connection keys, and a fail-closed handshake.