@bman654/clodex 1.1.0 → 1.2.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 (5) hide show
  1. package/README.md +7 -1
  2. package/dist/cli.js +990 -320
  3. package/dist/cli.js.map +1 -1
  4. package/docs/credential-helpers.md +75 -0
  5. package/package.json +1 -1
package/README.md CHANGED
@@ -214,7 +214,13 @@ clodex --version # version
214
214
  ## Configuration
215
215
 
216
216
  - Config home: `~/.clodex` (override with `CLODEX_HOME`). On first run, config is migrated automatically from a legacy `~/.relay-ai` directory if present; the legacy directory is never modified.
217
- - Credentials live in the OS credential store (Keychain / Windows Credential Manager / Secret Service) under the `clodex` service.
217
+ - The config-home filesystem must support hard links because registry locks are
218
+ published atomically. Keep `CLODEX_HOME` on a local filesystem rather than
219
+ FAT, exFAT, or a network mount that rejects hard links. An abrupt process kill
220
+ during lock publication can leave a `providers.json.lock.*.tmp` file; it does
221
+ not block later lock acquisition and can be removed when no Clodex process is
222
+ running.
223
+ - Credentials live in the OS credential store (Keychain / Windows Credential Manager / Secret Service) under the `clodex` service. Set `CLODEX_CREDENTIAL_HELPER` to an absolute executable path to use an external secure store instead; see [credential helpers](docs/credential-helpers.md).
218
224
  - `CLODEX_CLAUDE_PATH` overrides Claude Code binary discovery.
219
225
  - **Outbound proxy:** when `HTTP_PROXY`/`HTTPS_PROXY` (and optionally `NO_PROXY`) are set in clodex's environment, all clodex-originated network calls honor them — OAuth sign-in and token refresh, model-list and models.dev refreshes, upstream OpenAI API calls, and the ChatGPT/Codex OAuth WebSocket transport (tunneled via HTTP CONNECT).
220
226