What is the System One plugin for CLIProxyAPI?

A Go plugin that adds System One decision nodes to CLIProxyAPI. It takes a {model, state, questions} decision request, routes it to the node chosen by the model prefix, and returns the node's JSON answer unchanged.

What can act as a System One node?

Any System One-compatible server, per the README: a local model server such as Winnow 12B, or a hosted lane like OpenCode, OpenRouter or v1m.

How do I install the System One plugin?

Either install System One from the management panel's plugin store, or download systemone_ _ _ .zip from Releases and extract the .so, .dylib or .dll into the plugins directory. Building from source needs Go 1.26+ and a C compiler, though the digest truncates the build command.

What does the plugin's management UI provide?

A System One page lists nodes and offers Check with latency, fetching models from a node, and an example builder that sends test decisions. Configured models are exposed through GET /v1/models as prefix/model.

Why does the plugin not support streaming?

Because System One decisions are a single JSON response rather than a token stream, streaming is not supported; the README lists this limitation directly.

How are API keys handled for multiple nodes?

Nodes accept several API keys with round-robin selection and fallback, plus optional extra headers and a per-node proxy. The digest does not document key storage or rotation policies.

Who maintains the plugin and what license does it use?

The ducdao98z GitHub account, under MIT, with 2 stars; created and last pushed 2026-10-09. It requires CLIProxyAPI v8 with plugins enabled.

Jev directory

CommunityJev Integrations & Adapters

System One plugin for CLIProxyAPI

A CLIProxyAPI plugin that routes System One decision requests to any compatible node, a local model server such as Winnow 12B or hosted lanes like OpenCode, OpenRouter and v1m, chosen by model prefix, with a management UI.

See highlights Open github.com

Stars: 2
Language: Go
License: MIT
Reading time: 2 min
Published by: Community
Author: ducdao98z
Last verified: Oct 2026

ducdao98z/cpa-plugin-systemone

User repository on GitHub

View on GitHub

CLIProxyAPI plugin: route System One decision requests to any System One node (Winnow, OpenCode, OpenRouter, v1m) with a management UI

Forks: 0
Last pushed: Updated Oct 2026

Repo stats from the GitHub API, cached Oct 2026.

Tagscommunity github gateway go system-one

Works forJev for Routing

Used inJev for Software & DevTools

Languages: Go
Platforms: API
Capabilities: Open sourceSelf-hostedRequires API key

Highlights

Adds System One decision nodes to CLIProxyAPI: a {model, state, questions} request goes to the node chosen by model prefix.
Any System One-compatible server can be a node: a local model server such as Winnow 12B, or hosted lanes like OpenCode, OpenRouter and v1m.
Nodes are added by URL with multiple API keys (round-robin with fallback), extra headers and a per-node proxy.
Configured models appear in GET /v1/models as prefix/model; a management page offers node checks with latency and an example builder.
Requires CLIProxyAPI v8 with plugins enabled; streaming is not supported because decisions are a single JSON response.

Watch out

README and GitHub metadata reviewed 2026-10-17; the digest truncates the from-source build command mid-flag, so the exact build invocation and the rest of the install steps are not evidenced here.

Questions about this entry

Short answers drawn from the linked project or page.

Reactions & coverage

Posts, threads, and videos about this entry from around the web.

X: Jev 1.14 is now on OpenRouter

X: Jev lands on the Vercel AI Gateway

X: Jev as an LLM guardrail inside Agentgateway

YouTube: Greg Isenberg and Ryan Vogel on the businesses Jev unlocks, and a path in through the Vercel AI Gateway.

From the Jev guides

Original write-ups on what this entry is for.

Decision gates in agent frameworks: what each integration ships

Oct 16, 2026

How Pydantic AI, Mastra, TanStack AI, DSPy, Spring AI, and LiteLLM expose Jev: where the typed decision sits in the loop, what each integration returns, and which big frameworks are only adjacent.

Jev Integrations & Adapters#agents#frameworks#integrations

Read article

From the Jev AI model community

Posts from builders shipping with Jev right now.

Follow @typesafeai