AgentStack
MCP verified MIT Self-run

Hermes Kimi Code Bypass

mcp-lckx777-hermes-kimi-code-bypass · by lckx777

Kimi Code OAuth subscription bypass for Hermes Agent — zero pay-per-token, zero ToS risk. Companion to kristianvast/hermes-claude-auth.

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add mcp-lckx777-hermes-kimi-code-bypass

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets Used
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README — it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/mcp-lckx777-hermes-kimi-code-bypass)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude DesktopCursorWindsurf

Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Hermes Kimi Code Bypass? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

hermes-kimi-code-bypass

Hermes Agent provider plugin that reuses Kimi Code OAuth subscription credentials (managed by the official kimi CLI) to route inference through api.kimi.com/coding/v1 — zero pay-per-token, zero ToS violation, zero anti-bot dependency.

Companion to kristianvast/hermes-claude-auth (Anthropic bypass Q8) and the openai-codex bundled provider (ChatGPT subscription OAuth). Together they enable a fully subscription-only multi-provider Hermes squad.

Why this exists

The Hermes Agent ships kimi-coding as a built-in provider, but it only accepts static API keys prefixed sk-kimi-* (paid Kimi Code dashboard keys). Users who already have a Kimi Code subscription (paid app/CLI access) have OAuth credentials in ~/.kimi/credentials/kimi-code.json — but the bundled provider can't refresh them.

This plugin closes the gap:

  • Reads OAuth credentials from the kimi CLI's credential file
  • Auto-refreshes via the official OAuth endpoint (https://auth.kimi.com/api/oauth/token) when the access token is within 5min of expiry
  • Saves refreshed tokens back to the CLI's file (keeps kimi CLI in sync)
  • Seeds KIMI_API_KEY + KIMI_BASE_URL for the bundled chat_completions transport
  • Self-registers in both ProviderProfile (runtime) and PROVIDER_REGISTRY (auth-side)

The Hermes routes inference at api.kimi.com/coding/v1 using the Anthropic Messages API surface (Kimi Code endpoint is Anthropic-compatible).

Architecture

Hermes provider 'kimi-code-bypass'
    -> reads ~/.kimi/credentials/kimi-code.json (managed by kimi CLI)
    -> auto-refresh if access_token within 5min of expiry via
       POST https://auth.kimi.com/api/oauth/token (grant_type=refresh_token)
    -> seeds KIMI_API_KEY + KIMI_BASE_URL in os.environ on plugin import
    -> Anthropic Messages API surface at https://api.kimi.com/coding/v1/messages

This is NOT a web-scraping bypass. It is the same OAuth flow the official kimi CLI uses.

Prerequisites

  • Hermes Agent installed (hermes CLI working)
  • kimi CLI installed: uv tool install kimi-cli (or whatever your distribution method)
  • kimi auth login ran at least once (credential file populated)

Install

git clone https://github.com/lckx777/hermes-kimi-code-bypass.git
cd hermes-kimi-code-bypass
./install.sh

The installer copies the plugin into ~/.hermes/plugins/model-providers/kimi-code-bypass/ and runs a one-shot discovery check.

Verify

After install, in a new Hermes session:

hermes auth status kimi-code-bypass
# expect: "logged in"

hermes chat -q "Reply: PING" --provider kimi-code-bypass --model kimi-for-coding -Q --max-turns 1
# expect: "PING" (or similar short response)

Use as part of a subscription-only Hermes squad

Wire the 4-role squad (codex orchestrates → kimi codes → opus debugs → codex reviews) entirely via Hermes native config — no orchestrator code, no squad YAML required:

# ~/.hermes/config.yaml

model:
  provider: openai-codex
  model: gpt-5.5
  default: gpt-5.5            # critical: oneshot reads this

delegation:
  provider: kimi-code-bypass   # this plugin
  model: kimi-for-coding

fallback_providers:
  - {provider: openai-codex,     model: gpt-5.5}
  - {provider: anthropic,        model: claude-opus-4-7}
  - {provider: kimi-code-bypass, model: kimi-for-coding}

Then prompt the orchestrator: "delegue debug pra opus", "delegue review pra codex". The main LLM decides per-call routing.

Three failure modes (when something breaks)

| Cause | Symptom | Recovery | Time | |-------|---------|----------|------| | A (60%) — credential file missing | provider returns 401, env empty | kimi auth login | 2min | | B (30%) — refresh token expired (~30d) | 401 even after fresh access_token attempt | kimi auth login (re-mints both tokens) | 2min | | C (10%) — plugin not discovered / seeder didn't run | get_provider_profile('kimi-code-bypass') returns None | restart Hermes / check startup stderr for [kimi-code-bypass] warnings | 1min |

Full diagnostic procedure documented in the Hermes skill mcp/consuming-external-cli-oauth-from-hermes-provider/references/kimi-code.md.

Uninstall

./uninstall.sh

Removes ~/.hermes/plugins/model-providers/kimi-code-bypass/. Does NOT touch ~/.kimi/credentials/ (managed by the kimi CLI, not by this plugin).

License

MIT. See LICENSE.

Acknowledgments

Related

  • mcp/consuming-external-cli-oauth-from-hermes-provider — Hermes skill that codifies this CLI-OAuth bypass pattern as a class
  • mcp/auditing-hermes-setup-completeness/references/multi-provider-subscription-routing.md — validated config snapshot for the 4-role squad
  • mcp/repairing-hermes-bypass-q8-after-agent-refactor — the Anthropic-side equivalent

Built by lckx777 on 2026-05-17. ZERO-CHUTE rigor — all claims empirically validated before merge.

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.