The latest articles on DEV Community by SkepAgent (@skepagent). https://dev.to/skepagent https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4184742%2Ff7fe2af1-7999-4654-939c-9acf92bf4a58.png https://dev.to/skepagent en SkepAgent Wed, 14 Oct 2026 13:05:59 +0000 https://dev.to/skepagent/skep-cross-device-live-sessions-for-local-coding-agents-2c1e https://dev.to/skepagent/skep-cross-device-live-sessions-for-local-coding-agents-2c1e <p>I run coding agents on more than one machine. Claude Code on my laptop, another agent on a VPS, sometimes Pi on a Mac. They're all good at their jobs, but they can't talk to each other — and the options I found either wanted my API keys uploaded to someone's cloud, or amounted to SSH + tmux duct tape.</p> <p>So I built Skep: a thin session bus that lets coding agents on different machines join one live session. It's open source (Apache-2.0).</p> <h2> The problem </h2> <ul> <li>Agents are per-machine. Context, plans, and intent stay locked on the device where the agent runs.</li> <li>Most multi-agent setups centralize: your keys and your code flow through a third-party server.</li> <li>I wanted agents to share intent with each other, keys to stay on each device, and to keep running the local CLIs I already trust.</li> </ul> <h2> What Skep does </h2> <ul> <li>One machine becomes the <strong>master</strong>; other machines <strong>join</strong> with a short code + host. No accounts, no cloud relay.</li> <li>Peers run <strong>your own local</strong> Claude Code / Codex / Pi. Skep doesn't wrap them or proxy your prompts through a server.</li> <li> <strong>Keys stay on each device.</strong> Skep never harvests or uploads API keys — there's no central server for them to go to.</li> <li>Install: <code>npm i -g @skepagent/skep</code> (v0.1.15)</li> </ul> <h2> Why not a cloud platform? </h2> <p>Most "multi-agent collaboration" products hold your session state, your keys, and the billing meter on their servers. Convenient, but a bigger trust surface.</p> <p>Skep inverts it: the session is just a bus between machines you already own, meant for trusted devices on your own network. Less magic, fewer places your secrets can leak.</p> <h2> Try it </h2> <ul> <li>Site: <a href="https://skepagent.com" rel="noopener noreferrer">https://skepagent.com</a> </li> <li>Repo: <a href="https://github.com/Guxiaodong941005/skepAgent" rel="noopener noreferrer">https://github.com/Guxiaodong941005/skepAgent</a> </li> <li><code>npm i -g @skepagent/skep</code></li> </ul> <p>I'm the author — happy to answer protocol / threat-model questions in the comments. If you run agents across machines, I'd love to hear how you'd use this.</p> ai opensource showdev cli