- Use ccsxp if you want the built-in CCS Codex provider shortcut on native
- Codex. Use the saved recipe below if you want plain codex or a personal
- alias like cxp to default to CLIProxy.
-
+ Built-in: Use ccsxp for the CCS provider shortcut.
+
+ Native: Configure the recipe below to use CLIProxy directly with{' '}
+ codex.
+
{CLIPROXY_NATIVE_CODEX_RECIPE}
-
- 1. Save the cliproxy provider in your user config.
-
- 2. Set top-level model_provider to cliproxy.
-
- 3. Export CLIPROXY_API_KEY in your shell before launching native Codex.
-
cliproxy provider in your user config.
+ model_provider to cliproxy.
+ CLIPROXY_API_KEY before launching native Codex.
+ - - {renderTextWithLinks(note)} -
- ))} + {docsReference.notes.length > 0 && ( +Codex docs
diff --git a/ui/src/components/compatible-cli/codex-overview-tab.tsx b/ui/src/components/compatible-cli/codex-overview-tab.tsx index f74cd945..eb73f2eb 100644 --- a/ui/src/components/compatible-cli/codex-overview-tab.tsx +++ b/ui/src/components/compatible-cli/codex-overview-tab.tsx @@ -74,31 +74,23 @@ export function CodexOverviewTab({ diagnostics }: CodexOverviewTabProps) { How Codex works in CCS -Codex is a first-class runtime target in CCS, but it stays runtime-only in v1.
-
- ccs-codex and ccsx launch native Codex against your saved
- native config, while ccsxp is the opinionated shortcut for{' '}
- ccs codex --target codex.
-
- Plain codex or a personal alias like cxp needs{' '}
- model_provider = "cliproxy" plus a matching{' '}
- [model_providers.cliproxy] entry if you want CLIProxy as the saved native
- default.
-
- Built-in openai and oss providers are also valid native
- defaults and do not need a custom [model_providers] stanza.
-
- Saved default targets for API profiles and variants still remain on Claude or Droid. -
-
- CCS-backed Codex launches can apply transient -c overrides and inject
- CCS_CODEX_API_KEY, so effective runtime values may not match this file
- exactly.
-
ccs-codex and ccsx launch
+ native Codex using your saved defaults.
+ ccsxp (or{' '}
+ ccs codex --target codex) uses the CCS provider shortcut.
+ codex use CLIProxy,
+ set model_provider = "cliproxy" and add the recipe below.
+
- There are two supported paths. Use ccsxp if you want the built-in CCS
- Codex provider shortcut. Use the saved recipe below if you want plain{' '}
- codex or a personal alias like cxp to default to
- CLIProxy.
-
+ Two supported paths: +
+ccsxp for the CCS provider
+ shortcut.
+ codex.
+ Saved native Codex recipe
{CLIPROXY_NATIVE_CODEX_RECIPE}
- 1. Save a provider named cliproxy with the base URL and env key
- above.
-
- 2. In Top-level settings, set Default provider{' '}
- to cliproxy.
-
- 3. Export CLIPROXY_API_KEY in your shell before launching native
+
cliproxy with the base URL and env key above.
+ cliproxy.
+ CLIPROXY_API_KEY in your shell before launching native
Codex.
-
-
@@ -320,30 +320,44 @@ export function CodexOverviewTab({ diagnostics }: CodexOverviewTabProps) {
Native Codex runtime
- Use Native Codex runtime CCS Codex provider / bridge
- {supportsManagedRouting ? (
- <>
- Use CCS Codex provider / bridge
+ Unavailable (Codex build lacks ccs-codex, ccsx, or --target codex when
- you want the local Codex CLI to honor your saved native user config.
-
+
+ ccs-codex
+ ccsx
+ --target codex
+ ccsxp or ccs codex --target codex when you want
- the built-in CCS Codex provider on native Codex. That path uses transient
- CCS-managed overrides and is separate from the saved cliproxy{' '}
- recipe above.
- >
- ) : (
- <>
- The CCS Codex provider route is currently unavailable because the detected Codex
- build does not expose --config overrides.
- >
- )}
-
+
+ ccsxp
+ ccs codex --target codex
+ --config support).
+