Editor Code Assistant protocol #57
Closed
bombaywalla
started this conversation in
General
Replies: 1 comment
-
@bombaywalla thanks for reaching out. However, I think that ECA is an agent of it's own that happens to work with multiple providers. If they wanted, they could shift their communication with the editors to go over ACP, but it seems to be doing a lot of work that we would classify as an agent of their own. So I don't think there is a concern of overlap here. Thanks! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Just inquiring whether you folks are aware of the Editor Code Assistant (ECA) project and its underlying protocol?
On a quick glance it seems the protocols are at least semantically similar and the projects seem to have similar goals.
It would be a pity to have duplicated efforts.
Gauging whether there is any interest in working together on the protocol in order to have a single interoperable standard specification.
I'm not speaking for ECA in any official capacity, just as an interested user.
The project is here
Beta Was this translation helpful? Give feedback.
All reactions