feat(server): rename built-in models from settings

[t3dotgg]

There was no way to change the display name of a built-in model. Provider names could be overridden (providerInstances.<id>.displayName), but a customModels entry that reused a built-in slug was silently dropped.

Now a named customModels entry whose slug matches a built-in renames that model on the server. Every client (web, desktop, mobile) gets the new name from the provider snapshot.

"providerInstances": {
  "codex": {
    "driver": "codex",
    "config": { "customModels": [{ "slug": "gpt-5.5", "name": "Team GPT" }] }
  }
}

• providerModelsFromSettings applies the rename and drops the built-in shortName so compact UI does not show the old name. Codex now uses this helper instead of its own copy.
• Applies to every provider that merges custom models: Codex, Claude, Cursor, Grok, OpenCode, Muse, Pi, ACP. Antigravity has no custom models.
• The settings card no longer shows a duplicate custom row for an override. The settings file is the way in and the way out.
• Added a user doc example and one focused test.

🤖 Generated with Claude Code (Claude Opus 5.5)

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR adds an opt-in capability for renaming built-in model labels across provider snapshots and clients, with limited implementation scope and no product-default or sensitive-data changes. Because it modifies shared provider infrastructure and introduces cross-provider user-visible behavior in areas historically maintained by another contributor, human review is recommended.

^{You can add or adjust custom eligibility rules. Learn more.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	5.0 KiB	5.0 KiB	0 B (0.0%)	6.8 KiB	✅
Codex	Thread snapshot wire	3.8 KiB	3.8 KiB	0 B (0.0%)	4.9 KiB	✅
Codex	Live turn WebSocket wire	1.2 KiB	1.2 KiB	0 B (0.0%)	2.0 KiB	✅
Codex	Live turn WebSocket decoded	20.9 KiB	20.9 KiB	0 B (0.0%)	29.3 KiB	✅
Codex	Live turn messages	2	2	0 (0.0%)	8	✅
Claude	Total thread wire	5.0 KiB	5.0 KiB	+24 B (+0.5%)	6.8 KiB	✅
Claude	Thread snapshot wire	3.8 KiB	3.8 KiB	0 B (0.0%)	4.9 KiB	✅
Claude	Live turn WebSocket wire	1.2 KiB	1.2 KiB	+24 B (+2.0%)	2.0 KiB	✅
Claude	Live turn WebSocket decoded	21.2 KiB	21.2 KiB	+41 B (+0.2%)	29.3 KiB	✅
Claude	Live turn messages	1	2	+1 (+100.0%)	8	✅

Baseline: a3c4e9e · PR result: 10ef9b6 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 108.5 KiB
• Claude decoded thread snapshot: 108.8 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Path: .coderabbit.config.ts
• Review profile: CHILL
• Plan: Team
• Run ID: b68cdf32-ad3d-4f7b-b518-0b5aac06112a

📥 Commits

Reviewing files that changed from the base of the PR and between a3c4e9e and 10ef9b6.

📒 Files selected for processing (5)

• apps/server/src/provider/CodexProvider.ts
• apps/web/src/components/settings/ProviderInstanceCard.tsx
• docs/user/composer.md
• packages/provider-core/src/server/snapshotProbe.test.ts
• packages/provider-core/src/server/snapshotProbe.ts

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.

📝 Walkthrough

Walkthrough

Custom model settings can rename built-in models that have matching slugs. The Codex provider now uses shared model composition, and the settings display omits matching custom entries. Documentation and a test describe and verify the updated behavior.

Changes

Custom model naming

Layer / File(s)	Summary
Built-in model name overrides packages/provider-core/src/server/snapshotProbe.ts, packages/provider-core/src/server/snapshotProbe.test.ts	providerModelsFromSettings accepts nullable fallback capabilities and applies a differing custom name to a built-in model with the same slug. The override removes the built-in model’s shortName. The test checks the name, custom status, and capabilities.
Provider and settings integration apps/server/src/provider/CodexProvider.ts, apps/web/src/components/settings/ProviderInstanceCard.tsx, docs/user/composer.md	The Codex provider delegates model composition to the shared helper. The settings display excludes custom entries whose slugs match built-in models. The documentation shows a settings.json example for renaming a built-in model.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~12 minutes

Change: Feature

Suggested reviewers: juliusmarminge

Merge Risk: ⚪ Minimal · up to 10ef9

The reported naming concern does not require a change. No merge-blocking issue is established.

Pre-merge checks · 3 · 1

Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check		The description clearly explains the problem and implementation, but it does not follow the required section structure. It omits scope and approval details, focused verification results, and any UI ev…	Add the required Problem, Change, Scope and approval, and Verification sections. Link the triaged issue or maintainer approval, or explain why approval is not required. Document the exact tests or manual checks run and their observed result…

Passed checks (3 passed)

Check name	Status	Explanation
Title check		The title clearly and concisely describes the main change: renaming built-in models through server settings.
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Description check

Explanation

The description clearly explains the problem and implementation, but it does not follow the required section structure. It omits scope and approval details, focused verification results, and any UI evidence for the settings-card change.

Resolution

Add the required Problem, Change, Scope and approval, and Verification sections. Link the triaged issue or maintainer approval, or explain why approval is not required. Document the exact tests or manual checks run and their observed results. Include before and after screenshots for the UI change, if applicable.

• Fix all pre-merge checks with AI

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}