Skip to main content

​
GitLab Duo Provider

CCS supports GitLab Duo as a CLIProxy OAuth provider with two supported auth paths:
  • browser OAuth
  • personal-access-token login (--gitlab-token-login)

​
Quick Start

# Standard GitLab.com OAuth
ccs gitlab --auth

# Use a GitLab Personal Access Token instead of browser OAuth
ccs gitlab --auth --gitlab-token-login

# Target a self-hosted GitLab instance
ccs gitlab --auth --gitlab-url https://gitlab.example.com

# Run through the provider after auth
ccs gitlab "summarize this merge request"

​
Backend Requirement

GitLab Duo is a plus-only provider. 
cliproxy:
  backend: plus

​
Authentication Details

PathNotes
Browser OAuthlocal callback flow on port 17171
PAT loginuse --gitlab-token-login or legacy alias --token-login
Self-hosted GitLabpass --gitlab-url <url>; CCS switches to paste-callback mode when needed

​
Useful Commands

ccs gitlab --auth
ccs gitlab --auth --gitlab-token-login
ccs gitlab --auth --gitlab-url https://gitlab.example.com
ccs gitlab --accounts
ccs gitlab --use <account>
ccs gitlab --config
ccs gitlab --logout

​
Config And Storage

PathPurpose
~/.ccs/cliproxy/auth/shared OAuth token directory
~/.ccs/gitlab.settings.jsonprovider settings when a local settings file is used

​
Notes

  • Token refresh is delegated to CLIProxy
  • model/config surfaces depend on what the upstream CLIProxy management API exposes for the provider at runtime