Cosyncing

From CLI to GUI, live and in sync

Website · Install · Client · Docs · Contributing · 简体中文 · 日本語 · 한국어 · Español

---

Synchronize and control your agents — from CLI to GUI, from desktop to phone. Pick up right where you left off, anywhere. cosyncing keeps your coding agents in sync across your own network.

The broker runs on the machine where your agents work. It watches their sessions and serves a client that shows each one — grouped by project, with its transcript, diffs, commands, and any prompt waiting on you. Read a session, answer a prompt, or take over. No account to create, no hosted service between the client and the broker.

Supported agents

One protocol covers all twelve. Per-agent control differs: a Claude Code session in your own terminal syncs with the app in both directions, including approvals, once setup installs its mod; without the mod it opens read-only until you take over. See supported-agent setup for versions and installation, and adapter support for the capability matrix.

Foreground clients can join the same broker-owned Codex, Pi, omp, or Reasonix Drive session without starting a second native Resume. A Claude Code session without the mod keeps its Observe/Take-over flow on another client, while OpenCode keeps its shared-live behavior. Background Observe connections stay read-only.

Experimental: Eight provisional adapters are available to source contributors. Kimi Code observes every session on a kimi web server read-only, drives the ones cosyncing created — prompts, approvals, model selection — and takes over the ones it did not, explicitly. DeepSeek Harness connects to a dsh web host and gives active foreground clients a shared transcript and control surface, with model and reasoning-effort selection, permission presets, the host's own slash commands, and image attachments. General file attachments are not supported — the host accepts image content only — and background resident subscriptions and some message presentation remain follow-up work. Antigravity reads the Antigravity CLI's own conversation store — no server involved — replays every conversation read-only, and drives one through a broker-owned agy child; two clients can share a Drive, and a write from a terminal hands the session back. omp uses its own packaged bridge and native RPC dialect for discovery, live sync, prompts, approvals, commands, models, file input, and session creation. Reasonix observes its bounded local store and resumes through a lazy broker-owned ACP child; joined clients share one writer, while terminal true sync and file input remain unsupported. Grok Build observes its bounded local store and, on 1.0.13 or newer, adds authenticated broker-owned ACP Create/Resume, prompts, approvals, commands, and model/effort/mode controls. Cline keeps bounded default-profile parent/subagent snapshots read-only, while app-created sessions use an isolated broker-owned Hub for Create/Resume, prompts, Stop, approvals, create-time model/mode, and shared Drive. Exact-id terminal handoff stays separate from that