DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to route Claude model tiers to different models with Free Claude Code

Send Opus, Sonnet, and Haiku requests to separate FCC models to balance cost and quality.

Credentials. Each provider used for a tier needs its own key stored in FCC.

Who it is forA developer who wants heavy reasoning on a strong model and quick edits on a cheaper one.

The problemClaude Code expects its model tiers to map to one connection, which limits how much you can save per task.

The outcomeEach Claude model tier is sent to its own configured model, while tools, streaming, and images keep working.

What you need first

  • A macOS, Linux, or Windows computer with a terminal
  • An API key from at least one provider in the README catalog, such as NVIDIA NIM
  • Permission to run the install script from the README

Steps

  1. Install FCC with the install command from the README and choose Claude Code when prompted.
  2. Start FCC with fcc-server on Linux, or open Free Claude Code on Windows or macOS.
  3. In the Admin UI, configure the providers you want to use and select a model for each tier in Model Config.
  4. Click Apply to save the routing.
  5. Run fcc-claude and check the /model picker to confirm each tier.

Prompt for your agent

In the repo Alishahryar1/free-claude-code, map the Opus, Sonnet, and Haiku tiers to different FCC models and start `fcc-claude`. Expected output: each tier shows its assigned model in the /model picker. Verify by running one short prompt on each tier and checking the server log.

Caveat. The README says tiers are routed independently only with compatible models, so check each model's support before mapping it.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page