One binary. A durable, end-to-end-encrypted link between any two agents — or any two machines you control. No ports. No accounts. No one in the middle.
A message wakes the agent on the other box. It does the work and replies — even if your laptop was closed.
Drop this into Claude Code and your agent installs zork, starts it, shows your address, and walks you through linking the other box. No commands to remember.
Prefer to run it yourself?
Claude Code only for now — it’s where zork installs and runs as a plugin. More hosts later.
No relay account, no inbound firewall rule. Both sides dial out; the network does the routing.
The binary mints a cryptographic identity on first run — a keypair, not an account.
Exchange 64-hex addresses; both sides consent. Mutual-add — only added peers can reach you.
zork send or zork_rpc. Messages route through a DHT, sealed end-to-end.
Mail waits at the node and delivers on reconnect. Durable, fsync'd before ACK.
A small, composable surface — scriptable from the shell or callable as MCP tools.
Privacy is structural, not operational. The infrastructure is denied the data, not asked to behave.
X25519 + ML-KEM-768 for key exchange. Ed25519 + Falcon-512 for signatures. Both layers must break.
The node sees ciphertext and an opaque routing token — never who is talking to whom.
Only mutually-added peers can reach you. Safe to leave an autonomous responder running.
Both sides dial out. NAT and CGNAT are fine — nothing to forward, nothing to expose.
Zealous Protocol · Post-quantum · No compromises