## Problem
The Codex App cannot discover FCC provider/model slugs because it loads
a local model catalog at startup instead of querying FCC's `/v1/models`
endpoint. Users can configure FCC as a Responses provider, but its
native model picker remains incomplete. Fixes #1260.
## Changes
| Before | After |
| --- | --- |
| FCC generated the Codex catalog only when `fcc-codex` launched. | FCC
synchronizes the catalog from its canonical model lifecycle for
independently launched Codex clients. |
| Startup could leave a configured Codex App without a catalog file. |
Startup creates a missing catalog after routed-provider warming and
preserves an existing last-known-good catalog. |
| Every catalog publication replaced the file. | Identical content is
skipped and changed content is replaced atomically. |
| Catalog filesystem failures could escape a direct writer call. |
Runtime publication is fail-open and logs only the exception type. |
| Codex App setup was undocumented. | The README docum…
Isolate nested Codex launches from parent task context (#1055)
## Problem\n\nNested Codex launches inherited the parent task's thread,
shell, permission, and origin identity. This could attach a new client
or compatibility probe to the parent task, hang startup, or decode probe
output with the wrong Windows locale.\n\n## Changes\n\n| Before | After
|\n| --- | --- |\n| cc-codex forwarded parent-only Codex task context. |
cc-codex removes parent-only task context while preserving user
configuration such as CODEX_HOME. |\n| The installed-Codex probe
inherited the parent task and user Codex home. | The probe runs with a
standalone task identity and isolated Codex home. |\n| The probe decoded
output with the platform default encoding. | The probe decodes output as
UTF-8 with safe replacement. |
<!-- greptile_comment -->
<details open><summary><h3>Greptile Summary</h3></summary>
This PR isolates nested Codex launches from parent task identity. The
main changes are:
- Strips Codex thread, shell, permission, and origin context from
launched child envi…
Move runtime packages under src namespace (#1029)
## 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…
## 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…
Refactor CLI surfaces around launchers and managed Claude (#861)
## Problem
The CLI package preserved a generic adapter layer and managed Codex
parser path that did not match the supported customer workflows.
Messaging runs Claude Code sessions, while Codex is supported through
`fcc-codex` and extensions.
## Changes
| Before | After |
| --- | --- |
| `fcc-claude` and `fcc-codex` shared generic adapter plumbing. |
`fcc-claude` and `fcc-codex` use explicit launcher modules. |
| Messaging depended on a generic CLI session abstraction. | Messaging
depends on managed Claude Code sessions. |
| Codex catalog generation lived as a top-level CLI helper. | Codex
catalog generation lives under the Codex launcher owner. |
| Tests asserted deleted internal adapter shapes. | Tests assert
launcher, managed-Claude, and customer-surface behavior. |