I built LazyGravity to solve a personal itch: wanting to trigger real coding tasks when I am away from my desk, using an interface I already have (Discord on my phone).
It's a local-first bridge that forwards messages to my desktop AI coding setup, then reports results back. Instead of exposing my dev machine through public ports or relying on cloud relays, it uses Chrome DevTools Protocol (WebSocket) to drive the editor UI locally and securely.
It's a local-first bridge that forwards messages to my desktop AI coding setup, then reports results back. Instead of exposing my dev machine through public ports or relying on cloud relays, it uses Chrome DevTools Protocol (WebSocket) to drive the editor UI locally and securely.
I posted a short video demonstrating how it handles UI generation and hot-reloading here: https://x.com/m_web3/status/2027743280923086968
Repo: https://github.com/tokyoweb3/LazyGravity
I would love to hear your thoughts on this architecture, especially regarding local CDP security boundaries.