Alishahryar1/free-claude-code

If you already run Claude Code, Codex or another coding agent but keep hitting free-tier limits or switching tools to try a different model, FCC is a plausible installer-and-admin-UI layer to evaluate. It does not replace the agent; it changes where the model calls go.

The problem

You want one familiar coding agent, say Claude Code in the terminal, and you want to try a free provider or a local model without rewiring configuration by hand. Today that means editing per-tool config, checking which providers each harness supports, and redoing it when a quota runs out mid-task. FCC centralizes provider credentials and model choices in one Admin UI, then exposes that catalog to the agent you already run. The result is a single place to switch models, and a turn can continue on a configured backup model rather than forcing a restart.

What's different

The core mechanism is an intermediary between harnesses and providers: the README claims 61 providers, 12 coding agents and 1.3B+ free tokens monthly, with an explicit policy of following provider terms and dropping integrations that stop being allowed (project README). Fallback across configured models after retries are exhausted, applied to every client, is the most useful operational feature for people whose free quotas are unreliable. Two optional components, RTK and Headroom, filter command output and compress tool results, which the README estimates can cut token usage by up to 90% (project README). That is an author estimate, not independently measured, and it adds parts to the install and update path.

The less comfortable trade-off is geographic and contractual. The project frames its provider list as ToS-friendly and says it removes integrations when providers disallow them, so the available set is expected to shift over time; you should expect maintenance of credentials and provider choices, not a fixed setup. FCC is also AGPL-3.0-only licensed (license), which matters if you plan to redistribute a modified build. The README is long and covers installation, updating and uninstall, but provider-specific quotas and account eligibility sit with each provider, not with FCC.

Who should try it

Good fit: a developer or small team already using one or more of the supported CLI agents who wants a shared model list and automatic fallback without touching each tool's config, and who is comfortable letting an admin UI manage provider keys locally. A second good case is testing several models on the same coding task without learning each harness's provider settings.

Poor fit: anyone expecting a self-contained free coding assistant with fixed capacity. Also a poor fit for locked-down machines where a local admin UI and a background server process conflict with policy, or where installing optional output filters is unwanted complexity. The README's install path covers macOS/Linux and Windows and includes a desktop launcher on Windows and macOS; on Linux the server runs in a terminal and must stay open, which changes the everyday experience (installation instructions).

Requirements and limitations

FCC targets Python 3.14 and uses uv as its package manager (project README), so the install scripts bring a specific toolchain; older Python environments are not the assumed path. The install and uninstall scripts are the documented route, and the README warns to stop all running FCC commands and quit connected editors before uninstalling. Uninstall removes the application and ~/.fcc/ but deliberately keeps uv, Python and your coding agents, so cleanup is partial by design (project README).

Ongoing care matters more than installation: free model catalogs and provider terms change, and the project itself says it removes disallowed integrations. Budget time for occasional re-checks of which providers still work and for fcc-update runs. Optional voice support pulls in extra local components and a torch backend choice, so only include it if you need it.

HotRepo's take

HotRepo recorded 11 daily-board days between 2026-05-19 and 2026-10-26, going from 26,069 to 63,590 stars; the most recent recorded day, 2026-10-26, added 358 stars. Those are board snapshots, not a complete daily series, and the sample cannot establish lasting adoption. Before committing, verify the current provider list and the documented update path, since the provider mix is the part most likely to change under you.