ccshare

Product Introduction

1. Definition: Manycode (also known as ccshare) is a real-time, peer-to-peer terminal sharing and collaborative coding platform. Technically, it is a CLI tool and native application that creates a multiplexed pseudo-terminal (PTY) session, enabling live screen mirroring and bidirectional input for command-line interfaces and AI coding agents.
2. Core Value Proposition: It exists to enable instant, zero-setup, "AirDrop-style" collaboration for developers and engineers working in terminal-based environments, particularly with AI coding assistants like Claude Code, eliminating the friction of screen sharing, environment syncing, and tool installation for pair programming and live debugging.

Main Features

1. Live Terminal Mirroring with Shared Control: The core technology wraps a user's CLI session (e.g., claude, codex) in a real PTY. It then broadcasts a session hash derived from a simple 6-character alphanumeric code via UDP for LAN discovery. Connected clients receive a live stream of the terminal output, and input from any connected user is forwarded to the host PTY, allowing true collaborative typing. The viewport dynamically resizes to the smallest connected terminal to ensure a consistent visual frame for all participants.
2. Multi-Platform Access (CLI, Browser, Native App): Users can join a session via the CLI (manycode join CODE), a secure browser-based terminal client accessible via a unique HTTPS URL (powered by a bundled Cloudflare Quick Tunnel), or a native macOS application. The browser client requires zero installation, enabling participation from any device, including mobile phones. The native app provides a dedicated window with a live terminal, session code display, and a built-in room chat sidebar.
3. Flexible Networking & Security Modes: Sessions default to LAN-only using UDP broadcast for discovery. Optionally, a secure WebSocket tunnel is automatically established via cloudflared (no account required) for WAN connectivity, generating a random, unguessable URL. Advanced users can specify a direct host (--host IP:PORT), use a self-hosted relay server (via CCSHARE_RELAY environment variable), or enforce session approval (--approve) where the host must manually allow each connection via a macOS dialog.

Problems Solved

1. Pain Point: The high friction and tooling overhead for impromptu terminal-based pair programming, debugging sessions, or live demonstrations. Traditional methods involve complex screen sharing (which often degrades terminal readability), syncing development environments, or using heavyweight, account-based collaboration platforms.
2. Target Audience: Software developers, DevOps engineers, data scientists, and technical educators who frequently use terminal-based AI coding agents (Claude Code, Cursor, Windsurf) or work in CLI environments. It is particularly valuable for remote teams, workshop instructors, and developers seeking real-time assistance.
3. Use Cases: Rapid debugging assistance where a colleague can directly examine and interact with a live shell session; conducting live coding workshops or technical interviews where participants need to see exact terminal output; collaborative pair programming on a server or container environment; providing temporary, secure access to a terminal for support without sharing credentials.

Unique Advantages

1. Differentiation: Unlike generic screen sharing tools (Zoom, Discord), Manycode transmits crisp, text-based terminal data, ensuring perfect readability and low bandwidth use. Compared to traditional terminal multiplexers (tmux, screen) which require SSH and shared user accounts, Manycode offers instant, secure, code-based access without system-level permissions. It is more lightweight and focused than full IDE-based collaboration tools.
2. Key Innovation: The combination of dead-simple, memorable 6-character codes for session discovery and the seamless fallback network stack (LAN broadcast -> direct connection -> managed tunnel). The automatic provisioning of a secure, ephemeral public tunnel with no user configuration or account signup dramatically lowers the barrier to cross-network collaboration, making "anywhere" sharing a default, not an advanced feature.

Frequently Asked Questions (FAQ)

1. Is Manycode secure for sharing a live terminal session? Security is based on secret knowledge of the 6-character session code, which functions as the sole authentication token. Users must share this code as carefully as they would a temporary password. LAN traffic stays local; the optional public tunnel uses a long, random URL combined with the code. For sensitive work, use the --no-tunnel flag for LAN-only mode or --approve to manually vet each connection.
2. Can I use Manycode with AI coding assistants other than Claude? Yes. While optimized for Claude Code, Manycode is a generic PTY mirror. You can host sessions for any terminal-based agent or shell command using syntax like manycode host codex, manycode host opencode, or manycode host bash.
3. How does the browser-based joining work without any installation? The hosting instance bundles and runs cloudflared to create a secure Cloudflare Tunnel, exposing a local WebSocket server via a public HTTPS URL (e.g., *.trycloudflare.com). The join link points to a static web page that loads a terminal emulator (like xterm.js) which connects to this tunnel, streaming the PTY output and sending keystrokes back.
4. What happens if a joiner disconnects? Joinees can detach at any time using Ctrl-\] in the CLI or by closing the browser/native app window. This does not terminate the host's session. The host continues working uninterrupted, and the joiner can reconnect using the same session code while it remains active.
5. Can I record a collaborative Manycode session? Yes. Using the --record flag during hosting (e.g., manycode host --record) will save the entire session—including output from all participants—to an asciinema-compatible .cast file. This file can be replayed locally with asciinema play or uploaded to asciinema.org for sharing.