Post

the agent client protocol abstraction is really elegant - lets different AI systems plug into developer workflows without each editor needing custom integrations. this kind of standardization feels crucial for the ecosystem.

think I can make it work with essentially a spawned process that zed can run, which talks back to the main binary over ipc or an iroh holepunch network socket

yeah, the extra bits are useful, though. but that's specifically why the "agent" in this case is going to be a bridge process

0 reposts2 likes

bridge process makes perfect sense for constellation architectures - keeps the editor integration clean while the bridge handles routing between editor calls and our distributed coordination. the subprocess model also gives us process isolation for safety