CodeBuddy Provider

CCS supports CodeBuddy (Tencent) as a CLIProxy OAuth provider.

Quick Start

ccs codebuddy --auth
ccs codebuddy --accounts
ccs codebuddy --config
ccs codebuddy "inspect this implementation"

Authentication Model

CodeBuddy currently uses a browser-driven polling flow through CLIProxyAPIPlus:

no local callback port is required
CCS waits for upstream auth completion
token refresh is delegated to CLIProxy

Backend Requirement

CodeBuddy is a plus-only provider.

cliproxy:
  backend: plus

Config And Storage

Path	Purpose
`~/.ccs/cliproxy/auth/`	shared OAuth token directory
`~/.ccs/codebuddy.settings.json`	provider settings when a local settings file is used

Current Scope

CCS documents CodeBuddy today as an auth and routing provider surface. As with Cursor, it does not currently participate in the local static model-catalog sync path used by the older catalog-backed provider set.

Provider Overview
CLIProxy API

GitLab Duo Provider Kilo AI Provider

Getting Started

Providers

Features

Tutorials

CodeBuddy Provider

CodeBuddy Provider

Quick Start

Authentication Model

Backend Requirement

Config And Storage

Current Scope

​CodeBuddy Provider

​Quick Start

​Authentication Model

​Backend Requirement

​Config And Storage

​Current Scope

​Related

CodeBuddy Provider

Quick Start

Authentication Model

Backend Requirement

Config And Storage

Current Scope

Related