billion-context 0.1.30 → 0.1.31

package/README.md

@@ -102,6 +102,16 @@ base_url = "https://api.openai.com/v1"
 base_url = "http://localhost:8787/bili/https://api.openai.com/v1"
 ```
 
+**Codex (ChatGPT login)** — set the top-level `openai_base_url` field (keeps
+`model_provider = "openai"` and OAuth login intact):
+```toml
+# ~/.codex/config.toml (top-level field, not a section)
+model_provider = "openai"
+openai_base_url = "http://localhost:8787/bili/https://chatgpt.com/backend-api/codex"
+```
+Run `codex login` as usual; the OAuth token travels in the `Authorization`
+header, which bili forwards untouched to the upstream.
+
 **Pi** — edit `~/.pi/agent/models.json`, change the provider's `baseUrl`:
 ```jsonc
 // before:
@@ -114,43 +124,22 @@ base_url = "http://localhost:8787/bili/https://api.openai.com/v1"
 upstream URL is configured, prepend `http://localhost:8787/bili/` to it.
 Nothing else changes.
 
-#### B. Codex Route (API key or ChatGPT subscription)
-
-Codex can be connected without changing its active `model_provider` and
-without trusting a MITM certificate. Start bili, open
-[http://localhost:8787/__bili/](http://localhost:8787/__bili/), then enable
-**Codex Route** on the Routing page. For scripted startup, enable it before
-starting the owning server:
-
-```bash
-bili codex enable --port 8787
-bili start --port 8787
-```
-
-billion-context resolves only the active Codex provider, records its real
-`base_url`, and temporarily replaces that one field with
-`http://127.0.0.1:8787/codex`. The provider id never changes, so existing Codex
-history stays in the same bucket. Disabling the route or gracefully stopping
-the owning bili process restores the original field; edits made by the user
-while routing was active are preserved. A stale takeover is safely recovered
-the next time bili starts.
-
-The Routing page also offers a manual, backup-first repair for sessions created
-by older bili test provider ids. Normal routing never migrates Codex history.
-
-#### C. Other login/subscription clients (MITM transparent proxy)
+#### B. Login/subscription clients with hardcoded endpoints (MITM transparent proxy)
 
 Clients you sign **into an account** (ChatGPT Plus/Pro, Claude, ZCode coding
-plan, …) authenticate via **OAuth and hardcode the endpoint** — you can't
-change the baseURL, so the `/bili/` prefix trick doesn't work. These need
-**MITM transparent-proxy mode** instead.
+plan, …) authenticate via **OAuth**. Most such clients also **hardcode the
+endpoint** — if you can't change the baseURL, the `/bili/` prefix trick
+doesn't work. These need **MITM transparent-proxy mode** instead.
+
+> **Codex exception:** Codex exposes a top-level `openai_base_url` config
+> field, so the ChatGPT login version CAN use the `/bili/` prefix (see above).
+> MITM is not needed for Codex.
 
-Supported login clients:
+Supported MITM clients:
 
 | Client | Login | Endpoint hardcoded | Status |
 |---|---|---|---|
 | **ZCode** | bigmodel coding plan (OAuth) | `open.bigmodel.cn` (builtin provider) | ✅ tested |
-| **Codex** | ChatGPT account (OAuth) | `chatgpt.com/backend-api` | ✅ use Codex Route above; MITM is fallback only |
 | **Claude Code** | Claude subscription (OAuth) | `api.anthropic.com` | ❓ untested (may not work — needs verification) |
 
 How MITM mode works: the client only offers an **HTTP proxy** setting, so it

package/README.zh-CN.md

@@ -86,6 +86,14 @@ base_url = "https://api.openai.com/v1"
 base_url = "http://localhost:8787/bili/https://api.openai.com/v1"
 ```
 
+**Codex(ChatGPT 登录)** —— 设顶层 `openai_base_url` 字段(保持 `model_provider = "openai"` 和 OAuth 登录不变):
+```toml
+# ~/.codex/config.toml（顶层字段,不是 section）
+model_provider = "openai"
+openai_base_url = "http://localhost:8787/bili/https://chatgpt.com/backend-api/codex"
+```
+照常运行 `codex login`;OAuth token 随 `Authorization` 头传输,bili 原样转发给上游。
+
 **Pi** —— 编辑 `~/.pi/agent/models.json`,改 provider 的 `baseUrl`:
 ```jsonc
 // 之前:
@@ -96,38 +104,20 @@ base_url = "http://localhost:8787/bili/https://api.openai.com/v1"
 
 **其他 API-key 客户端(Cursor / Aider / Continue ……)** —— 只要配置了上游 URL,前面加 `http://localhost:8787/bili/` 就行,其他都不用改。
 
-#### B. Codex 路由(API key 或 ChatGPT 订阅)
-
-Codex 不需要改 `model_provider`,也不需要信任 MITM 证书。启动 bili,打开
-[http://localhost:8787/__bili/](http://localhost:8787/__bili/),在“路由”页启用
-**Codex 路由**。脚本化启动时,先启用路由,再启动拥有它的服务:
-
-```bash
-bili codex enable --port 8787
-bili start --port 8787
-```
-
-billion-context 只解析当前激活的 Codex provider,记录它的真实 `base_url`,
-并临时只把这个字段替换成 `http://127.0.0.1:8787/codex`。provider id 始终
-不变,所以现有 Codex 历史仍在同一个分桶。关闭路由或正常停止拥有该路由的
-bili 进程时会恢复原字段;路由期间用户自己做的新修改会被保留。异常退出留下
-的接管状态会在下次启动 bili 时安全恢复。
-
-“路由”页还提供旧版 bili 测试 provider 会话的手动修复:先预览、先备份、再
-修复。正常路由绝不会自动迁移 Codex 历史。
-
-#### C. 其他登录/订阅客户端(MITM 透明代理)
+#### B. 登录/订阅客户端(硬编码端点,MITM 透明代理)
 
 需要 **登录账号**的客户端(ChatGPT Plus/Pro、Claude、ZCode coding plan
-……)通过 **OAuth 认证,且硬编码了端点**——你改不了 baseURL,所以 `/bili/`
-前缀方式对它们无效。这类客户端要用 **MITM 透明代理模式**。
+……)通过 **OAuth 认证**。多数这类客户端还 **硬编码了端点**——如果你改不了
+baseURL,`/bili/` 前缀方式就无效。这类客户端要用 **MITM 透明代理模式**。
+
+> **Codex 例外:** Codex 暴露了顶层 `openai_base_url` 配置字段,所以
+> ChatGPT 登录版 CAN 用 `/bili/` 前缀(见上方)。Codex 不需要 MITM。
 
-支持的登录客户端:
+支持的 MITM 客户端:
 
 | 客户端 | 登录方式 | 硬编码端点 | 状态 |
 |---|---|---|---|
 | **ZCode** | 智谱 coding plan(OAuth) | `open.bigmodel.cn`(内置 provider) | ✅ 已测试 |
-| **Codex** | ChatGPT 账号(OAuth) | `chatgpt.com/backend-api` | ✅ 优先使用上面的 Codex 路由;MITM 仅作 fallback |
 | **Claude Code** | Claude 订阅(OAuth) | `api.anthropic.com` | ❓ 未测试(可能不支持,需验证) |
 
 MITM 模式原理:这类客户端只提供 **HTTP 代理**设置,所以它发送