alternate transports (not TCP) /protocols (not HTTP)

[aktau]

At work there is infrastructure that I think is a good fit for integrating with codecompanion, but it does not have a HTTP interface. its communication is done over stdin/stdout (not TCP) and JSON-RPC (not HTTP). In effect, it's an LSP extension.

From what I can gather, by reading the code and docs, this isn't supported (endpoint/url is required).

I could build a HTTP server wrapper using sticks and ston^W Neovim's builtin luv, but it would be more reliable, easier to code and more intellegible if my provider could just offer some functions to request/respond data. Just wondering if you've considered this.

[olimorris]

I don't have any interest in adding this level of complexity directly into the plugin unfortunately. You could overwrite codecompanion.http with your own library to intercept this however.

[aktau]

That's reasonable, and the suggestion is another decent workaround (on top of the shim HTTP server I was consdering). Thanks for considering it, and your work on the plugin itself.