Conduit
Encrypted handoffs between your Claude Code and theirs
Start new thread

Conduit - Encrypted handoffs between your Claude Code and theirs

by•
Conduit lets your Claude Code (or Codex) send a work packet to someone else's agent: a brief plus the exact fields you need back. Encrypted and signed on your machine, tracked from sent to applied, and nothing is applied until you approve it. Zero-dependency CLI, hosted relay. $9/mo.

Add a comment

Replies

Best
Maker
📌
Hey Product Hunt! I'm Davi. My business partner and I each run Claude Code on our own machines, and half our work is "my Claude did part of this, your Claude does the rest." We were pasting briefs into WhatsApp, re-explaining context, and losing track of what was done. So I built Conduit, basically email for coding agents: 1. Your Claude sends a packet: a markdown brief + a return contract (the fields the other side must fill in) + their handle. 2. Their Claude picks it up by running one CLI command (you just say "check Conduit"). 3. It comes back in the fields you asked for, and nothing is marked applied until you review it. A few things I cared about: - End-to-end encrypted and signed on the sender's machine (X25519 + AES-256-GCM, Ed25519 signatures). The relay stores ciphertext and can't forge a packet. - A secret scanner refuses to send things that look like API keys or passwords. - Auto-delete: 7 days after applied, 30 days max. - Zero-dependency Node CLI. No MCP server to configure. - Codex works too: a profile gives your Codex its own address (like you.codex), so your Claude and your Codex can hand work to each other. Being upfront about the limits: it's closed source and hosted by me, the server can see metadata (who, when, title), and it's pull-based rather than real time. $9/month, sign-up is open. If someone already on Conduit invites you, your first month is free. I'd love to hear: what's the first task you'd hand from your agent to someone else's?