OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Agent Frameworks

Cligate

Cligate is an AGPL-3.0 JavaScript framework that provides a local AI assistant and unified model proxy for AI coding clients, agent workflows and API-compatible applications.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Cligate — OpenViST project profile in Agent Frameworks.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Cligate when a local deployment needs both a task-oriented AI assistant and a shared routing layer for several model clients or providers.

Who it is for

  • People using Claude Code, Codex CLI, Gemini CLI or OpenClaw who want a local shared model-access layer.
  • Operators managing provider accounts, API keys, model routes, logs and local runtimes.
  • Users building assistant workflows around MCP, skills, tools, channels and scheduled tasks.

Documented uses

  • Route requests from multiple AI coding clients through one local proxy.
  • Map applications and model names to configured provider access.
  • Manage accounts, API keys, routing priority, logs, usage and pricing views.
  • Run assistant tasks with memory, approvals, tools, channels and scheduled work.
  • Connect MCP, skills, shell or file tools and optional delegated coding-agent sessions.
Before you choose

Requirements & limits

The documented setup uses a local npm installation, global npm installation or desktop release package. The README requires Node.js 24 or later for the npm path and describes access to a local dashboard at http://localhost:8081. At least one working account, API key or local model runtime is required for the model-access path.

  • Choose the assistant path if you need memory, approvals, follow-ups, scheduled tasks, channels or tool execution.
  • Choose the proxy path if your main requirement is shared model access for multiple clients or API-compatible applications.
  • Check provider and client configuration needs before adoption: the project documents separate settings for Claude Code and Codex CLI, with dashboard configuration for Gemini CLI and OpenClaw.
  • The framework is local-first and includes account, API-key, routing, model-mapping and log-management functions in the proxy layer.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Start Cligate and configure a first local proxy

Set up the local service, add a credential, and prepare a supported client connection.

Before you start

  • Node.js 24 or later for the npm installation path.
  • A working account, provider API key, or local model runtime.
  • Claude Code, Codex CLI, Gemini CLI, OpenClaw, or another API-compatible client for the proxy path.

Steps

  1. Start Cligate with the documented npm command, install it globally, or open a platform release package.

  2. Open the local dashboard at http://localhost:8081.

  3. Add a credential through Accounts, API Keys, or Local Models.

  4. Use the dashboard configuration path for Gemini CLI or OpenClaw, or apply the documented Claude Code or Codex CLI settings.

Expected outcome

A local Cligate service is started with a configured credential and a documented client connection path.

Guide limitations

  • The guide documents setup and configuration paths, but does not establish that a particular provider credential or client request will work in every environment.
  • Provider access still depends on the configured account, API key, or local runtime.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
3 October 2026
Original website title
codeking-ai/cligate · Official homepage title · retained in its source language
How we review sourcesSuggest a correction