codex-doctorlisted

# Codex Doctor Analyze Codex usage from local session data, separate evidence from interpretation, and turn recurring patterns into small workflow changes. ## Choose the analysis mode - Use telemetry-only mode by default. It is local, deterministic, strict-privacy, and does not invoke a model. - Use AI mode only when the user explicitly asks for AI diagnosis or a deeper interpretation. It makes one compact `codex-cli` diagnosis call and may consume Codex usage. - Never use the `openai` provider unless the user explicitly requests it and provides the required authorization. Do not use paid production APIs, production credentials, or real user data for this analysis. ## Locate and run the analyzer 1. Resolve the analyzer directory in this order: - a path supplied by the user; - `CODEX_DOCTOR_DIR` if set; - the current workspace when it contains `bin/codex-insights.js` and the Codex Doctor package; - a narrowly scoped local path the user has already mentioned. 2. If no analyzer directory is available, ask for its path. Do not scan the whole home directory or install dependencies without a reason. 3. Run from the analyzer directory and write output and, when needed, cache data to dedicated temporary or user-selected directories. If the default cache location is not writable, pass an explicit `--cache-dir`. Telemetry-only example: ```bash node ./bin/codex-insights.js report \ --telemetry-only \ --days 14 \ --limit 20 \ --no-open \ --cache-dir <report-d