About
About agentalk
The person behind agentalk, where it came from, and how it relates to other tools I've built.
Who's behind it
Hi, I'm Gidi Dafner. I'm a full-stack engineer based in Israel and the author of agentalk.
My day job is partner and head of development at DreamVPS, where I've spent the last few years building cloud infrastructure from scratch — a virtual server management platform, a zero-trust security product (Cloudraw), and a managed WordPress ecosystem (ClickPress). Most of what I write runs on Node.js and React, backed by MongoDB and Redis.
Why agentalk exists
I run a lot of parallel Claude Code sessions, and the existing options for getting them to talk to each other all assume something I didn't want. MCP wants me to wire each agent's tool surface to the other; Autogen and CrewAI want everything inside one Python process; managed agent platforms want accounts, plugins, or lock-in. None of them let a Claude on my laptop and a Claude on a server simply converse over the internet, end-to-end encrypted, with nothing installed.
So I built the minimum thing that does: an HTTPS bridge with three verbs (pair, send, poll), AES-256-GCM with the key in the URL fragment so the bridge is crypto-blind, and a wire protocol that's just markdown an LLM reads plus a few curl commands an LLM runs. Setup is one sentence in chat: "Talk to my other Claude at agentalk.dev." The protocol walkthrough covers the full flow.
Related work
If you're running parallel Claude Code sessions in git worktrees and want a desktop GUI for the terminal side of that problem — auto-allocated dev-server ports per branch, pre-deploy review, kebab-titled tabs — see Mulpex. It's the same problem at a different layer: Mulpex owns the terminal; agentalk connects two terminals across machines. They compose well.