Commit History
-
feat: add key management and provider keypool (# new feature)
shinmentakezo07 +1: Claude- Add src/free_claude_code/config/admin/keys.py - Add src/free_claude_code/providers/keypool.py - Add corresponding test files - Update admin static assets and config files - Bump version to 4.18.0 Co-Authored-By: Claude <noreply@anthropic.com>2c96ecb
-
Use codebase .env for server and admin config
shinmentakezo07Settings and the Admin UI now load and persist config from the repo-local .env instead of the user-managed ~/.fcc/.env, so a codebase .env is always authoritative. Admin writes target the repo .env, and the managed env source label is removed from the Admin UI.3cc3731
-
Make reasoning policy provider-neutral and client-aware (#1148)
Unverified signature## Problem FCC reduced reasoning to global and route booleans, mixing client intent, configuration, provider wire capabilities, output visibility, and history replay. That discarded named client efforts, encouraged model-name checks, and made provider behavior inconsistent. ## Changes | Before | After | | --- | --- | | Admin exposed global and route thinking toggles. | Admin exposes **Off**, **From client**, **Low**, **Medium**, **High**, **X-High**, and **Max**; Fable, Opus, Sonnet, and Haiku also expose **Inherit**. | | Request intent was repeatedly reduced to a boolean across routing and providers. | The application boundary resolves one immutable `ReasoningPolicy` with independent control, named effort, and exact positive token budget. | | Provider adapters could infer reasoning behavior from upstream model names or versions. | Provider profiles translate only documented provider-wide wire capabilities; architecture and contributor rules prohibit model-specific reasoning branche…dc04eee
-
Establish single-owner runtime with stream-safe provider hot swaps (#1036)
Unverified signature## Problem Provider runtime ownership was split between lifecycle code and mutable FastAPI state, so Admin replacements could leak the new runtime, double-close the old runtime, or close providers still serving active streams. The API package also owned concrete process composition, obscuring subsystem boundaries. ## Changes | Before | After | | --- | --- | | FastAPI routes inspected several concrete `app.state` resources. | FastAPI receives one explicit `ApiServices` boundary and stores only `app.state.services`. | | Admin Apply persisted config and directly replaced one runtime reference. | Admin Apply validates a candidate, commits atomically, and publishes it through the single runtime owner. | | Provider replacement could close clients used by active streams. | Generation leases retain old providers until each streaming or non-streaming response finishes. | | Provider generations owned discovery state and model metadata. | `ProviderRuntimeManager` owns one application-lifetime …0602b26