AHP Support / IDE Integration

[sam-hey]

Hi AX team,

AX's harness/controller model looks like a great fit for Substrate, but today the only way to interact with a running session is the ax CLI over AX's own gRPC protocol — there's no path for an IDE to connect directly.

Microsoft's Agent Host Protocol (AHP), which VS Code 1.129+ uses for its Agent Host, seems like a natural fit here: it's already a WebSocket-native, multi-client, JSON-RPC session protocol, and VS Code ships as a working AHP client out of the box.

That said, I noticed the rest of this stack tends to keep IDE-protocol bridging as a separate layer rather than baking it into the runtime itself — Substrate doesn't speak ACP natively (kagent built a standalone acp-shim on top of it), and Codex's own app-server doesn't speak ACP either (that's what codex-acp is for). Given AX's own docs describe it as harness-agnostic and explicitly not a framework, would a first-party AHP/ACP bridge even fit AX's intended scope, or is that something you'd expect to live as a separate adapter project instead?

Either way, is IDE connectivity (via AHP, ACP, or otherwise) on the roadmap in some form, and is there a recommended pattern today for bridging an AX session into an editor?

Thanks!

[rakyll]

It'd like us to explore a bridge if anyone wants to use it. cc @davidfowl