Cligate

CliGate

English | 中文

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

- One local dashboard for a resident private assistant and unified model routing
- Assistant tasks with memory, approvals, follow-ups, scheduled work, channels, and tool execution
- Account pools, API keys, local runtimes, app routing, and model mapping in one proxy layer
- Channels for Telegram, Feishu, and DingTalk workflows
- Local-first deployment without a hosted relay

What It Includes

Assistant

- Dashboard chat and Assistant Tasks for personal task execution
- A persistent assistant agent with task records, memory, policies, approvals, and resumable executions
- Tool execution through skills, MCP, shell/file tools, scheduled tasks, channels, and optional desktop automation
- Optional delegation to Codex / Claude Code runtime sessions when a task needs an external coding agent
- Telegram, Feishu, and DingTalk channel workflows

Model Proxy

- Anthropic Messages, OpenAI Chat Completions, OpenAI Responses, Codex, and Gemini-compatible endpoints
- One-click configuration…