billion-context 0.1.20 → 0.1.22

package/README.md

@@ -62,6 +62,19 @@ so you don't have to invent the schema from scratch:
 [acp-config] created empty config at ~/.config/billion-context/billion-context.json — add your providers (see README Quickstart), then restart
 ```
 
+**Or configure via the web UI** (easier): open `http://localhost:8787/__acp/` in
+a browser while the proxy is running — edit providers in a form, and get
+copy-ready config snippets for Pi / OpenCode / Codex. The startup banner prints
+this URL too:
+
+```
+acp-proxy listening on http://localhost:8787 — web UI: http://localhost:8787/__acp/
+```
+
+This is the recommended path for first-time setup. (Prefer editing the JSON
+file directly — e.g. for git-managed or scripted deployments? See
+[Manual config file](#manual-config-file) below.)
+
 ### How routing works
 
 The proxy routes by a **provider name in the URL path** — the first path
@@ -86,40 +99,20 @@ to send each request. In the config below, `zhipu` corresponds to:
       }
 ```
 
-### Step 2 — Edit the config file
-
-Open the file from Step 1 (`~/.config/billion-context/billion-context.json`)
-and edit the `providers` block to match what you pay for. Each entry is a
-**name → URL** mapping; the name is what you'll put in the client's base URL in
-Step 3.
-
-```json
-{
-  "providers": {
-    "zhipu": {
-      "url": "https://open.bigmodel.cn",
-      "models": {
-        "glm-5.2": { "context": 1000000, "output": 131072 }
-      }
-    },
-    "anthropic": "https://api.anthropic.com"
-  }
-}
-```
-
-- Delete providers you don't use.
-- Add others (e.g. `"deepseek": "https://api.deepseek.com"`).
-- The API key is **not** here — it lives in the client; the proxy passes it
-  through untouched.
+### Step 2 — Configure your providers
 
-After saving, **restart `bili`**. The startup banner lists your routes:
+Open the **web UI** at `http://localhost:8787/__acp/` and add your providers
+there (add provider → fill name + URL + per-model context → Save). This writes
+to `~/.config/billion-context/billion-context.json` directly. Then **restart
+`bili`** — the startup banner lists your routes:
 
 ```
-acp-proxy listening on http://127.0.0.1:8787 — routes: anthropic=https://api.anthropic.com, zhipu=https://open.bigmodel.cn
+acp-proxy listening on http://localhost:8787 — routes: anthropic=https://api.anthropic.com, zhipu=https://open.bigmodel.cn
 ```
 
-That confirms the proxy picked up your config. (Full schema — per-model context
-windows, optional fields — is in [Configuration](#configuration).)
+That confirms the proxy picked up your config. (Prefer editing the JSON file by
+hand? See [Manual config file](#manual-config-file). Full schema — per-model
+context windows, optional fields — is in [Configuration](#configuration).)
 
 ### Step 3 — Point your client at the proxy
 
@@ -187,6 +180,48 @@ Not yet supported. The proxy currently speaks the Anthropic, OpenAI
 chat-completions, and OpenAI Responses protocols — if your client uses a
 different protocol or a non-standard auth header, it won't work yet.
 
+### Web UI
+
+Open `http://localhost:8787/__acp/` in a browser while the proxy is running. You can:
+
+- **Edit providers** in a form (add/remove providers and per-model context windows) and save — this writes to `billion-context.json` directly.
+- **Generate client URLs** — pick a provider, get ready-to-copy config snippets for Pi / OpenCode / Codex (the `baseUrl`/`baseURL`/`base_url` line with the proxy origin + provider name filled in).
+- **View sessions** — live table of active sessions (requests, tokens saved, last seen), auto-refreshing.
+
+Changes to providers require a **restart** to take effect (the UI tells you this).
+
+### Manual config file
+
+Prefer editing JSON by hand — for git-managed configs, scripted deployments, or
+if you just don't want to use the browser? The web UI writes to the same file,
+so you can edit it directly with identical results.
+
+Open `~/.config/billion-context/billion-context.json` and edit the `providers`
+block. Each entry is a **name → URL** mapping; the name is what you put in the
+client's base URL in Step 3.
+
+```json
+{
+  "providers": {
+    "zhipu": {
+      "url": "https://open.bigmodel.cn",
+      "models": {
+        "glm-5.2": { "context": 1000000, "output": 131072 }
+      }
+    },
+    "anthropic": "https://api.anthropic.com"
+  }
+}
+```
+
+- Delete providers you don't use.
+- Add others (e.g. `"deepseek": "https://api.deepseek.com"`).
+- The API key is **not** here — it lives in the client; the proxy passes it
+  through untouched.
+
+After saving, **restart `bili`**. (Full schema — per-model context windows,
+optional fields — is in [Configuration](#configuration).)
+
 ### Verify
 
 With the proxy running and your config saved, check it answers and that your

package/README.zh-CN.md

@@ -53,67 +53,16 @@ bili
 
 它监听 `http://127.0.0.1:8787`。保持这个终端开着(或后台运行,见[运行代理](#运行代理))。
 
-首次运行 `bili` 会**自动创建一份空的配置文件**,并告诉你路径:
-
-```
-[acp-config] created empty config at ~/.config/billion-context/billion-context.json — add your providers (see README Quickstart), then restart
-```
-
-### 路由怎么工作
-
-代理按 **URL 路径里的 provider 名**路由 —— host 后面的第一段路径。它会
-剥离该名字,把剩余部分转发给那个 provider。名字之后的整段路径原样透传:
-
-```
-客户端 baseURL: http://localhost:8787/zhipu/api/coding/paas/v4
-                 └──────────┬──────────┘└────────┬────────┘
-                     代理 host            剩余路径
-                     + provider 名        (原样转发)
-```
-
-这就是为什么第 2 步让你声明带名字的 provider、第 3 步又让你把同样的名字
-放在客户端 base URL 的开头 —— 代理凭这个知道每条请求发到哪。
-稍后在配置文件中,`zhipu` 对应的是:
-```json
-    "zhipu": {
-      "url": "https://open.bigmodel.cn",
-      "models": {
-        "glm-5.2": { "context": 1000000, "output": 131072 }
-      }
-```
-
+点击[http://localhost:8787/__acp/](http://localhost:8787/__acp/) 添加你的模型
+<img width="2908" height="1787" alt="image" src="https://github.com/user-attachments/assets/cacf4b64-e5c6-41f2-b270-fd2be02eab0c" />
 
 ### 第 2 步 —— 编辑配置文件
 
-打开第 1 步创建的文件(`~/.config/billion-context/billion-context.json`),
-编辑 `providers` 块,填入你付费使用的 provider。每个条目是一个
-**名字 → URL** 映射;这个名字就是你在第 3 步里写进客户端 base URL 的东西。
+复制以下内容
 
-```json
-{
-  "providers": {
-    "zhipu": {
-      "url": "https://open.bigmodel.cn",
-      "models": {
-        "glm-5.2": { "context": 1000000, "output": 131072 }
-      }
-    },
-    "anthropic": "https://api.anthropic.com",
-  }
-}
-```
+<img width="2931" height="1519" alt="image" src="https://github.com/user-attachments/assets/c02278be-bc7a-4f14-8f58-0f2d83784d54" />
 
-- 删掉你不用的 provider。
-- 添加其他的(例如 `"deepseek": "https://api.deepseek.com"`)。
-- API key **不**写在这里 —— key 在客户端那边,代理原样透传。
-
-保存后**重启 `bili`**。启动行列出你的路由:
-
-```
-acp-proxy listening on http://127.0.0.1:8787 — routes: anthropic=https://api.anthropic.com, zhipu=https://open.bigmodel.cn
-```
-
-这证明代理读到了你的配置。(完整 schema —— 按模型的 context 窗口、可选字段 —— 见[配置](#配置)。)
+> 不想用网页?也可以直接手编 JSON 文件,见下文[手动配置文件](#手动配置文件)。
 
 ### 第 3 步 —— 把客户端指向代理
 
@@ -178,6 +127,51 @@ base_url = "http://localhost:8787/zhipu/api/coding/paas/v4"
 暂不支持。代理目前说 Anthropic、OpenAI chat-completions、OpenAI Responses
 三种协议 —— 如果你的客户端用别的协议或非标准 auth header,还用不了。
 
+### 手动配置文件
+
+上面用网页配置。如果你不想用网页、想把配置纳入 git 管理、或者用脚本
+自动化部署,也可以直接手编 JSON 文件,效果完全一样。
+
+打开 `~/.config/billion-context/billion-context.json`,编辑 `providers` 块。
+每个条目是一个**名字 → URL** 映射;这个名字就是你在第 3 步里写进客户端
+base URL 的东西。
+
+```json
+{
+  "providers": {
+    "zhipu": {
+      "url": "https://open.bigmodel.cn",
+      "models": {
+        "glm-5.2": { "context": 1000000, "output": 131072 }
+      }
+    },
+    "anthropic": "https://api.anthropic.com"
+  }
+}
+```
+
+- 删掉你不用的 provider。
+- 添加其他的(例如 `"deepseek": "https://api.deepseek.com"`)。
+- API key **不**写在这里 —— key 在客户端那边,代理原样透传。
+
+保存后**重启 `bili`**。启动行列出你的路由:
+
+```
+acp-proxy listening on http://127.0.0.1:8787 — routes: anthropic=https://api.anthropic.com, zhipu=https://open.bigmodel.cn
+```
+
+这证明代理读到了你的配置。(完整 schema —— 按模型的 context 窗口、可选字段 —— 见[配置](#配置)。)
+
+### 网页配置
+
+代理跑着的时候,在浏览器打开 `http://localhost:8787/__acp/`。你可以:
+
+- **编辑 providers** —— 用表单增删 provider 和按模型的 context 窗口,点 Save 直接写入 `billion-context.json`。
+- **生成客户端 URL** —— 选一个 provider,得到可直接复制的配置片段(Pi / OpenCode / Codex 的 `baseUrl`/`baseURL`/`base_url` 一行,已填好代理地址 + provider 名)。
+- **查看会话** —— 实时会话表(请求数、省的 token、最后活跃时间),自动刷新。
+
+改完 providers 需要**重启 bili** 才生效(UI 会提醒你)。
+
 ### 验证
 
 代理跑着、配置保存了之后,确认它能应答,并且第一个真实请求在日志里显示压缩活动: