Commit History
-
feat: theme dashboard charts and expose admin UI on HF Spaces
shinmentakezo078bdd0d7
-
feat: track local-path usage and enrich analytics dashboard
shinmentakezo07- Record server-tool and local-optimization requests in the usage ledger - Relay cache read/creation tokens into Responses usage details - Add cache/reasoning KPIs, request-log pagination, heatmap metric toggle, latency tooltips, and a sticky sidebar in the Admin UI - Rebuild admin static assets for the updated dashboard - Add usage-tracking and cache-token relay tests - Bump version to 4.28.0c860470 -
feat: add usage tracking with live throughput rates and analytics dashboard
shinmentakezo07 +1: ClaudeTrack per-request token usage (input/output/cache/reasoning) plus full prompts (capped at 64 KB) in a JSON ring buffer at ~/.fcc/usage.json, captured through a transparent UsageTrackingStream over the executor stream. Expose GET /admin/api/usage and a new Usage page in the admin UI with KPI cards, token mix, volume area chart, top endpoints, routing sankey, and hourly heatmap, auto-refreshing every 10 seconds. Throughput rates use a trailing 60-second live window on both backend and frontend so they track real-time traffic and decay to zero when idle; tokens/second counts output tokens only, tokens/minute counts input plus output. Bump 4.25.0 -> 4.27.0. Co-Authored-By: Claude <noreply@anthropic.com>e8f2acc -
feat: surface saved endpoint models and revamp the admin UI
shinmentakezo07Model ids saved per OpenAI-compatible endpoint on the admin page are now included in the admin model options and provider status, so numbered routes (openai_compatible_1/<model>) stay listed even when the endpoint's live /models route is unreachable. - settings: OpenAI-compatible instances persist an optional models list - status: endpoint cards report saved model ids alongside live ones - admin API: model options merge configured, discovered, and stored ids - tests: stored endpoint models appear in options/status; config round-trip Admin UI overhaul: - dark mode toggle (system-aware, persisted) with a light/dark token pass - responsive sidebar: off-canvas drawer with backdrop/Escape on mobile - sticky blurred header (view icon, title, description, version) and a sticky action bar with status icons and a dirty-count badge - config sections become cards with per-section icons and a model refresh action; fields gain source badges and description hints - provider/connected-account c…ee2cd20 -
fix: cache-bust admin UI and show the running version
shinmentakezo07The admin UI required a hard refresh after every deploy: the bundle was emitted with fixed filenames (assets/admin.js, assets/admin.css) even though the server already sent Cache-Control: no-store. Any cache that ignored or reused those URLs (browser memory/disk cache, back-forward cache, or an edge proxy in front of the deployment) kept serving the old bytes, since the URL never changed between deploys. - vite emits content-hashed filenames (admin-[hash].js/.css), so each build references new URLs and stale caches become inert by construction; index.html stays no-store and always fresh - admin config API now returns the installed package version (api -> core import, respecting the config package's dependency policy) and the header shows a vX.Y.Z badge, so a deployed update is visible without digging - cache-policy contract test now covers every built asset instead of the fixed names; version presence asserted in the manifest test - version 4.23.0 -> 4.23.11c54cf1 -
fix: make model combobox editable and searchable in Model Routing
shinmentakezo07The model field combobox looked searchable but was broken: the input was controlled by the committed value so keystrokes were reverted, typed text could never be committed (the empty state promised a custom slug that was impossible to enter), Enter only worked after arrow selection, and blur discarded the draft. Rewrite it as a true editable+searchable combobox: - the input shows the draft text while editing, so model ids can be typed or edited in place (WYSIWYG: the text in the box is the value) - filtering over the model list now reacts to visible typing - Enter commits the highlighted option, or the typed text as a custom model id when nothing is highlighted - blur commits the draft (exact option match selects the canonical option; anything else becomes a custom id); Escape reverts - stale filter/query and arrow index state reset on open/query change - version 4.22.1 -> 4.23.0c03ea68 -
feat: fetch models from OpenAI-compatible endpoints in admin UI
shinmentakezo07Add a Fetch models button to each numbered endpoint card on the OpenAI-Compatible page. It calls the endpoint's /models route through the existing provider test endpoint (GET {base}/models via the OpenAI client), lists the returned model ids on the card, adds them as provider/model options for the Model Config dropdowns, and offers "Use as default" to set the numbered route as the default model. - frontend: per-endpoint fetch/clear/use-model state, model list panel on each card, error surfacing through the action bar - tests: numbered instance list_model_infos() fetches model ids; contract status test accounts for numbered instances replacing the legacy openai_compatible entry when endpoints are configured - docs: README fetch-models notes - version 4.21.0 -> 4.22.0969cedb -
feat: numbered OpenAI-compatible endpoints admin page
shinmentakezo07Add a dedicated Admin UI page for OpenAI-compatible endpoints. Each endpoint becomes a numbered provider (openai_compatible_1/<model>, openai_compatible_2/<model>, ...) stored as a JSON array in OPENAI_COMPATIBLE_INSTANCES, with per-endpoint base URL, comma-separated key pool, and proxy. Endpoint 1 also answers the legacy openai_compatible/ route; the single-endpoint env vars remain the fallback. - settings: OpenAICompatibleInstance model, JSON parse/validate, numbered route validation across model fields - runtime: instance resolution in create_provider, provider config builder, model-list discovery includes numbered ids - admin: manifest field + status entries (numbered instances replace the single-endpoint entry when configured) - frontend: OpenAI-Compatble view with add/remove/import/test per endpoint - tests: settings parsing, route validation, factory resolution, discovery, manifest, admin status - version 4.20.0 -> 4.21.0f78c884 -
feat: admin dedicated pages, pool key management, keypool quotas (#1350)
shinmentakezo07- Admin UI becomes a Vite build under frontend/ with hash-routed dedicated pages (#/providers, #/model-config, #/messaging); the providers view renders only on its page. - Pool fields support reveal/edit/remove of individual keys via a new loopback-only GET /admin/api/pools/{field_key} endpoint; apply resolves tokens mixed with raw edits against stored keys. - admin assets now serve Cache-Control: no-store, fixing stale-bundle breakage after the frontend migration. - ApiKeyPool gains per_key_quota rotation plus transient HTTP 429/5xx/overload failover rotation with mark_failure. - CI runs the frontend build and verifies committed admin assets.9b71fd0 -
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
-
Add ChatGPT OAuth as an OpenAI Codex provider (#1279)
Unverified signature## Problem FCC supports API-key and local providers, but customers cannot use models included with their ChatGPT subscription. Reusing Codex credentials would also couple FCC to another application's mutable authentication state. ## Changes | Before | After | | --- | --- | | OpenAI subscription access was unavailable. | Customers connect ChatGPT from the local Admin UI with browser PKCE or device code. | | Provider availability came only from static settings. | A process-owned connected account adds, refreshes, and evicts OpenAI models dynamically. | | FCC had no ChatGPT Codex transport. | `openai/<model-id>` uses FCC-owned renewable credentials and neutral Responses conversion. | | Retries and reasoning continuity had no subscription-provider coverage. | Commit-boundary retries prevent duplicate output while encrypted reasoning and tool IDs survive round trips. | <!-- greptile_comment --> <details open><summary><h3>Greptile Summary</h3></summary> This PR adds ChatGPT OAuth and a…9fb95ba
-
Add Google Vertex AI with renewable ADC (#1193)
Unverified signature## Problem | Before | After | | --- | --- | | FCC supported Google AI Studio API keys but could not route coding agents through a Google Cloud Vertex AI project. | `vertex/...` routes through Google's [documented OpenAI-compatible Chat Completions endpoint](https://cloud.google.com/vertex-ai/generative-ai/docs/start/openai), using the global endpoint by default or an explicitly configured region. | | A pasted Vertex access token would expire, while Application Default Credentials were not part of provider construction. | FCC loads [Application Default Credentials](https://cloud.google.com/docs/authentication/application-default-credentials), supplies a renewable credential callback to the OpenAI transport, coalesces concurrent refreshes, and returns typed authentication or transient failures. | | Vertex does not expose its model catalog through the compatible OpenAI `/models` route. | FCC translates its generic discovery operation to Google's paginated [publisher-model list API](https…cabd2d4
-
Prevent the admin UI from being served from cache (#1160)
Unverified signature## Problem Browsers could retain the local admin page, assets, or error responses, leaving users on stale UI state after an FCC update. ## Changes | Before | After | | --- | --- | | Admin responses had no complete cache policy, and route-level handling missed exception responses. | A dedicated admin response boundary sends `Cache-Control: no-store` for every `/admin` response, including 403, 404, validation, and unexpected errors. | | Admin API fetches used the browser's default cache mode. | Admin API fetches explicitly use `cache: "no-store"`. | | Cache behavior was untested. | Tests cover HTML, assets, JSON, failure responses, and path scoping. | <!-- greptile_comment --> <details open><summary><h3>Greptile Summary</h3></summary> This PR prevents browsers from retaining stale admin UI responses. The main changes are: - Adds `Cache-Control: no-store` to successful and error responses under `/admin`. - Sets admin API fetches to use the browser's `no-store` cache mode. - Adds te…98786ea -
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
-
Add an explicit searchable model dropdown (#1133)
Unverified signature## Problem Admin model fields depended on the browser's native datalist. Filtering worked, but browsers did not consistently expose a visible dropdown for browsing the full model catalog. ## Changes | Before | After | | --- | --- | | Model fields relied on browser-native datalist behavior. | Model fields use one FCC-owned searchable combobox with a visible chevron. | | Suggestions became discoverable only through browser-specific interactions. | Clicking the field or chevron opens the full catalog, while typing filters it. | | Keyboard navigation and empty results depended on native picker behavior. | Arrow keys, Enter, Escape, empty-state guidance, custom slugs, and None are handled explicitly. | | Selects and model fields rendered separate dropdown indicators. | Both controls use the same shared chevron asset. | <!-- greptile_comment --> <details open><summary><h3>Greptile Summary</h3></summary> This PR replaces native model datalists with an explicit searchable combobox. The m…1db2c84
-
Add searchable model selection to the Admin UI (#1121)
Unverified signature## Problem Admin model routing fields required users to construct provider-prefixed model slugs. Optional tier overrides represented inheritance as an unexplained blank value. ## Changes | Before | After | | --- | --- | | Model inputs only gained suggestions after an individual provider refresh. | Model inputs load configured and discovered canonical slugs from one Admin catalog. | | Model routing looked like unrestricted text entry. | Model routing uses the browser's searchable model dropdown while retaining manual entry. | | Tier overrides displayed an empty value for fallback routing. | Tier overrides display **None** and persist it as an unset override. | | Model refresh returned provider-shaped cache internals. | Model refresh returns the same canonical catalog consumed by the Admin UI. | | Users inferred the provider/model slug format from examples. | The Admin UI and README define and present complete provider/model slugs. | <!-- greptile_comment --> <details open><summary>…0ff89da
-
Move runtime packages under src namespace (#1029)
Unverified signature## Problem Runtime modules were published as generic top-level packages like `api`, `cli`, and `providers`. That shape is fragile for PyPI packaging and weakens explicit ownership boundaries. ## Changes | Before | After | | --- | --- | | Runtime code lived in root-level packages. | Runtime code lives under `src/free_claude_code/`. | | Console scripts targeted top-level modules. | Console scripts target namespaced modules. | | Tests and smoke helpers imported old package roots. | Tests and smoke helpers import `free_claude_code.*`. | | Packaging listed six root packages. | Packaging builds the single namespaced package. | | Contracts allowed old root package directories. | Contracts require the src namespace and reject old root imports. | <!-- greptile_comment --> <details open><summary><h3>Greptile Summary</h3></summary> This PR moves the runtime packages into the `src/free_claude_code` namespace. The main changes are: - Console scripts now point to `free_claude_code.*` entrypoi…0d0f0f9