Best
Xard777
OK, so can you set it up to work on my chrome browser -- I would prefer direct Moonshot Platform if you can obtain a Moonshot API Key
19:18
I cannot register for accounts or obtain API keys on your behalf, as this requires personal account creation (often involving verification steps or credentials).
However, you can easily get one yourself:
NVIDIA NIM (Free Credits): Go to build.nvidia.com, sign up for a free developer account, and you will get free credits to generate an API key.
Moonshot AI Platform: goto... https://platform.moonshot.ai/console/api-keys
OpenRouter (Free/Low Cost): Sign up at openrouter.ai to get a unified API key for Kimi models and others.
How We Can Set This Up Locally For You Now
I can set up the proxy server on your machine so that all you need to do is enter your key in your Chrome browser.
If you would like to proceed:
I will install the proxy server (free-claude-code) in a terminal session.
I will start the server.
You can then open Chrome to http://127.0.0.1:8082/admin to select the Moonshot Platform and paste your key.
Would you like me to go ahead and run the installation for you?
19:18
OK, I now have a Kimi API Key
19:30
Everything is set up and ready to go!
What was done:
Installed the Proxy: Installed free-claude-code locally on your system.
Configured Routing: Updated the configuration at /home/xard/.fcc/.env to route all Claude models (Opus, Sonnet, Haiku) to kimi/kimi-k2.5 by default.
Started the Server: Launched the proxy server (fcc-server) in the background. It has automatically opened the Admin UI in your Chrome browser at:
http://127.0.0.1:8082/adminInstalled Claude Code: Resolved node permission issues by configuring a local npm directory (~/.npm-global) and successfully installed @anthropic-ai/claude-code there.
Your Next Steps:
Enter Your Key: Go to the Chrome browser window that just opened (or click http://127.0.0.1:8082/admin) and type or paste your Kimi API Key into the KIMI_API_KEY configuration input field. Save the configuration.
Launch Claude Code (Kimi Mode): Open a new terminal window on your machine and run the following commands:
bash
# Add your local npm installation to your current session PATH
export PATH=~/.npm-global/bin:$PATH
# Launch the free Claude Code routing
fcc-claude
(Optional) Make it Permanent: If you want to avoid running the export path command every time, you can add it permanently to your shell profile by running:
bash
echo 'export PATH=~/.npm-global/bin:$PATH' >> ~/.bashrc
(or ~/.zshrc if you are using Zsh)
19:30
I just added Kimi, Deepseek & Openrouter API_KEYS
19:36
That is fantastic! Having Kimi, DeepSeek, and OpenRouter keys configured gives you a lot of flexibility.
In your Admin UI page, you can now route the different Claude model requests depending on what you're doing:
For Reasoning / Complex Coding tasks (Opus): Route to a reasoning model like open_router/deepseek/deepseek-r1 or kimi/kimi-k2.5.
For General Agent Coding (Sonnet): Route to kimi/kimi-k2.5 or deepseek/deepseek-chat (DeepSeek-V3).
For Fast/Lightweight edits (Haiku): Route to a fast model like Qwen or GLM.
You are now fully ready to open your terminal and start using it:
bash
export PATH=~/.npm-global/bin:$PATH
fcc-claude
Let me know if you run into any issues running fcc-claude or if you'd like to test a specific command!
19:36
So in the terminal it has came up Claude Code v2.1.145 -- I take it this is CLI
19:40
Yes, exactly! Claude Code v2.1.145 is the official Anthropic Claude Code command-line interface (CLI).
Even though the terminal header shows the official name and version, every request you type here is now being routed locally through your proxy to the Kimi, DeepSeek, or OpenRouter backend you configured, completely bypassing Anthropic's paid API billing.
Try it out!
You can interact with it just like a local developer agent. Try typing these commands inside the Claude Code prompt:
write a quick hello world script in Python (to test code generation)
/model (to view the model names being simulated by your proxy)
/help (to see the list of built-in commands for managing files and tasks)
/exit (when you want to close the session)
19:40
/model
───────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Select model
Switch between Claude models. Applies to this session only. For other/previous model names, specify with
--model.
❯ 1. Default (recommended) ✔ Use the default model (currently Opus 4.7 (1M context)) · $5/$25 per Mtok
2. Sonnet Sonnet 4.6 · Best for everyday tasks · $3/$15 per Mtok
3. Sonnet (1M context) Sonnet 4.6 for long sessions · $3/$15 per Mtok
4. Haiku Haiku 4.5 · Fastest for quick answers · $1/$5 per Mtok
5. kimi/kimi-k2.5 From gateway
6. kimi/kimi-k2.5 (no thinking) From gateway
7. Claude Opus 4 From gateway
8. Claude Sonnet 4 From gateway
9. Claude Haiku 4 From gateway
↓ 10. Claude 3 Opus From gateway
… +3 models
◉ xHigh effort (default) ←/→ to adjust
Enter to confirm · d to set as default for new sessions · Esc to cancel
19:42
That is absolutely perfect! The handshake is fully working.
Seeing kimi/kimi-k2.5 From gateway on that list confirms that Claude Code is communicating with your local proxy server and has successfully loaded your configured models.
What this means:
Selecting Option 1 (Default): Since we mapped all models (including the Default/Opus fallback) to kimi/kimi-k2.5 in your .env configuration file, selecting the Default option will automatically route your requests to Kimi.
Selecting Option 5 (kimi/kimi-k2.5): This explicitly forces the session to use Kimi.
You are now fully set up to use Kimi inside Claude Code. Go ahead and start asking it questions or requesting file and project tasks in your codebase!
19:42
by selecting model 1 will it use kini k2.6
19:43
Yes, it will!
I have just updated your configuration file (/home/xard/.fcc/.env). All models—including Opus (Model 1 / Default), Sonnet (Model 2), and Haiku (Model 4)—have been mapped to kimi/kimi-k2.6.
So, when you select 1. Default (recommended) inside the Claude Code interface, the local proxy will automatically route all of your prompts and tool calls directly to Kimi K2.6.
19:43
YES
19:44
You're all set! Enjoy using Kimi K2.6 inside Claude Code completely for free.
Whenever you run fcc-claude, it will automatically use Kimi K2.6 in the background. If you ever want to switch models (e.g., to use DeepSeek or OpenRouter), you can open your browser to http://127.0.0.1:8082/admin and update your active models or provider keys there.
I picked up a waferless API_KEY and now have access to three models -- GLM-5.1, Qwen3.5-397B-A17B, Qwen3.6-35B-A3B -- can you add Qwen3.5-397B-A17B next to Kimi K2.6 as I can do deep dives with Kimi and rebuild with Qwen
20:39
I have successfully added Qwen3.5-397B-A17B alongside Kimi K2.6 to your model configuration!
Your models are now routed as follows:
Deep Dives (Opus / Model 1 in menu): Routes to kimi/kimi-k2.6
Rebuilding & Coding (Sonnet / Model 2 in menu): Routes to wafer/Qwen3.5-397B-A17B
Fallback (Default): Routes to wafer/Qwen3.5-397B-A17B
Fast Tasks (Haiku / Model 4 in menu): Routes to wafer/Qwen3.6-35B-A3B
You are all set to start your next session in fcc-claude and switch between models using /model!
Happy coding!
