@bitkyc08/opencodex 2.1.5 → 2.1.6

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.ko.md CHANGED
@@ -112,6 +112,7 @@ codex -m "xai/grok-4" "이 PR을 리뷰해 줘"
112
112
  |---|---|---|
113
113
  | OpenAI (ChatGPT 로그인) | `openai-responses` | forward (키 불필요) |
114
114
  | OpenAI (API 키) | `openai-responses` | key |
115
+ | Umans AI Coding Plan | `anthropic` | key |
115
116
  | Anthropic Claude | `anthropic` | oauth / key |
116
117
  | xAI Grok | `openai-chat` | oauth / key |
117
118
  | Kimi (Moonshot) | `openai-chat` | oauth / key |
package/README.md CHANGED
@@ -132,6 +132,7 @@ Routed models also appear in the **Codex App** model picker with per-model reaso
132
132
  |---|---|---|
133
133
  | OpenAI (ChatGPT login) | `openai-responses` | forward (no key) |
134
134
  | OpenAI (API key) | `openai-responses` | key |
135
+ | Umans AI Coding Plan | `anthropic` | key |
135
136
  | Anthropic Claude | `anthropic` | oauth / key |
136
137
  | xAI Grok | `openai-chat` | oauth / key |
137
138
  | Kimi (Moonshot) | `openai-chat` | oauth / key |
@@ -243,6 +244,22 @@ Local models work too. Point opencodex at any OpenAI-compatible server running o
243
244
 
244
245
  WebSocket transport is off by default. Set `"websockets": true` only if you want Codex to advertise and use the Responses WebSocket path instead of HTTP/SSE.
245
246
 
247
+ opencodex leaves existing Codex resume history untouched by default. This avoids changing Codex's
248
+ local thread index just because the proxy started, but Codex App may hide old OpenAI-backed project
249
+ threads and opencodex-created `exec` threads while `opencodex` is the active provider. If you want
250
+ those chats to appear while the proxy is active, enable the reversible compatibility remap with
251
+ `"syncResumeHistory": true`. opencodex records the original provider/source metadata in
252
+ `~/.opencodex/codex-history-backup.json`. `ocx stop` / `ocx restore` restores backed-up OpenAI rows
253
+ to OpenAI, and ejects any remaining opencodex user threads to OpenAI as well so native Codex does not
254
+ try to resume a thread whose provider no longer exists in `config.toml`.
255
+
256
+ If you tested an older development build where `syncResumeHistory` already remapped history before
257
+ backup support existed, you can also run the explicit recovery command:
258
+
259
+ ```bash
260
+ ocx recover-history --legacy-openai
261
+ ```
262
+
246
263
  See the **[Configuration reference](https://lidge-jun.github.io/opencodex/reference/configuration/)** for every field.
247
264
 
248
265
  ## Documentation
package/README.zh-CN.md CHANGED
@@ -106,6 +106,7 @@ codex -m "deepseek/deepseek-r1" "分析这个性能瓶颈"
106
106
  |---|---|---|
107
107
  | OpenAI(ChatGPT 登录) | `openai-responses` | 转发(无需 key) |
108
108
  | OpenAI(API key) | `openai-responses` | key |
109
+ | Umans AI Coding Plan | `anthropic` | key |
109
110
  | Anthropic Claude | `anthropic` | oauth / key |
110
111
  | xAI Grok | `openai-chat` | oauth / key |
111
112
  | Kimi(Moonshot) | `openai-chat` | oauth / key |