Zum Hauptinhalt springen
Echtzeit-Radar & Feeds
Alle RSS Feeds ➔
👥 Community & Social
Windows Tipps & SecurityGrafikkarte vor Überhitzung schützen: So geht’s(25.09.2026 um 08:00 Uhr)
••••••••••
Windows Tipps & SecurityGrafikkarte vor Überhitzung schützen: So geht’s(25.09.2026 um 08:00 Uhr)
••••••••••
Intelligence View
⚡ tsecurity.de Intelligence

I Stopped Paying for AI CLI Chaos: This Local Gateway Makes Claude Code, Codex, and Gemini Work as One

If you are juggling Claude Code, Codex CLI, Gemini CLI, and random API keys across different providers, the setup gets ugly fast. Different protocols. Different auth flows. Different config files. Different model names. Different rate…

0
↗ Quelle (dev.to)
Reagiere als Erste:r — dein Feedback zählt!

If you are juggling Claude Code, Codex CLI, Gemini CLI, and random API keys across different providers, the setup gets ugly fast.



Different protocols. Different auth flows. Different config files. Different model names. Different rate limits.



So I built CliGate: a local multi-protocol AI gateway that sits on localhost and turns that mess into one controllable entry point.



Instead of wiring every tool separately, you point them at CliGate once and get:




  • multi-account pooling

  • API key failover

  • protocol translation

  • app-level routing

  • free-model fallback

  • a visual dashboard for everything






What CliGate actually does



CliGate is an open-source local proxy for AI coding tools and model APIs.



It currently supports:





  • Claude Code via Anthropic Messages API


  • Codex CLI via OpenAI Responses API, Chat Completions, and the Codex internal endpoint


  • Gemini CLI via Gemini API compatibility


  • OpenClaw via provider injection



That means one local service can sit between your tools and multiple upstream providers like OpenAI, Anthropic, Google Gemini, Vertex AI, and even free-model routes.






The real problem it solves



Most people do not have one clean AI stack.



They have:




  • a few accounts with different limits

  • some paid API keys

  • a CLI tool that only speaks one protocol

  • another tool that expects a completely different endpoint

  • no decent visibility into cost, usage, or failures



CliGate fixes that by separating the client protocol from the upstream provider.



Your tool can keep speaking the protocol it expects, while CliGate decides where the request should actually go.






The killer features






1. One gateway for multiple AI coding tools



You can run Claude Code, Codex CLI, Gemini CLI, and OpenClaw through the same local server.



No more maintaining a fragile pile of per-tool environment variables and scattered config files.






2. Account pools, not just API keys



CliGate is not just another API proxy.



It can manage:




  • ChatGPT account pools

  • Claude account pools

  • Antigravity accounts

  • provider API key pools



It supports OAuth login, token refresh, rotation strategies, quota tracking, and per-account management from the dashboard.






3. Smart routing instead of manual switching



You can choose:




  • account-pool-first

  • API-key-first

  • automatic routing

  • manual app assignment



So Claude Code can use one credential source, Codex can use another, and fallback behavior stays under your control.






4. Free-model routing for cheap or zero-cost workflows



One of my favorite parts is the ability to route lightweight requests such as claude-haiku to free models through Kilo AI.



That gives you a practical low-cost path for lightweight coding, testing, and background tasks without burning premium quota for everything.






5. A real dashboard instead of blind debugging



CliGate ships with a web UI where you can manage:




  • accounts

  • API keys

  • model mapping

  • per-app routing

  • request logs

  • usage and cost stats

  • pricing overrides

  • local tool installation and one-click configuration



This matters because most proxy tools become painful the moment you need to debug token expiry, failed routing, or mismatched models.






Why I think the protocol translation matters



This is the part that makes CliGate more than a credential switcher.



It exposes compatible endpoints for:




  • POST /v1/messages

  • POST /v1/chat/completions

  • POST /v1/responses

  • POST /backend-api/codex/responses

  • POST /v1beta/models/*



So tools that were never designed to share the same backend can still be managed through one local layer.



That unlocks a cleaner workflow:




  1. Keep your preferred client.

  2. Route it however you want.

  3. Change upstream providers without rebuilding your whole local setup.






Local-first is the point



CliGate runs on localhost.



That means:




  • no third-party relay server

  • no hosted control plane

  • no forced telemetry layer

  • direct connections to official upstream APIs



For people who care about privacy, local control, or just not introducing another external dependency into their dev workflow, this is the right architecture.






Quick start



You can start it with:




npx cligate@latest start






Or install globally:




npm install -g cligate
cligate start






Then open:




http://localhost:8081






From there you can add accounts or API keys, map models, and configure your CLI tools to hit the local gateway.






Who this is for



CliGate is especially useful if you:




  • use more than one AI coding CLI

  • switch between Claude, OpenAI, Gemini, and other providers

  • want fallback behavior when limits or keys fail

  • want usage visibility across accounts and models

  • want a local control plane instead of ad hoc shell config






Repo



GitHub: https://github.com/codeking-ai/cligate



If you are building serious local AI coding workflows, this project is designed to remove a surprising amount of friction.



It is the difference between “a pile of disconnected AI tools” and “one local gateway that actually behaves like infrastructure.”

1. Sofort-Triage & Abwehrmaßnahmen

SOC Incident Playbook: Remote Code Execution (RCE) Defense
Syntax validiert (0 Fehler)
title: Detect Exploitation - I Stopped Paying for AI CLI Chaos: This Local Gateway Makes Claude Code, Codex, and Gemini Work as One
id: f0525b6d-5f38-4f9a-8638-b168ce5a250d
status: experimental
description: Automatisch generierte SIEM-Erkennungsregel basierend auf CTI Intelligence
references:
  - https://tsecurity.de/
author: iShareStuff CTI Automated Detection Engine
date: 2026-09-25
logsource:
  category: network_connection
  product: any
detection:
  selection:
      CommandLine|contains:
        - 'exploit'
  condition: selection
falsepositives:
  - Legitime administrative Zugriffe oder Penetrationstests
level: high
tags:
  - attack.initial_access
Syntax validiert (0 Fehler)
rule CTI_Threat_Indicator {
    meta:
        author = "iShareStuff CTI Automated Detection Engine"
        date = "2026-09-25"
        description = "YARA Signature for "
    strings:
        $str = "I Stopped Paying for AI CLI Ch" ascii wide
    condition:
        any of them
}
Syntax validiert (0 Fehler)
index=security sourcetype IN ("cisco:asa", "pan:traffic", "zeek_conn", "suricata", "WinEventLog:Security")
("I Stopped Paying for AI CLI Chaos This L")
| stats count earliest(_time) as first_seen latest(_time) as last_seen by src_ip, dest_ip, dest_host, signature
| eval first_seen=strftime(first_seen, "%Y-%m-%d %H:%M:%S"), last_seen=strftime(last_seen, "%Y-%m-%d %H:%M:%S")
| sort - count
Syntax validiert (0 Fehler)
message: "*I Stopped Paying for AI CLI Chaos This L*"
Syntax validiert (0 Fehler)
CommonSecurityLog
| where Message has "I Stopped Paying for AI CLI Chaos This L"
| summarize EventCount = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by SourceIP, DestinationIP, DestinationPort, Activity
| extend DetectionRule = "iShareStuff-CTI-Compiled"
| sort by EventCount desc

2. Cyber Threat Intelligence & Forensik

CTI Threat Relationship Graph2 Knoten / 1 Relationen
CVE / Incident Software MITRE ATT&CK CWE Weakness IoC
🎯
MITRE ATT&CK Matrix Navigator 14 Taktiken
Reconnaissance
-
Resource Development
-
Initial Access
Execution
Persistence
-
Privilege Escalation
Defense Evasion
Credential Access
-
Discovery
-
Lateral Movement
-
Collection
-
Command and Control
Exfiltration
-
Impact
tsecurity.de Cognitive Threat RAG
Fokus-Vektor:

Kognitive Analyse für identifizierte Bedrohung: Erhöhte Bedrohungslage im Bereich I Stopped Paying for AI CLI Chaos: This .... Basierend auf 368k Vektor-Korrelationen werden sofortige Isolationsmaßnahmen für betroffene Endpunkte empfohlen.

🛡️ Angriffsfläche & Exposure

Netzwerk/Remote-Zugriff ohne Vorauthentifizierung möglich.

⚡ Empfohlene Sofortmaßnahmen
  • 1. Perimeter-Inspektion: Relevante Portfreigaben und exponierte Endpunkte unverzüglich scannen.
  • 2. Patch-Applikation: Hersteller-Hotfix einspielen oder betroffene Daemons in isolierte DMZ-Segmente überführen.
  • 3. Telemetrie & EDR-Alerts: Prozessaufrufe und Child-Processes auf anomale Shell-Spawns überwachen.
🔗 Semantisch verwandte Zero-Days MariaDB 11.7 VEC
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten I Stopped Paying for AI CLI Chaos: This Local Gateway Makes Claude Code, Codex, and Gemini Work as One

Thematisch verwandte Begriffe: Stopped, Paying, Chaos, This · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Zum Aktualisieren ziehen
ZERO-DAY CVE-2026-97898 | Insecure Direct Object Reference / missing object-level authorization in…
Advisory →
tsecurity.de Icon
Offline-Lesen, Eilmeldungen & 0ms Ladezeit

Installiere tsecurity.de direkt auf deinen Home-Bildschirm für das ultimative Vollbild-Magazinerlebnis ohne Browser-Leisten.

Nächster Beitrag