clawdi 0.11.0 → 0.12.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.
- package/README.md +11 -5
- package/dist/index.js +326 -317
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -143,12 +143,12 @@ AI Provider metadata lives in `~/.clawdi/ai-providers/catalog.json`; API keys do
|
|
|
143
143
|
Apply provider config explicitly, with a dry run first:
|
|
144
144
|
|
|
145
145
|
```bash
|
|
146
|
-
clawdi ai-provider apply
|
|
147
|
-
clawdi ai-provider apply
|
|
146
|
+
clawdi ai-provider apply openai-main --dry-run
|
|
147
|
+
clawdi ai-provider apply openai-main
|
|
148
148
|
codex --profile clawdi-ai-provider
|
|
149
149
|
|
|
150
|
-
clawdi ai-provider apply --
|
|
151
|
-
clawdi ai-provider apply --
|
|
150
|
+
clawdi ai-provider apply openai-main --target hermes --dry-run
|
|
151
|
+
clawdi ai-provider apply openai-main --target openclaw --dry-run
|
|
152
152
|
```
|
|
153
153
|
|
|
154
154
|
Codex OAuth is managed through the AI Provider surface:
|
|
@@ -159,9 +159,15 @@ clawdi ai-provider add openai-codex \
|
|
|
159
159
|
--default-model gpt-5-codex \
|
|
160
160
|
--auth agent:codex/default
|
|
161
161
|
clawdi ai-provider connect openai-codex --tool codex
|
|
162
|
-
clawdi ai-provider
|
|
162
|
+
clawdi ai-provider apply openai-codex
|
|
163
163
|
```
|
|
164
164
|
|
|
165
|
+
`apply openai-codex` writes compatible target config and materializes the Codex
|
|
166
|
+
OAuth profile into each selected target's native auth store. For the default
|
|
167
|
+
target set, that means `$CODEX_HOME/auth.json`, `$HERMES_HOME/auth.json`, and
|
|
168
|
+
OpenClaw's `agents/<agentId>/agent/auth-profiles.json`. Those projections do
|
|
169
|
+
not write API key refs for OAuth-backed providers.
|
|
170
|
+
|
|
165
171
|
Use `clawdi ai-provider connect ... --callback manual` in headless environments. Export/import is metadata-only by default; `--include-secrets` requires passphrase-encrypted secret export.
|
|
166
172
|
|
|
167
173
|
Current vault storage is server-managed encryption. Clawdi avoids plaintext secrets in repo files and local templates, but the backend can decrypt stored vault values and credential profiles today. Do not treat this release as zero-knowledge.
|