Skep
An open-source, lightweight session bus tool that lets local coding Agents on different machines join the same real-time session. It uses a master-peer topology, requires no account registration or cloud relay, and keeps keys on each device. It is intended for trusted network environments.
Timeline (last 90 days)
Skep is an open-source lightweight session bus that lets coding agents on different machines join the same real-time session; it uses the Apache-2.0 license, its project address is skepagent.com, and the repository is on GitHub (Guxiaodong941005/skepAgent).
Skep's current version is v0.1.15, and it is installed via `npm i -g @skepagent/skep`.
Skep uses a master-peer topology, with one machine as the master and other machines joining using a short code and host, with no account registration and no cloud relay.
Skep does not wrap or proxy local CLI agents such as Claude Code, Codex or Pi; agents still run as local programs, and Skep is only responsible for session-level message passing.
Skep explicitly promises not to collect or upload API keys, because its architecture has no central server that could receive them.
Skep is designed for trusted network environments, assuming devices are mutually trusted; it is suitable for deployment between machines the user controls, and not suitable for cross-organizational collaboration scenarios.
Skep uses a master-peer topology rather than decentralized P2P because multi-agent collaboration requires an authoritative node to determine the session's initial state and participant list.
Skep's potential security risks include: the short code being guessed by other devices on the LAN, the entire session being affected if the master node is compromised, and plaintext messages being sniffed on untrusted networks.
Using Skep directly on the open internet without network-layer encryption is not necessarily lower-risk than handing data to a cloud platform; it merely changes the risk type from trusting a service provider to trusting your own network configuration.
All Facts (8)
Skep is an open-source lightweight session bus that lets coding agents on different machines join the same real-time session; it uses the Apache-2.0 license, its project address is skepagent.com, and the repository is on GitHub (Guxiaodong941005/skepAgent).
50%UnverifiedSkep uses a master-peer topology, with one machine as the master and other machines joining using a short code and host, with no account registration and no cloud relay.
50%UnverifiedSkep does not wrap or proxy local CLI agents such as Claude Code, Codex or Pi; agents still run as local programs, and Skep is only responsible for session-level message passing.
50%UnverifiedSkep explicitly promises not to collect or upload API keys, because its architecture has no central server that could receive them.
50%UnverifiedSkep is designed for trusted network environments, assuming devices are mutually trusted; it is suitable for deployment between machines the user controls, and not suitable for cross-organizational collaboration scenarios.
50%UnverifiedSkep uses a master-peer topology rather than decentralized P2P because multi-agent collaboration requires an authoritative node to determine the session's initial state and participant list.
50%UnverifiedSkep's potential security risks include: the short code being guessed by other devices on the LAN, the entire session being affected if the master node is compromised, and plaintext messages being sniffed on untrusted networks.
50%UnverifiedUsing Skep directly on the open internet without network-layer encryption is not necessarily lower-risk than handing data to a cloud platform; it merely changes the risk type from trusting a service provider to trusting your own network configuration.
50%