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

How to keep a coding session running during provider outages with Free Claude Code

Set a fallback model list so FCC moves to your next model when a provider fails.

Credentials. Each provider you add needs its own API key, and every key stays stored in FCC.

Who it is forA developer in the middle of a long coding task who cannot afford a stalled turn when one provider goes down.

The problemWhen a model provider has an outage or errors out, the coding agent stops and the turn has to be restarted by hand.

The outcomeAfter retries are used up, FCC tries the next configured model, and the turn continues across every connected client.

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 configure at least two providers in Providers → Admin UI.
  2. Open Model Config in the Admin UI and add an ordered Fallback Models list.
  3. Click Apply to save the model selection.
  4. Run fcc-codex or fcc-claude and work as normal.
  5. Check the FCC server log after an outage to confirm which model handled the retry.

Prompt for your agent

In the repo Alishahryar1/free-claude-code, configure two providers and an ordered Fallback Models list in Model Config, then start `fcc-codex`. Expected output: a coding turn completes even when the first model is unavailable. Verify by checking the server log for the fallback model name.

Caveat. The README warns that a failed request may reach and consume usage from more than one provider before it succeeds.

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