I’ve been exploring ways to interact with local AI coding agents (like Antigravity) while away from my desk. Traditional remote desktop solutions are too heavy for quick mobile fixes, and exposing local ports to the internet is a security nightmare.

I ended up building a bridge that connects the editor’s UI directly to Discord, and I thought the technical approach might be interesting to those working with Electron or AI agent orchestration.

**1. Driving the UI via Chrome DevTools Protocol (CDP)** Instead of hacking a private API or injecting custom scripts into the IDE (which can be brittle or lead to account bans in some cases), I used CDP over WebSockets.

* **The Hack:** By launching the IDE with `--remote-debugging-port`, I can evaluate JS in the context of the editor's DOM.
* **Observation:** I implemented a mutation observer-like logic to poll the AI agent's status/plan and pipe that back as rich Discord embeds. This allows for real-time progress monitoring without the IDE having any native "remote" feature.

**2. Security: The "No-NAT" Approach** The biggest challenge was security. How do you control a local machine from a phone without Port Forwarding or a Cloud VPN?

* **Architecture:** The bridge runs as a local Node.js process that acts as a Discord Gateway client.
* **Result:** This creates an outbound-only connection. The local machine is never "listening" for incoming internet traffic; it only responds to events from the Discord WebSocket.
* **Access Control:** I implemented a strict whitelist at the bot logic level, ensuring only specific Discord User IDs can trigger the `Runtime.evaluate` calls.

**3. State Management in Async AI Tasks** Discord is inherently synchronous (message -> reply), but AI coding tasks are long-running and asynchronous.

* I had to build an "event-to-message" mapper that keeps track of the AI’s current thinking/execution phase and updates the Discord UI accordingly.
* Added a `/screenshot` command that uses CDP’s `Page.captureScreenshot` to provide a visual sanity check from the phone.

**Lessons Learned:**

* CDP is surprisingly powerful for "headless" control of desktop apps if they are Electron-based.
* The latency of Discord's API is negligible compared to the time AI takes to "plan" a refactor, making it a viable UI for long-running tasks.

I’ve open-sourced the prototype (LazyGravity) to get some feedback on the security model and the CDP implementation. If anyone has experience with more stable ways to IPC with Electron from an external process, I’d love to hear your thoughts.

**Repo for those interested in the architecture:** [https://github.com/tokyoweb3/LazyGravity](https://github.com/tokyoweb3/LazyGravity)

Reverse-driving an Electron-based AI IDE via CDP: Implementing a secure, "local-first" mobile bridge