feat: admin dedicated pages, pool key management, keypool quotas (#1350)
shinmentakezo07
9b71fd0
- 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.
Simplify README around customer workflows (#1345)
## Problem
The README buried setup and usage under repeated screenshots, duplicated
commands, and implementation details. Documentation tests coupled CI to
wording and layout instead of production behavior.
## Changes
| Before | After |
| --- | --- |
| The opening repeated product copy and stacked screenshots before the
guide. | The opening leads with five scannable benefits and retains
three contextual screenshots. |
| Provider, client, and integration guidance was dense and repetitive. |
Advanced guidance is grouped into focused expandable sections with
shared platform instructions. |
| Documentation wording and structure were enforced by mechanical tests
and README-derived metadata. | Documentation tests and doc-only metadata
are removed while packaging and production coverage remain. |
Add coding-agent selection and validate PowerShell downloads (#1324)
## Problem
Installers always installed or verified every coding agent, so users
could not choose only Claude Code, Codex, or Pi. Windows could also
execute an intercepted HTML response as PowerShell. Fixes #1322.
## Changes
| Before | After |
| --- | --- |
| Interactive installs processed all three coding agents. | Interactive
installs ask about Claude Code, Codex, and Pi with Yes defaults. |
| Users could not skip individual agents. | No skips installation and
verification while leaving an existing agent unchanged. |
| Selecting no agents had no defined contract. | All-No re-prompts, and
installation requires at least one selected agent to be available. |
| Automation depended on the unconditional client flow. |
Non-interactive installs preserve the existing all-selected behavior. |
| Completion output advertised every required wrapper. | Completion
output advertises only selected and available coding agents. |
| Every nonempty downloaded file was executed as PowerShell. | Every
do…
Fix Windows ARM64 installation without source builds (#1293)
## Problem
Windows ARM64 installations selected native Python and attempted to
compile `cryptography` because current releases provide no ARM64 Windows
wheel. Fresh FCC installation therefore failed without a local Rust and
C build environment. Fixes #1289.
## Changes
| Before | After |
| --- | --- |
| The PowerShell installer requested architecture-neutral Python 3.14.0.
| The PowerShell installer requests x64 CPython 3.14.0, which Windows on
ARM runs through transparent emulation. |
| ARM64 dependency resolution selected unsupported native source builds.
| ARM64 dependency resolution consumes the supported Windows x64 wheels.
|
| Installer contracts checked only the Python version. | Installer
contracts preserve the complete x64 interpreter request. |
| The package version was 4.15.0. | The package version and lockfile are
4.15.1. |
<!-- greptile_comment -->
<details open><summary><h3>Greptile Summary</h3></summary>
The Windows installer now requests CPython 3.14.0 for Windows …
## Problem
PowerShell does not wait when directly invoking the Windows
`fcc-desktop` GUI executable. The installer checked for the exported ICO
before the GUI process finished, then stopped before replacing generic
shortcut icons.
## Changes
| Before | After |
| --- | --- |
| Icon export used the synchronous command helper even though Windows
launched the GUI executable asynchronously. | A Windows-specific icon
export helper starts the GUI process hidden and waits for completion. |
| Export success could be checked before the process exited. | The
installer validates the completed process exit code and exported file
before writing shortcuts. |
| Installer tests used only synchronous batch commands for the desktop
entrypoint. | Regression coverage runs a real Windows GUI launcher
through PowerShell 5.1 and 7, including a destination path containing
spaces. |
| The package version was 4.12.5. | The package and lockfile version are
4.12.6. |
<!-- greptile_comment -->
<details open><s…
## Problem
Free Claude Code's desktop surfaces had no shared visual identity. The
tray used a generated blue `F`, Windows shortcuts inherited the generic
executable icon, and the macOS app bundle declared no icon at all.
## Changes
| Before | After |
| --- | --- |
| Desktop artwork was generated independently at runtime. | A
deterministic SVG source and packaged PNG, ICO, and ICNS variants define
one high-contrast orange FCC mark. |
| The tray, Windows shortcuts, and macOS bundle displayed unrelated or
generic artwork. | Every desktop surface now consumes the same packaged
brand asset. |
| Installers had no native icon handoff contract. | `fcc-desktop
--export-icon` copies the wheel-owned format into installer-managed
locations, with fail-fast verification and uninstall coverage through
the existing managed paths. |
| Icon packaging and platform wiring were implicit. | Regression tests
validate native containers, byte-preserving export, Windows shortcut
metadata, macOS bundle metada…
## Problem
Selecting "Do nothing" in Pi's installer returned success without
installing Pi. FCC then required the missing command and stopped before
installing itself. Fixes #1240.
## Changes
| Before | After |
| --- | --- |
| A successful Pi installer exit always required a compatible `pi`
command. | A successful Pi installer exit may leave Pi unavailable while
FCC installation continues. |
| Pi verification and completion guidance always ran. | Pi verification
and completion guidance run only when Pi is available. |
| Installer documentation described Pi as mandatory. | Installer
documentation describes Pi as optional. |
| Skip behavior lacked cross-platform regression coverage. | Skip
behavior is covered on PowerShell and POSIX, including an unrelated
existing `pi` command. |
<!-- greptile_comment -->
<details open><summary><h3>Greptile Summary</h3></summary>
The PR makes Pi optional during installation.
- Continues FCC installation when Pi’s installer succeeds without
install…
Structure startup instructions by platform (#1226)
## Problem
The startup section combines Windows, macOS, Linux, desktop, and
terminal behavior in one block, making each platform's launch path
harder to scan.
## Changes
| Before | After |
| --- | --- |
| Startup instructions mixed all platforms in one paragraph. | Startup
instructions use separate Windows, macOS, and Linux subsections. |
| Desktop and terminal details interrupted the platform-specific steps.
| Shared desktop and terminal details follow the platform-specific
steps. |
Add a native FCC desktop launcher for Windows and macOS (#1225)
## Problem
Free Claude Code currently has to remain attached to a terminal, so
closing that window stops the proxy and users have no native way to
reopen Admin or control the background server. The contributed Windows
wrapper also would have introduced a second bundled server lifecycle
instead of reusing FCC's cleanup and restart ownership. Fixes #1147.
## Changes
| Before | After |
| --- | --- |
| Users keep `fcc-server` running in a terminal. | Windows and macOS
users can launch a console-free FCC Desktop host from a
desktop/application shortcut and control it from the tray or menu bar. |
| A wrapper would need to spawn and terminate a child server. | The
terminal and desktop paths share one in-process supervisor, one graceful
runtime shutdown path, and an OS-held singleton lock. |
| Installers manage only command entry points. | Windows installs
desktop and Start-menu shortcuts; macOS installs a per-user app bundle
and owned desktop link; uninstallers remove only those FCC artifa…
Fail safely when FCC is running during installation (#1182)
## Problem
A running Free Claude Code command can make `uv tool install --force`
fail after partially deleting the installed tool environment. The
installers did not detect this precondition, and the POSIX fallback
relied on truncated process names.
## Changes
| Before | After |
| --- | --- |
| Installers entered tool replacement while FCC commands were running. |
Installers report matching FCC commands and PIDs, then exit before
mutation. |
| A process starting during client or uv setup could reach tool
replacement. | Installers recheck immediately before `uv tool install`.
|
| The no-`pgrep` fallback compared truncated `comm` names. | Install and
uninstall fallbacks match full command lines. |
| Running-process coverage existed only for uninstallers. |
Cross-platform tests cover every FCC entry point, late starts, similar
names, and fallback detection. |
| The package version was 4.8.7. | The package version is 4.8.8. |
<!-- greptile_comment -->
<details open><summary><h3>Grepti…
Enable uv malware checks on every CI runner (#1177)
## Problem
Dependabot updates passed CI without uv checking their locked packages
against known malware advisories. The supported uv minimum also predated
this capability.
## Changes
| Before | After |
| --- | --- |
| Project, installers, and CI allowed uv versions without malware
checking. | All supported surfaces require uv `0.11.16` or newer. |
| Parallel CI runners synchronized dependencies without an OSV malware
check. | Workflow-wide uv environment settings enable the check
independently on every runner. |
| Installers treated prerelease builds as their equivalent stable
version. | Installers accept stable uv releases only while preserving
valid build metadata. |
| uv security-policy values and edge behavior could drift between
maintained surfaces. | Contract and installer tests enforce the shared
policy. |
| FCC reported version `4.8.5`. | FCC reports patch version `4.8.6`. |
<!-- greptile_comment -->
<details open><summary><h3>Greptile Summary</h3></summary>
This PR enabl…
## Problem
FCC had no first-class Pi path, so Pi users had to maintain provider
configuration themselves. FCC's installers and ownership docs also
covered only Claude Code and Codex.
## Changes
| Before | After |
| --- | --- |
| Pi required persistent user-managed provider configuration. | `fcc-pi`
registers an ephemeral FCC provider from the live model catalog and
leaves Pi-owned state untouched. |
| Client launchers normalized blank proxy authentication separately. |
Claude, Codex, and Pi share one neutral proxy-auth policy. |
| FCC installers and uninstallers did not account for Pi. | Installers
delegate missing Pi setup to its official platform installer, while
uninstallers remove only `fcc-pi` and preserve native Pi. |
| Pi compatibility had no executable FCC contract. | Deterministic
launcher and lifecycle coverage plus a real Pi 0.80.6 smoke verify model
discovery and `/v1/messages` end to end. |
<!-- greptile_comment -->
<details open><summary><h3>Greptile Summary</h3></su…
## Problem
FCC required Git solely to fetch its source from GitHub. Customers had
to install an unrelated prerequisite before running an otherwise
self-contained installer.
## Changes
| Before | After |
| --- | --- |
| Installers fetched FCC through a mutable `git+` repository URL. |
Installers fetch the same visible `main` source through GitHub's
generated ZIP archive. |
| Git had to exist before either installer could continue. | FCC
installation has no Git dependency or Git-specific branch. |
| The unnamed source requirement relied on Git metadata. | Every base
and voice variant uses a named direct-archive requirement. |
| Reinstallation relied on Git to discover the current branch head. |
`--refresh-package free-claude-code` fetches the current archive on
every rerun. |
| Installer tests provisioned a fake Git executable. | Windows and Linux
scenarios pass with no Git executable and verify archive and voice
specifications. |
| The README described installer internals and a manua…
Make installers native, fail-fast, and verifiable (#1086)
## Problem
The install and uninstall scripts mixed tool ownership, relied on npm
and package-manager detection, and could report success after native
commands or FCC removal failed. Users could be left without runnable FCC
commands or lose `~/.fcc` while the FCC tool remained. Fixes #547, #753,
#908, #942, #952, #1078, and #1080.
## Changes
| Before | After |
| --- | --- |
| Missing Claude Code and Codex were installed through global npm. |
Missing clients use their official native installers without requiring
Node.js or npm. |
| Existing uv installations were updated through package-manager
detection. | Compatible uv installations are preserved; missing or
obsolete uv uses Astral's standalone installer. |
| Python 3.14 was installed as a separate step. | `uv tool install
--python 3.14.0` owns Python selection and FCC installation together. |
| PowerShell relied on `$ErrorActionPreference` and process metadata. |
Native exits are checked explicitly and the PowerShell host resolves
t…
## Problem
Python 3.14 provides native lazy annotations, but the codebase still
relied on legacy future annotation imports. Those imports also made
type-only import cycles easier to hide instead of fixing ownership
boundaries.
## Changes
| Before | After |
| --- | --- |
| Python files used `from __future__ import annotations`. | Python files
rely on Python 3.14 native lazy annotations. |
| Some runtime modules used `TYPE_CHECKING` or local imports for
required dependencies. | Runtime modules use top-level owner-module
imports with explicit boundaries. |
| Local and GitHub guardrails only rejected type ignore suppressions. |
Local and GitHub guardrails reject type ignore suppressions and legacy
future annotation imports. |
| Agent docs only documented the no-type-ignore rule. | Agent docs
document the Python 3.14 annotation and import-boundary rules. |
<!-- greptile_comment -->
<details open><summary><h3>Greptile Summary</h3></summary>
This PR moves the codebase to Python 3.14 nat…