codeking-ai/cligate

90 stars · Last commit 2026-06-07

Private AI assistant, AI agent, and unified model proxy for Claude Code, Codex CLI, Gemini CLI & OpenClaw. Skills, MCP, tools, channels, tasks,model routing, accounts, keys, logs, dashboard.

README preview

# CliGate

![CliGate Dashboard](./images/dashboard.png)

[![AGPL-3.0 License](https://img.shields.io/badge/License-AGPL--3.0-blue.svg)](https://www.gnu.org/licenses/agpl-3.0)
[![Node.js Version](https://img.shields.io/badge/Node.js-24%2B-blue.svg)](https://nodejs.org/)
[![npm Version](https://img.shields.io/npm/v/cligate)](https://www.npmjs.com/package/cligate)
[![GitHub stars](https://img.shields.io/github/stars/codeking-ai/cligate?style=social)](https://github.com/codeking-ai/cligate)

**[English](./README.md) | [中文](./README_CN.md)**

CliGate is a local AI control plane built around two core capabilities:

- **Assistant**: a resident private assistant that stays available in the background, understands user tasks, remembers context, uses tools, schedules work, operates channels, and can execute actions through MCP, skills, desktop automation, shell/file tools, or delegated runtimes.
- **Model Proxy**: one local API and model-routing layer for Claude Code, Codex CLI, Gemini CLI, OpenClaw, and API-compatible clients, with unified accounts, API keys, model mapping, logs, usage, and cost visibility.

It keeps both layers local-first on `localhost`: the assistant acts like a personal operator for real tasks, while the proxy owns provider access, routing, credentials, unified model names, and observability.

## Why CliGate

View full repository on GitHub →