Opening up GitLab Duo Chat Completions API

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

A few customers have been asking to make GitLab Duo Chat Completions API a public API.

They want to use it in their automations to generation content, such as release notes or git commit messages.

Whether Duo Chat Completions is the right API for that is not clear to me (@tlinz) for the following reasons. Maybe this calls for a different solution than making exactly this API public.

1. After all it implements a chat, but the use cases that customers mention are unrelated to a chat.
2. It is for interaction with human users and output contains information useful for humans such as "Source: ..." but maybe unwanted in a commit message or other auto-generated content.
3. Also, it is likely that the automation that they want to build has all the context needed for the generation of content, hence there is no benefit of the agent that can fetch additional context.
4. Finally, the API is only used for testing Duo Chat and not intended for external use.
5. Lastly, the licensing model of Duo Chat is a per-user seat license. This does not seem compatible with automation usage that is typically unrelated to a user.