API documentation

[notramo]

Is it possible to provide API documentation that would make possible to develop community-supported plugins for less-popular editors?

[pqn]

We have some internal documentation for this that we can consider open sourcing, cc @fortenforge. For now, we have a few different open sourced implementations of the API that hopefully can serve as examples.

First party:

• https://github.com/Exafunction/codeium-chrome
• https://github.com/Exafunction/codeium.vim
• https://github.com/Exafunction/codeium.el

Community:

• https://github.com/intitni/CodeiumForXcode

[notramo]

@pqn Why is the server executable required? Does it access other files in the project, or provide other statistics? Or it would be possible to write a plugin for Kakoune which would talk directly to the Codeium server API, without running a local process?

[notramo]

We have some internal documentation for this that we can consider open sourcing,

@pqn if it's not something that would give the competition an advantage, then it's definitely worth open sourcing. It would open endless possibilities. For example, I want to create a Codeium plugin for my favourite editor (Kakoune).

[pqn]

@pqn Why is the server executable required? Does it access other files in the project, or provide other statistics? Or it would be possible to write a plugin for Kakoune which would talk directly to the Codeium server API, without running a local process?

Yes, it access other files and maintains state among other things.

@pqn if it's not something that would give the competition an advantage, then it's definitely worth open sourcing. It would open endless possibilities. For example, I want to create a Codeium plugin for my favourite editor (Kakoune).

It's just a matter of prioritization right now, I believe we intend to do this at some point.

[hovancik]

+1 for this. I would love to see Codeium for Pulsar.