Reuse, don’t re-authenticate.
The reference plugin reads the login created by the official Grok CLI. CCBUD receives login metadata, not its access or refresh tokens.
CCBUD now hosts local sidecar plugins. A plugin can reuse a coding agent’s existing CLI login, speak a standard protocol, and appear as an ordinary service. The Grok reference plugin needs an eligible Grok subscription but no separate API key or per-token API billing; xAI limits and terms still apply.
CCBUD keeps the host generic. It translates client protocols and manages the process; each plugin handles only its vendor’s login and API shape.
The reference plugin reads the login created by the official Grok CLI. CCBUD receives login metadata, not its access or refresh tokens.
CCBUD selects the platform binary, assigns a free localhost port, waits for health, and auto-starts the active service next launch.
Claude and Codex get family-aware model lists and primary/fast tier mapping through the same gateway.
The host owns the repetitive work without hiding it. Building, starting, health-check, stopped, and failed states stay visible and under your control.
A Git source is cloned and runs its manifest build command with your user permissions. A local folder installs an already built plugin.
Enable starts the process and routes only after /healthz returns 200. This checks process readiness—not login or vendor availability.
Installation adds the service; Enable only starts or stops its sidecar. Status, updates, and declared actions stay in Plugins.
Grok reference plugin: sign in with the official Grok CLI first. The plugin reads and may cache its OAuth tokens; refresh can require signing in again. Your Grok plan, quotas, and xAI terms still apply.
Git import needs Git and the plugin’s declared build toolchain; Grok Build currently needs Go and make.
PR #27 tested both client families. Below, a Codex → Grok capture is paired with a sanitized Claude-family gateway view.
Drop another compatible plugin into ~/.ccbud/plugins and the host needs no vendor-specific code. The manifest drives models, protocol, lifecycle, icon, updates, and even buttons or forms.
ManifestIdentity, binaries, models, protocol, source, and declarative UI.
Control planeHealth, status, auth state, and plugin-defined actions.
Data planeA standard inference endpoint and the plugin’s model catalog.
{
"spec": "ccbud-plugin/1",
"id": "grok-build",
"runtime": {
"args": ["serve", "--port", "{port}"]
},
"endpoint": {
"protocol": "openai-responses",
"healthPath": "/healthz"
},
"modelMapping": {
"primary": "grok-4.5",
"light": "grok-build"
},
"ui": {
"actions": [/* link · call · form */]
}
}
127.0.0.1:{port}
The new plugin layer sits on top of the routing, monitoring, history, and reversible configuration workflow already built into CCBUD.
Follow request streams, latency, model rewrites, translated bodies, headers, gateway events, and upstream errors.
Manage presets and custom endpoints, test connections, map stable aliases, and change the active service without shell edits.
Search Claude Code projects and Codex sessions, inspect tool calls and diffs, then export readable JSONL or HTML.
The gateway binds to 127.0.0.1, but loopback is not a sandbox. Config edits are reversible; CCBUD and installed plugin code can be audited, while the selected vendor remains external.
Download CCBUD for macOS, Windows, or Linux, then add the Grok reference plugin from Git—or build the next adapter yourself.
brew install --cask ccbud/tap/ccbud