@christiandoxa/prodex 0.192.0 → 0.194.0

package/README.md

@@ -48,7 +48,6 @@ You need at least one logged-in Prodex profile.
 |---|---|
 | Codex CLI | `prodex`, `prodex run`, `prodex caveman`, `prodex super` |
 | Claude Code | `prodex claude` |
-| Claude-Mem | `mem` variants |
 | RTK | `rtk` variants and `prodex s` / `prodex super` |
 
 </details>
@@ -144,7 +143,7 @@ If you install from source, make sure the `codex` binary in your `PATH` is alrea
 
 ## Optional tools
 
-`prodex` can run without Claude-Mem, RTK, SQZ, token-savior, claw-compactor, or Presidio.
+`prodex` can run without RTK, SQZ, token-savior, claw-compactor, or Presidio. `prodex-memory` is built in and is enabled by Super mode as a local-first memory MCP server.
 
 Install them only if you want to use commands such as:
 
@@ -152,46 +151,84 @@ Install them only if you want to use commands such as:
 <summary>Optional tool commands</summary>
 
 ```bash
-prodex caveman mem
-prodex caveman mem rtk
 prodex rtk
 prodex sqz
 prodex tokensavior
 prodex clawcompactor
+prodex mem
+prodex s doctor
 prodex presidio doctor
 prodex presidio redact --text "My phone is 212-555-1234"
 prodex gateway --provider gemini
 prodex s
 prodex super
-prodex claude mem
-prodex claude caveman mem
 ```
 
 </details>
 
 <details>
-<summary>Install Claude-Mem</summary>
-
-Claude-Mem is used by the `mem` variants.
-
-Recommended install:
+<summary>Prodex memory mode</summary>
 
 ```bash
-npx claude-mem install
+prodex s
+prodex super
+prodex caveman mem
+prodex s doctor
 ```
 
-Then follow the interactive prompts.
+`prodex s` runs Codex with the built-in `prodex-memory` MCP server registered in the temporary overlay `CODEX_HOME`.
+The base Codex profile stays unchanged; memory state is owned by Prodex.
+Use `prodex caveman mem` when you want only Caveman plus the local memory MCP overlay, without the full Super stack.
 
-You can also install it from inside Claude Code:
+`prodex-memory` provides Mem0-style local memory without Mem0 Cloud, Mem0 CLI, or `MEM0_API_KEY`.
+By default it stores memories in a SQLite database under `PRODEX_HOME`:
 
 ```text
-/plugin marketplace add thedotmack/claude-mem
-/plugin install claude-mem
+$PRODEX_HOME/memory/prodex-memory.sqlite
 ```
 
-After installation, restart Claude Code or your coding CLI.
+`prodex s` asks the Presidio prompt first, then asks whether to use managed Mem0 memory. Empty input or `n` keeps the lightweight SQLite backend. Answer `y` or pass `--mem0` to start the managed Mem0 OSS Docker server. Use `--no-mem0` to skip that prompt non-interactively.
+
+The default SQLite path remains the fastest OOTB memory path:
+
+- no Mem0 Cloud endpoint
+- no `MEM0_API_KEY`
+- no user-visible Mem0 auth
+- local SQLite storage
+- MCP tools exposed as `prodex-memory`
+
+Managed Mem0 mode requires Docker Compose (`docker compose` or `docker-compose`). It does not require a Mem0 Cloud token or a user-supplied provider API key for the default memory path. OpenAI-compatible API-key profiles, `--url` local providers, and supported provider bridges can provide richer upstream LLM/embedding behavior; otherwise Prodex falls back to local embeddings for Mem0.
+
+<details>
+<summary>Managed Mem0 internals</summary>
+
+Managed Mem0 mode is still local-first:
 
-> Do not use `npm install -g claude-mem` as the main install method. That installs the SDK/library only; it does not register the plugin hooks or start the worker service.
+- Prodex clones `https://github.com/mem0ai/mem0` under `$PRODEX_HOME/mem0` if needed.
+- Prodex writes the Mem0 server `.env` with generated local `ADMIN_API_KEY`, `JWT_SECRET`, and Postgres password.
+- Mem0 auth stays enabled; Prodex keeps the local API key internal and injects it only into the temporary MCP overlay.
+- Mem0 receives `OPENAI_BASE_URL=http://host.docker.internal:<prodex-gateway-port>/v1`.
+- Mem0 receives an internal Prodex gateway bearer token as `OPENAI_API_KEY`.
+- The gateway selects an efficient memory LLM when available, preferring nano/mini models, and defaults embeddings to `text-embedding-3-small`.
+- If no upstream API-key profile is available, the internal gateway still serves deterministic local embeddings for Mem0 and disables generation endpoints for that Mem0-only gateway.
+- Prodex writes raw/no-infer memories by default, so the managed path does not spend LLM quota for memory extraction.
+- No Mem0 Cloud endpoint and no user-managed `MEM0_API_KEY` are used.
+
+</details>
+
+<details>
+<summary>Memory diagnostics</summary>
+
+Use `prodex s doctor` to verify that the built-in memory store can be opened before launching Codex. The hidden MCP server can also be launched directly for diagnostics:
+
+```bash
+prodex s doctor
+prodex __memory-mcp --store /tmp/prodex-memory.sqlite
+```
+
+Mem0 Cloud's official MCP endpoint is intentionally not part of Prodex Super's default path. Configure it manually only when you explicitly want Mem0 Platform auth and are willing to manage `MEM0_API_KEY` yourself.
+
+</details>
 
 </details>
 
@@ -401,6 +438,8 @@ docker run -d --name presidio-analyzer -p 5002:3000 mcr.microsoft.com/presidio-a
 docker run -d --name presidio-anonymizer -p 5001:3000 mcr.microsoft.com/presidio-anonymizer:latest
 ```
 
+When Super mode opts into Presidio and the default local endpoints are not healthy, Prodex now tries to start these Docker containers automatically before launching Codex. Set `PRODEX_PRESIDIO_AUTO_START=0` to disable that best-effort auto-start and only use the configured endpoints.
+
 Source checkout with Compose:
 
 ```bash
@@ -538,7 +577,6 @@ This is the mode I tune and use myself every day.
 It combines:
 
 - Caveman mode
-- Claude-Mem transcript watching
 - RTK shell-command guidance
 - full-access launch mode
 - Smart Context Autopilot in the runtime proxy
@@ -553,33 +591,40 @@ prodex s expose
 `prodex super` expands to:
 
 ```bash
-prodex caveman mem rtk sqz tokensavior clawcompactor --full-access
+prodex caveman rtk sqz tokensavior clawcompactor mem --full-access
 ```
 
 Before launch, Super asks whether to add Presidio redaction. Empty input or `n` keeps the expansion above. If you answer `y`, it is equivalent to:
 
 ```bash
-prodex caveman mem rtk sqz tokensavior clawcompactor presidio --full-access
+prodex caveman rtk sqz tokensavior clawcompactor mem presidio --full-access
 ```
 
 Use `prodex super --presidio` to enable Presidio without prompting, or `prodex super --no-presidio` to skip the prompt and keep Presidio disabled. Presidio enables runtime request-body and WebSocket text redaction through local Presidio for the session. The runtime uses `presidio.toml` endpoints when configured, falls back to `http://localhost:5002` and `http://localhost:5001`, and honors `fail_mode = "open"` or `"closed"`.
 
+After the Presidio prompt, Super asks whether to use managed Mem0 memory. Empty input or `n` keeps the built-in SQLite-backed `prodex-memory` MCP backend. Answer `y` or pass `--mem0` to start the managed Mem0 OSS Docker server, route its OpenAI-compatible calls through a session-local Prodex gateway, and inject the local Mem0 API key into the temporary Codex MCP config. Use `--no-mem0` to skip the prompt. This path does not use Mem0 Cloud or `MEM0_API_KEY`; Docker Compose is required, and Prodex falls back to local embeddings when no upstream provider API key is available.
+
+Super prints prelaunch progress for runtime proxy setup, Presidio auto-start/checks, and managed Mem0 Docker startup. The output happens before Codex starts; runtime notices still go to logs once the TUI is running.
+
 Full access maps to Codex's sandbox-bypass launch flag. Use it only when you intentionally want Codex to run without the normal approval and sandbox protections.
 
+Use `prodex s doctor` to inspect the Super optimizer stack without launching Codex. Add `--json` for machine-readable output, `--strict` to exit non-zero when any optimizer check is unavailable, and `--presidio` to include local Presidio Analyzer/Anonymizer health checks. `prodex s --dry-run` also prints the same optimizer matrix for the launch preview.
+
 Use `prodex s expose` when you need to reach the live Super terminal from a browser. Prodex starts a local PTY bridge protected by a high-entropy access token, launches `cloudflared tunnel --protocol http2 --url ...` when `cloudflared` is available, and prints both the loopback and Cloudflare quick-tunnel URLs. The browser tab can close without stopping the session; reopening the same token URL reconnects to the existing PTY and replays recent scrollback. Add `--no-tunnel` for local-only access, `--max-clients N` to cap simultaneous browsers, or `--command 'prodex s --no-presidio'` to choose the initial terminal command.
 
-Super's built-in optimization stack is deliberately local and deterministic. It preloads the existing Caveman and Claude-Mem pieces, exposes an overlay `rtk` wrapper plus RTK auto-wrappers for common noisy commands when RTK is installed, auto-registers `sqz-mcp` and `token-savior` MCP servers when those binaries are already on `PATH` or in a managed `prodex-optimizers` checkout, exposes `sqz` and `claw-compactor` wrappers when those commands/checkouts are discoverable, invokes a trusted one-shot `prodex-claw-compactor-sessionstart` SessionStart benchmark probe when Claw-Compactor is available, falls back to a temporary shadow `MEMORY.md` when the workspace has no Markdown memory files, then uses Smart Context Autopilot through a dedicated runtime proxy for lower-token request shaping. The probe delegates to `prodex-claw-compactor-auto "$(pwd)"` and uses a marker under `CODEX_HOME` so Codex conversation restarts do not replay it. Presidio redaction is added to that proxy only when you opt in at the prompt. Prodex passes token-savior cache and stats paths under `PRODEX_HOME` (default `~/.prodex`) so compatible token-savior versions keep generated state out of worktrees.
+Super's built-in optimization stack is deliberately local and deterministic. It preloads Caveman, exposes an overlay `rtk` wrapper plus RTK auto-wrappers for common noisy commands when RTK is installed, auto-registers `sqz-mcp`, `token-savior`, and built-in `prodex-memory` MCP servers, exposes `sqz` and `claw-compactor` wrappers when those commands/checkouts are discoverable, invokes a trusted one-shot `prodex-claw-compactor-sessionstart` SessionStart benchmark probe when Claw-Compactor is available, falls back to a temporary shadow `MEMORY.md` when the workspace has no Markdown memory files, then uses Smart Context Autopilot through a dedicated runtime proxy for lower-token request shaping. The probe delegates to `prodex-claw-compactor-auto "$(pwd)"` and uses a marker under `CODEX_HOME` so Codex conversation restarts do not replay it. Presidio redaction is added to that proxy only when you opt in at the prompt. Prodex passes token-savior cache, stats paths, and local memory under `PRODEX_HOME` (default `~/.prodex`) so compatible token-savior versions and memory state stay out of worktrees.
 
 Super instructs Codex to use the whole local optimizer stack where it fits the task, not just RTK:
 
-- Claude-Mem handles prior-session/project recall through the active Prodex session watch.
 - RTK works upstream/input-side. Use visible `rtk <cmd>` for noisy terminal commands before their output enters the model context, such as `git diff`, `cargo test`, `npm test`, build logs, and package-manager output. Prodex also auto-wraps common noisy commands as a fallback when RTK is installed, but that fallback does not make the TUI show an `rtk` prefix.
 - SQZ works downstream/context-side through the auto-registered `prodex-sqz` MCP server. Use it for repeated workspace reads, large text blobs, long command outputs that need reuse, and long-session context compression instead of emitting the same full content again.
 - token-savior handles symbol lookup, caller/context navigation, duplicate/dead-code checks, and API-impact searches before broad source reads.
 - claw-compactor handles workspace-level summary or benchmark requests through `prodex-claw-compactor` / `prodex-claw-compactor-auto`; treat its output as overview context and reread exact source before edits.
+- prodex-memory provides local Mem0-style memory through the default SQLite backend, or through managed Mem0 OSS Docker when you opt in with the Super prompt or `--mem0`; neither path uses Mem0 Cloud auth or `MEM0_API_KEY`.
 - Presidio stays optional and only runs when you opt in with the Super prompt or `--presidio`.
 
 Managed optimizer checkouts are discovered from `PRODEX_OPTIMIZERS_HOME`, `$XDG_DATA_HOME/prodex-optimizers`, then `~/.local/share/prodex-optimizers`.
+The generated `SUPER_OPTIMIZERS.md` overlay includes an `Available Now` section so the model can see which MCP servers and wrappers were actually discovered for that session.
 
 </details>
 
@@ -702,7 +747,7 @@ unless Prodex explicitly owns that command.
 |---|---|---|
 | Normal Codex | `prodex` or `prodex run` | Managed Codex launch with profile selection and quota routing. |
 | Caveman | `prodex caveman` | Runs Codex with a temporary overlay `CODEX_HOME`. |
-| Super | `prodex s` or `prodex super` | Daily mode with Caveman, Claude-Mem, RTK guidance, full access, and deterministic/local token optimizations. |
+| Super | `prodex s` or `prodex super` | Daily mode with Caveman, RTK guidance, full access, and deterministic/local token optimizations. |
 | Claude Code | `prodex claude` | Runs Claude Code through Prodex-managed state. |
 
 <details>
@@ -722,13 +767,14 @@ prodex exec "review this repo"
 
 ```bash
 prodex caveman
-prodex caveman mem
-prodex caveman mem rtk
 prodex rtk
 prodex sqz
 prodex tokensavior
 prodex clawcompactor
+prodex mem
 prodex caveman --dry-run
+prodex s doctor
+prodex s doctor --json --strict
 prodex caveman --profile main
 prodex caveman exec "review this repo in caveman mode"
 prodex caveman 019c9e3d-45a0-7ad0-a6ee-b194ac2d44f9
@@ -736,9 +782,7 @@ prodex caveman 019c9e3d-45a0-7ad0-a6ee-b194ac2d44f9
 
 `prodex caveman` runs Codex with a temporary overlay `CODEX_HOME`, so the base profile home stays unchanged after the session ends.
 
-If you use the `mem` variant, Prodex points an existing Claude-Mem Codex setup to the active Prodex session path instead of the default `~/.codex/sessions`.
-
-Add optimizer prefixes before Codex args when you want Prodex to inject a specific launch overlay for that session: `mem`, `rtk`, `sqz`, `tokensavior`, `clawcompactor`, or `presidio`. Top-level shortcuts such as `prodex rtk` and `prodex sqz` map to `prodex caveman <prefix>`.
+Add optimizer prefixes before Codex args when you want Prodex to inject a specific launch overlay for that session: `rtk`, `sqz`, `tokensavior`, `clawcompactor`, `mem`, or `presidio`. Top-level shortcuts such as `prodex rtk`, `prodex sqz`, and `prodex mem` map to `prodex caveman <prefix>`.
 
 RTK is still an external binary. Install it separately if `rtk gain` is unavailable.
 
@@ -763,21 +807,7 @@ prodex super 019c9e3d-45a0-7ad0-a6ee-b194ac2d44f9
 
 `prodex s` is the short alias for `prodex super`.
 
-This is my daily mode. It is the path I keep tuning for normal work: Caveman enabled, Claude-Mem transcript watching enabled, RTK guidance enabled, full access available, and context handling handled by the runtime proxy.
-
-Super mode uses Prodex's slim Claude-Mem Codex schema by default to avoid storing full assistant/tool output in recall context.
-
-Use `--mem-super-slim` to store prompt summaries/references instead of full prompt bodies:
-
-```bash
-prodex super --mem-super-slim
-```
-
-Use `--mem-full` when you need the full transcript schema:
-
-```bash
-prodex super --mem-full
-```
+This is my daily mode. It is the path I keep tuning for normal work: Caveman enabled, RTK guidance enabled, full access available, and context handling handled by the runtime proxy.
 
 Super also enables Smart Context Autopilot in the runtime proxy.
 
@@ -837,7 +867,7 @@ Gemini Live realtime websocket translation remains available for compatible call
 
 Run `npm run test:gemini-schema` after changing Gemini request, response, SSE, semantic compact, exact-output, tool-schema, or Live translation. Run `PRODEX_LIVE_GEMINI=1 npm run test:gemini-live` for a credentialed end-to-end Gemini adapter smoke request; set `PRODEX_BIN` or `PRODEX_LIVE_GEMINI_MODEL` to override the binary or model. Add `PRODEX_LIVE_GEMINI_EXTENDED=1` for command-output-only, file edit, `apply_patch`, reference-repo clone/inspection, optional-tool update discipline, semantic compact, and explicit `exec resume` checks. Add `PRODEX_LIVE_GEMINI_MCP=1` and/or `PRODEX_LIVE_GEMINI_MULTIMODAL=1` when the local environment should also exercise MCP and image-input paths.
 
-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.
+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. Super then asks whether to use managed Mem0 memory. Empty input or `n` keeps the built-in SQLite memory backend; answer `y` or pass `--mem0` to start the managed Mem0 OSS Docker server and route its OpenAI-compatible calls through Prodex gateway. Use `--no-mem0` to skip that prompt.
 
 Prodex now supports multi-language Presidio redaction, including automatic detection and multi-language merging. The runtime uses `presidio.toml` endpoints and language configuration when available, falling back to `http://localhost:5002` and `http://localhost:5001` for Analyzer/Anonymizer URLs, and English (`en`) for language if not specified. It honors `fail_mode = "open"` or `"closed"`.
 
@@ -869,11 +899,8 @@ Managed optimizer checkouts are discovered from `PRODEX_OPTIMIZERS_HOME`, `$XDG_
 
 ```bash
 prodex claude -- -p "summarize this repo"
-prodex claude mem -- -p "recall past work on this repo"
 prodex claude caveman
-prodex claude caveman mem
 prodex claude caveman -- -p "summarize this repo briefly"
-prodex claude caveman mem -- -p "summarize this repo briefly"
 prodex claude --profile second caveman -- -p "review the latest diff briefly"
 prodex claude --profile second -- -p --output-format json "show the latest diff"
 ```
@@ -882,8 +909,6 @@ prodex claude --profile second -- -p --output-format json "show the latest diff"
 
 `prodex claude caveman` enables Caveman for that session while keeping state under the Prodex-managed `CLAUDE_CONFIG_DIR`, not the global `~/.claude`.
 
-`prodex claude caveman mem` combines Caveman and Claude-Mem.
-
 `prodex claude` is only supported with the default OpenAI/Codex provider.
 
 </details>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@christiandoxa/prodex",
-  "version": "0.192.0",
+  "version": "0.194.0",
   "description": "Safe multi-account auto-rotate for Codex CLI with isolated CODEX_HOME profiles",
   "license": "Apache-2.0",
   "bin": {
@@ -16,12 +16,12 @@
     "@openai/codex": "latest"
   },
   "optionalDependencies": {
-    "@christiandoxa/prodex-linux-x64": "0.192.0",
-    "@christiandoxa/prodex-linux-arm64": "0.192.0",
-    "@christiandoxa/prodex-darwin-x64": "0.192.0",
-    "@christiandoxa/prodex-darwin-arm64": "0.192.0",
-    "@christiandoxa/prodex-win32-x64": "0.192.0",
-    "@christiandoxa/prodex-win32-arm64": "0.192.0",
+    "@christiandoxa/prodex-linux-x64": "0.194.0",
+    "@christiandoxa/prodex-linux-arm64": "0.194.0",
+    "@christiandoxa/prodex-darwin-x64": "0.194.0",
+    "@christiandoxa/prodex-darwin-arm64": "0.194.0",
+    "@christiandoxa/prodex-win32-x64": "0.194.0",
+    "@christiandoxa/prodex-win32-arm64": "0.194.0",
     "@openai/codex-linux-x64": "npm:@openai/codex@linux-x64",
     "@openai/codex-linux-arm64": "npm:@openai/codex@linux-arm64",
     "@openai/codex-darwin-x64": "npm:@openai/codex@darwin-x64",