@christiandoxa/prodex 0.146.0 → 0.147.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +4 -2
  2. package/package.json +7 -7
package/README.md CHANGED
@@ -739,7 +739,7 @@ GEMINI_API_KEY=... prodex s --provider gemini --model gemini-2.5-pro
739
739
  prodex s --provider gemini --model gemini-2.5-pro --api-key "$GEMINI_API_KEY"
740
740
  ```
741
741
 
742
- Without `--api-key`, Prodex uses the Google OAuth profile created by `prodex login` and routes through Google's Code Assist Gemini endpoint. With `--api-key`, or `GEMINI_API_KEY(S)` / `GOOGLE_API_KEY(S)`, Prodex routes through the public Gemini API. Plural key env vars may be comma-, semicolon-, or newline-separated and rotate before commit on auth/quota/rate/temporary failures. The default model is `gemini-2.5-pro`, matching Gemini CLI's current default, and the injected catalog exposes Gemini reasoning efforts with the 2.5 default thinking budget of 8192. `prodex quota` reads the same Google OAuth profile and fetches Gemini Code Assist `retrieveUserQuota` bucket data. The Super optional tools still run as local Codex overlays on this path: Prodex maps Codex/MCP tool schemas to Gemini function declarations, honors `auto` / `none` / `required` tool-choice modes, and preserves Gemini thought signatures across tool-call followups.
742
+ Without `--api-key`, Prodex uses the Google OAuth profile created by `prodex login` and routes through Google's Code Assist Gemini endpoint. Google login verifies Code Assist readiness before creating or updating the profile, and may open a second browser page if Google requires account verification. With `--api-key`, or `GEMINI_API_KEY(S)` / `GOOGLE_API_KEY(S)`, Prodex routes through the public Gemini API. Plural key env vars may be comma-, semicolon-, or newline-separated and rotate before commit on auth/quota/rate/temporary failures. The default model is `gemini-2.5-pro`, matching Gemini CLI's current default, and the injected catalog exposes Gemini reasoning efforts with the 2.5 default thinking budget of 8192. `prodex quota` reads the same Google OAuth profile and fetches Gemini Code Assist `retrieveUserQuota` bucket data. The Super optional tools still run as local Codex overlays on this path: Prodex maps Codex/MCP tool schemas to Gemini function declarations, honors `auto` / `none` / `required` tool-choice modes, and preserves Gemini thought signatures across tool-call followups.
743
743
 
744
744
  Before launch, Super asks whether to add Presidio redaction. Empty input or `n` keeps Presidio disabled; answer `y` or pass `--presidio` to add the `presidio` prefix. Use `--no-presidio` to make the disabled choice explicit for non-interactive use.
745
745
 
@@ -898,7 +898,9 @@ On Unix-like systems, this is usually:
898
898
  ~/.codex
899
899
  ```
900
900
 
901
- In practice, profile `history.jsonl`, `sessions`, `config.toml`, `environments.toml`, plugins, skills, app-server plugin state, memory-extension state, and Codex runtime SQLite files such as `state_*`, `goals_*`, `logs_*`, and `memories_*` link to the same Codex home that direct Codex uses.
901
+ In practice, profile `history.jsonl`, `sessions`, `archived_sessions`, `config.toml`, `managed_config.toml`, `environments.toml`, plugins, skills, app-server plugin state, memory-extension state, remote-control enrollment, and Codex runtime SQLite files such as `state_*`, `goals_*`, `logs_*`, and `memories_*` link to the same Codex home that direct Codex uses.
902
+
903
+ Codex cloud-managed config bundle caches are identity/account scoped and remain profile-local. System-level Codex requirements and managed config files remain owned by upstream Codex and the operating system.
902
904
 
903
905
  Prodex does not synthesize legacy Codex `[profiles.*]` behavior. File-based Codex profile config selected by `--profile` stays in shared Codex state, while Prodex-owned account selection remains in Prodex profile metadata.
904
906
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@christiandoxa/prodex",
3
- "version": "0.146.0",
3
+ "version": "0.147.0",
4
4
  "description": "Safe multi-account auto-rotate for Codex CLI with isolated CODEX_HOME profiles",
5
5
  "license": "Apache-2.0",
6
6
  "bin": {
@@ -16,12 +16,12 @@
16
16
  "@openai/codex": "latest"
17
17
  },
18
18
  "optionalDependencies": {
19
- "@christiandoxa/prodex-linux-x64": "0.146.0",
20
- "@christiandoxa/prodex-linux-arm64": "0.146.0",
21
- "@christiandoxa/prodex-darwin-x64": "0.146.0",
22
- "@christiandoxa/prodex-darwin-arm64": "0.146.0",
23
- "@christiandoxa/prodex-win32-x64": "0.146.0",
24
- "@christiandoxa/prodex-win32-arm64": "0.146.0"
19
+ "@christiandoxa/prodex-linux-x64": "0.147.0",
20
+ "@christiandoxa/prodex-linux-arm64": "0.147.0",
21
+ "@christiandoxa/prodex-darwin-x64": "0.147.0",
22
+ "@christiandoxa/prodex-darwin-arm64": "0.147.0",
23
+ "@christiandoxa/prodex-win32-x64": "0.147.0",
24
+ "@christiandoxa/prodex-win32-arm64": "0.147.0"
25
25
  },
26
26
  "engines": {
27
27
  "node": ">=18"