multiplayercoding agents.

share your live Claude Code session with a 6-char code, AirDrop-style. your friend joins from their terminal - or just opens a link in their browser, nothing to install - sees your exact screen, and both of you can type. works over your wifi with zero setup, or anywhere through a free tunnel.

Download for Mac macOS 13+ · drag into Applications

First open: right-click manycode in Applications → OpenOpen. macOS warns once because the app isn't notarized yet — this gets past it. After that it opens normally.

$ curl -fsSL https://manycode.vercel.app/install.sh | sh

the app bundles nothing extra — it drives the same CLI, which the one-liner installs (onboards on first run, re-run to update) · MIT · no accounts · no telemetry · source on github

manycode - multiplayer claude code | Product Hunt
you
$ cd my-project
$ manycode host
 
 
7KQ 2FM
 
same wifi: manycode join 7KQ2FM
direct: manycode join 7KQ2FM --host 192.168.1.4:42518
browser: https://ideal-times-sing.trycloudflare.com/#7KQ2FM
 
* friend connected
your friend, same wifi
$ manycode join 7KQ2FM
manycode: looking for the session on your network…
manycode: connected (lan). Ctrl-] to leave.
 
╭─ your claude session renders here, live
same screen. same prompt. both keyboards work.
╰─

how it works

01
host
manycode host wraps claude in a real pty and prints a code. you keep using claude exactly as before.
02
share the code
say it out loud. on the same wifi that is the whole setup: discovery is a udp broadcast carrying a hash of the code, never the code itself.
03
join
manycode join 7KQ2FM attaches read-write. no terminal handy? they open the browser link instead - same live session, from any device. Ctrl-] detaches without killing it.

the details


security, plainly

the code is the only auth

anyone holding a live code can type into a real shell on the host's machine. share codes like you'd hand over your laptop, and only with people you trust. codes die when the session ends. lan traffic stays on your network; the default tunnel exposes your session behind a random unguessable url plus the code - use --no-tunnel to keep a session lan-only.