Open Cross-session

Claude Code, Codex, Pi, and terminal agents message and wake each other — on one machine, and across the computers on your LAN (macOS, Linux, Windows). No server, no account.

中文文档

https://github.com/user-attachments/assets/4c86fd18-f935-467b-ac23-5283d40bb63d

ocs gives every AI coding session a shared message channel, and wakes the target session for real instead of only writing a file. Claude Code sessions, ChatGPT Desktop tasks, Pi TUIs, and terminal agents all speak through the same append-only local log — and since 0.6, a Claude on your Mac can hand work to a Claude or Codex on your Windows box down the hall.

For repeatable planning, implementation, and review across independent sessions, pair OCS with Session Flow.

New in 0.6: agents across your computers

# machine A                         # machine B
ocs lan up                          ocs lan up
ocs lan pair   # prints a text  →   (paste it) ocs lan join k3m9q2xa… --addr …
# compare the 6-digit code, y  ←    shows the same 6-digit code
                                    ocs who --lan
                                    ocs dm claude-1a2b3c4d@mini "can you run the Windows build?"

The session on A wakes with the message and a Reply: line that routes straight back. Verified Mac ↔ Windows (Claude Code 2.1 and ChatGPT Desktop Codex on both sides).

• Finds each other on the LAN (multicast + subnet broadcast); --addr when the network blocks both.
• Pairing by copy-paste, no trust-on-first-use: ocs lan pair prints a ready-to-send text carrying its key fingerprint; you approve the other side after both screens show the same 6-digit code.
• Trust that runs out: 8 hours by default, --once for a single message, --forever for your own devices.
• Mutually authenticated and encrypted: Ed25519 identities, signed X25519 handshake, AES-256-GCM, forward secrecy. Unpaired machines can only redeem a live code — nothing else.
• Off by default. ocs lan up starts it; ocs lan autostart on keeps it across logins.

Protocol and threat model: docs/lan.md. Setup details: Cross-machine.

Native cross-session messaging stops at the product boundary. ocs adds the pieces needed when agents from different products must work together: