coding-proxy 0.2.1a3__tar.gz → 0.2.3a1__tar.gz

{coding_proxy-0.2.1a3 → coding_proxy-0.2.3a1}/CHANGELOG.md

@@ -4,22 +4,21 @@
 
 ## [Unreleased]
 
-- style(lint): 移除未使用变量 `old_base_url` 并合并重复的 `antigravity` 导入块;
-## [v0.2.1](https://github.com/ThreeFish-AI/coding-proxy/releases/tag/v0.2.1a1) — 2026-04-11
+## [v0.2.3](https://github.com/ThreeFish-AI/coding-proxy/releases/tag/v0.2.3a1) — 2026-04-15
 
-- fix(antigravity): 修复 Google OAuth token 刷新后 scope 校验过严导致 403 的问题;
-- refactor(request-normalizer): 移除跨供应商 tool_result 重定位死代码，docstring 对齐实际剥离行为;
+- feat(dashboard): 新增实时 Web Dashboard 页面，聚合展示流量与用量统计;
+- docs(user-guide): 补充 POST /v1/messages 完整 API 参考文档;
+- fix(request-normalizer): misplaced tool_result 从剥离改为重定位，修复跨供应商降级后 Anthropic 恢复失败;
 
+## [v0.2.2](https://github.com/ThreeFish-AI/coding-proxy/releases/tag/v0.2.2) — 2026-04-13
 
-- **请求规范化死代码清理**：移除 `request_normalizer` 中永远不可达的 `tool_result` 重定位逻辑（Phase 1 剥离已覆盖全部场景，Phase 2 重定位因方向错误无法启用）；更新 docstring 使之与实际行为（剥离）一致；
+- feat(reset): CLI reset 命令新增 -v/--vendor 参数，支持运行时 N-tier 链路重排序（逗号分隔的 vendor 列表）;
+- fix(logging): 修复 uvicorn.error 日志在文件中重复打印的问题;
 
-### 🐛 Bug 修复
+## [v0.2.1](https://github.com/ThreeFish-AI/coding-proxy/releases/tag/v0.2.1) — 2026-04-11
 
-- **fix(antigravity)**: 新增 Google Cloud Code **v1internal 协议支持 + project_id 自动发现**，彻底解决 `ACCESS_TOKEN_SCOPE_INSUFFICIENT` (403) 问题。
-  - **根因**：此前调用标准 Generative Language API (`generativelanguage.googleapis.com`)，该端点对 OAuth scope 校验严格；参考项目 Antigravity-Manager 实际使用的是 Cloud Code v1internal 内部 API (`cloudcode-pa.googleapis.com/v1internal`)，接受相同凭证但协议格式不同
-  - **修复（v1internal 协议）**：新增 `project_id` 配置字段 + v1internal 请求信封包装 + 客户端指纹 Headers + 端点 URL 适配
-  - **修复（自动发现）**：利用已有的 `cloud-platform` OAuth scope 通过 Cloud Resource Manager API 自动发现用户的 GCP `project_id`，首次请求时零配置自动切换至 v1internal 模式——开箱即用，无需手动配置
-  - **附带改进**：`_acquire()` scope 校验保持 warning 降级；`_mark_scope_error_if_needed()` 增强诊断日志；`get_diagnostics()` 暴露发现状态
+- feat(logging): 实现日志双写（控制台 + 本地文件），日志文件支持 5MB 自动轮转及 gzip 压缩备份；ModelCall 日志降级为 DEBUG 级别；
+- feat(circuit-breaker): 补全熔断器状态转换日志的 vendor 上下文信息;
 
 ## [v0.2.0](https://github.com/ThreeFish-AI/coding-proxy/releases/tag/v0.2.0) — 2026-04-09
 

{coding_proxy-0.2.1a3 → coding_proxy-0.2.3a1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: coding-proxy
-Version: 0.2.1a3
+Version: 0.2.3a1
 Summary: A High-Availability, Transparent, and Smart Multi-Vendor Proxy for Claude Code. Support Claude Plans, GitHub Copilot, Google Antigravity, ZAI/GLM, MiniMax, Qwen, Xiaomi, Kimi, Doubao...
 Project-URL: Source Code, https://github.com/ThreeFish-AI/coding-proxy
 Project-URL: User Guide, https://github.com/ThreeFish-AI/coding-proxy/blob/master/docs/user-guide.md
@@ -56,7 +56,7 @@ When you're deeply immersed in your coding "zone" with **Claude Code** (or any A
 
 ## 🌟 Core Features
 
-- **⛓️ N-tier Chained Failover**: Automatically downgrades from official Claude Plans, gracefully falling back to GitHub Copilot, then Google Antigravity, with Zhipu GLM acting as the ultimate safety net.
+- **⛓️ N-tier Chained Failover**: Autonomous descending sequence, supporting Claude's official plans, as well as Coding Plans from GitHub Copilot, Z AI, MiniMax, Alibaba Qwen, Xiaomi, Kimi, Doubao, etc.
 - **🛡️ Smart Resilience & Quota Guardians**: Every single vendor node comes fully armed with an independent **Circuit Breaker** and **Quota Guard** to proactively dodge avalanches without breaking a sweat.
 - **👻 Phantom-like Transparency**: **100% transparent** to the client! No code tweaks required. Overwrite `ANTHROPIC_BASE_URL` with a single line, and you're good to go.
 - **🔄 Universal Alchemy (Formats & Models)**: Native support for two-way request/streaming (SSE) translations between Anthropic ←→ Gemini. Plus, auto/DIY model name mapping (e.g., effortlessly morphing `claude-*` into `glm-*`).

{coding_proxy-0.2.1a3 → coding_proxy-0.2.3a1}/README.md

@@ -29,7 +29,7 @@ When you're deeply immersed in your coding "zone" with **Claude Code** (or any A
 
 ## 🌟 Core Features
 
-- **⛓️ N-tier Chained Failover**: Automatically downgrades from official Claude Plans, gracefully falling back to GitHub Copilot, then Google Antigravity, with Zhipu GLM acting as the ultimate safety net.
+- **⛓️ N-tier Chained Failover**: Autonomous descending sequence, supporting Claude's official plans, as well as Coding Plans from GitHub Copilot, Z AI, MiniMax, Alibaba Qwen, Xiaomi, Kimi, Doubao, etc.
 - **🛡️ Smart Resilience & Quota Guardians**: Every single vendor node comes fully armed with an independent **Circuit Breaker** and **Quota Guard** to proactively dodge avalanches without breaking a sweat.
 - **👻 Phantom-like Transparency**: **100% transparent** to the client! No code tweaks required. Overwrite `ANTHROPIC_BASE_URL` with a single line, and you're good to go.
 - **🔄 Universal Alchemy (Formats & Models)**: Native support for two-way request/streaming (SSE) translations between Anthropic ←→ Gemini. Plus, auto/DIY model name mapping (e.g., effortlessly morphing `claude-*` into `glm-*`).

{coding_proxy-0.2.1a3 → coding_proxy-0.2.3a1}/docs/user-guide.md

@@ -908,17 +908,298 @@ curl -I http://127.0.0.1:8046/
 
 ### 5.2 POST /v1/messages
 
-代理 Anthropic Messages API，支持流式和非流式请求。
+代理 Anthropic Messages API，支持流式（SSE）与非流式请求。请求经过规范化处理后，路由至配置的 vendor tier 链；若当前 tier 不可用或返回可恢复错误，自动故障转移至下一 tier。
+
+#### 5.2.1 请求格式
+
+**请求头**
+
+| 请求头 | 必填 | 说明 |
+|--------|------|------|
+| `Content-Type` | ✓ | 固定为 `application/json` |
+| `Authorization` | ✗ | 格式 `Bearer <token>`；对 Anthropic vendor 透传，对其他 vendor 由代理内部凭证管理 |
+| `anthropic-version` | ✗ | Anthropic API 版本，建议传 `2023-06-01`；透传至上游 |
+| `anthropic-beta` | ✗ | Beta 功能标识，透传至上游（如 `interleaved-thinking-2025-05-14`） |
+
+> **注**：`hop-by-hop` 头（如 `Connection`、`Transfer-Encoding`）会在转发前自动过滤。
+
+**请求体参数**
+
+| 字段 | 类型 | 必填 | 约束 | 说明 |
+|------|------|------|------|------|
+| `model` | string | ✓ | 非空 | 目标模型标识。经 `model_mapping` 规则映射后路由至实际 vendor 模型 |
+| `messages` | array | ✓ | 至少 1 条；`user`/`assistant` 交替；末尾必须为 `user` | 对话历史，详见[消息结构](#消息结构) |
+| `max_tokens` | integer | ✗ | > 0 | 最大输出 token 数 |
+| `stream` | boolean | ✗ | 默认 `false` | 是否以 SSE 流式返回 |
+| `temperature` | number | ✗ | `[0, 2]` | 采样温度 |
+| `top_p` | number | ✗ | `(0, 1]` | Top-p 采样 |
+| `top_k` | integer | ✗ | ≥ 1 | Top-k 采样 |
+| `stop_sequences` | array[string] | ✗ | | 提前停止的字符串序列 |
+| `system` | string \| array | ✗ | | 系统提示词；可为纯字符串或 content block 数组 |
+| `tools` | array | ✗ | | 工具定义；详见 Anthropic 官方文档 |
+| `tool_choice` | object | ✗ | | 工具选择策略（`auto`/`any`/`tool`） |
+| `thinking` | object | ✗ | 需 `budget_tokens`；部分 vendor 不支持 | Extended Thinking 配置，格式 `{"type":"enabled","budget_tokens":N}` |
+| `metadata` | object | ✗ | | 用户元数据（如 `user_id`），透传至上游 |
+
+<a id="消息结构"></a>**消息结构**
+
+每条消息的 `content` 字段可为纯字符串或 content block 数组：
+
+```json
+{
+  "role": "user",
+  "content": [
+    { "type": "text", "text": "请描述这张图片" },
+    {
+      "type": "image",
+      "source": {
+        "type": "base64",
+        "media_type": "image/png",
+        "data": "<base64 编码的图片数据>"
+      }
+    }
+  ]
+}
+```
+
+支持的 content block 类型：
+
+| 类型 | 适用角色 | 必填字段 | 说明 |
+|------|---------|---------|------|
+| `text` | `user`/`assistant` | `text` | 纯文本 |
+| `image` | `user` | `source`（`type`/`media_type`/`data` 或 `url`） | 图片；部分 vendor 不支持 |
+| `tool_use` | `assistant` | `id`（`toolu_` 前缀）、`name`、`input` | 模型发起工具调用 |
+| `tool_result` | `user` | `tool_use_id`、`content` | 工具调用结果；**只能出现在 `user` 消息中** |
+| `thinking` | `assistant` | `thinking`、`signature` | Extended Thinking 内容块；跨 vendor 时会被自动剥离 |
+
+---
+
+#### 5.2.2 非流式请求示例
+
+```bash
+curl -X POST http://127.0.0.1:8046/v1/messages \
+  -H "Content-Type: application/json" \
+  -H "Authorization: Bearer $ANTHROPIC_API_KEY" \
+  -H "anthropic-version: 2023-06-01" \
+  -d '{
+    "model": "claude-sonnet-4-5",
+    "max_tokens": 1024,
+    "messages": [
+      {"role": "user", "content": "你好，介绍一下你自己"}
+    ]
+  }'
+```
+
+**成功响应（HTTP 200）**
+
+```json
+{
+  "id": "msg_01XFDUDYJgAACzvnptvVoYEL",
+  "type": "message",
+  "role": "assistant",
+  "content": [
+    { "type": "text", "text": "你好！我是 Claude，一个由 Anthropic 开发的 AI 助手。" }
+  ],
+  "model": "claude-sonnet-4-5-20251101",
+  "stop_reason": "end_turn",
+  "stop_sequence": null,
+  "usage": {
+    "input_tokens": 14,
+    "output_tokens": 32,
+    "cache_creation_input_tokens": 0,
+    "cache_read_input_tokens": 0
+  }
+}
+```
+
+**响应字段说明**
+
+| 字段 | 类型 | 说明 |
+|------|------|------|
+| `id` | string | 消息唯一 ID，格式 `msg_*` |
+| `type` | string | 固定为 `"message"` |
+| `role` | string | 固定为 `"assistant"` |
+| `content` | array | 响应内容块列表（`text`/`tool_use` 等） |
+| `model` | string | 实际处理请求的模型完整 ID |
+| `stop_reason` | string | 停止原因，见下表 |
+| `stop_sequence` | string \| null | 触发停止的序列字符串；未命中时为 `null` |
+| `usage.input_tokens` | integer | 输入消耗的 token 数 |
+| `usage.output_tokens` | integer | 输出消耗的 token 数 |
+| `usage.cache_creation_input_tokens` | integer | 创建缓存的 token 数（Prompt Cache） |
+| `usage.cache_read_input_tokens` | integer | 从缓存命中的 token 数（Prompt Cache） |
+
+**`stop_reason` 枚举**
+
+| 值 | 含义 |
+|----|------|
+| `end_turn` | 模型自然输出完毕 |
+| `tool_use` | 模型发起工具调用，等待结果 |
+| `stop_sequence` | 触发了请求中指定的停止序列 |
+| `max_tokens` | 达到 `max_tokens` 上限 |
+
+---
+
+#### 5.2.3 流式请求示例（SSE 模式）
+
+在请求体中设置 `"stream": true`，响应将以 `text/event-stream` 格式逐块下发：
 
 ```bash
 curl -X POST http://127.0.0.1:8046/v1/messages \
   -H "Content-Type: application/json" \
   -H "Authorization: Bearer $ANTHROPIC_API_KEY" \
   -H "anthropic-version: 2023-06-01" \
-  -d '{"model":"claude-sonnet-4-*","max_tokens":1024,"messages":[{"role":"user","content":"Hello"}]}'
+  --no-buffer \
+  -d '{
+    "model": "claude-sonnet-4-5",
+    "max_tokens": 1024,
+    "stream": true,
+    "messages": [
+      {"role": "user", "content": "用一句话介绍你自己"}
+    ]
+  }'
+```
+
+**SSE 事件流示例**
+
 ```
+event: message_start
+data: {"type":"message_start","message":{"id":"msg_01abc","type":"message","role":"assistant","content":[],"model":"claude-sonnet-4-5-20251101","stop_reason":null,"stop_sequence":null,"usage":{"input_tokens":14,"output_tokens":1,"cache_creation_input_tokens":0,"cache_read_input_tokens":0}}}
+
+event: content_block_start
+data: {"type":"content_block_start","index":0,"content_block":{"type":"text","text":""}}
+
+event: ping
+data: {"type":"ping"}
+
+event: content_block_delta
+data: {"type":"content_block_delta","index":0,"delta":{"type":"text_delta","text":"我是"}}
+
+event: content_block_delta
+data: {"type":"content_block_delta","index":0,"delta":{"type":"text_delta","text":" Claude"}}
+
+event: content_block_stop
+data: {"type":"content_block_stop","index":0}
+
+event: message_delta
+data: {"type":"message_delta","delta":{"stop_reason":"end_turn","stop_sequence":null},"usage":{"output_tokens":8}}
+
+event: message_stop
+data: {"type":"message_stop"}
+```
+
+**SSE 事件类型说明**
+
+| 事件类型 | 说明 |
+|---------|------|
+| `message_start` | 消息开始，包含初始元数据 |
+| `content_block_start` | 新的 content block 开始（每个 block 有独立 `index`） |
+| `content_block_delta` | content block 增量；`delta.type` 为 `text_delta` 或 `input_json_delta`（工具调用参数） |
+| `content_block_stop` | 当前 content block 结束 |
+| `message_delta` | 消息级别的增量更新，包含最终 `stop_reason` 和累计 `usage` |
+| `message_stop` | 消息结束，流关闭 |
+| `ping` | 心跳事件，客户端可忽略 |
+| `error` | 流式处理过程中发生错误（见[错误响应](#错误响应)） |
+
+> **注**：流式模式下，一旦 SSE 流开始发送，代理不再进行 tier 级别的故障转移。若中途出现错误，会以 `event: error` 事件通知客户端，随后关闭流。
+
+---
+
+#### 5.2.4 工具调用示例
+
+```bash
+curl -X POST http://127.0.0.1:8046/v1/messages \
+  -H "Content-Type: application/json" \
+  -H "anthropic-version: 2023-06-01" \
+  -d '{
+    "model": "claude-sonnet-4-5",
+    "max_tokens": 1024,
+    "tools": [
+      {
+        "name": "get_weather",
+        "description": "获取指定城市的当前天气",
+        "input_schema": {
+          "type": "object",
+          "properties": {
+            "city": {"type": "string", "description": "城市名称"}
+          },
+          "required": ["city"]
+        }
+      }
+    ],
+    "messages": [
+      {"role": "user", "content": "北京今天天气怎么样？"}
+    ]
+  }'
+```
+
+---
+
+<a id="错误响应"></a>
+#### 5.2.5 错误响应
+
+**错误响应结构**
+
+```json
+{
+  "error": {
+    "type": "invalid_request_error",
+    "message": "详细错误描述",
+    "details": ["原因1", "原因2"]
+  }
+}
+```
+
+> `details` 字段为可选，仅在 `NoCompatibleVendorError`（无可用 vendor）等特定场景中包含。
+
+**HTTP 状态码对照**
+
+| HTTP 状态码 | `error.type` | 触发场景 | 是否可重试 |
+|------------|-------------|---------|-----------|
+| `400` | `invalid_request_error` | 请求格式/内容不合规（消息结构错误、缺少必填字段、无兼容 vendor 等） | ✗ |
+| `401` | `authentication_error` | 无有效认证凭证 | ✗ |
+| `403` | `permission_error` | 权限不足 | ✗ |
+| `429` | `rate_limit_error` | 所有 vendor 均触发速率限制 | ✓（等待后重试） |
+| `500` | `api_error` | 代理内部异常 | ✓（视情况） |
+| `502` | `api_error` | 所有 vendor 均不可达（超时/连接失败） | ✓ |
+| `503` | `authentication_error` | Token 获取失败（如 OAuth 凭证失效） | ✓（重新认证后） |
+
+**流式错误事件**
+
+流式响应中途发生错误时，以 SSE 事件形式通知：
+
+```
+event: error
+data: {"type":"error","error":{"type":"api_error","message":"上游连接超时"}}
+```
+
+---
+
+#### 5.2.6 请求规范化行为
+
+代理在将请求转发至 vendor 前，会自动进行规范化处理。**以下行为对调用方透明，无需手动处理**：
+
+**自动修复（静默处理）**
+
+| 问题 | 处理方式 |
+|------|---------|
+| `tool_use_id` 格式不符（非 `toolu_` 前缀，如 `srvtoolu_*`） | 自动重写为合规格式，并维护映射关系 |
+| `tool_result` 出现在 `assistant` 消息中 | 将该 block 从 assistant 消息中剥离（首次触发时记录 WARNING 日志） |
+| `tool_use` 缺少合法 ID | 自动生成新 ID 并建立映射 |
+
+**致命验证错误（返回 HTTP 400）**
+
+| 场景 | 错误示例 |
+|------|---------|
+| `tool_use` block 缺少 `id` 字段 | `"tool_use block is missing 'id' field"` |
+| `tool_result` block 缺少 `tool_use_id` 字段 | `"tool_result block is missing 'tool_use_id' field"` |
+| 消息角色不交替（连续相同角色） | `"messages must alternate between user and assistant"` |
+| `messages` 末尾不是 `user` 消息 | `"last message must be from user"` |
+
+**Thinking Block 跨 Vendor 处理**
+
+当请求被路由至非 Anthropic vendor（如 Copilot、智谱等）时，assistant 历史消息中的 `thinking` block 会被自动剥离，因为这些 block 包含仅 Anthropic 可验证的签名（`signature` 字段）。此行为不影响当前轮次的 `thinking` 功能配置（由目标 vendor 的能力决定）。
 
-> **注**：示例中使用 `claude-sonnet-4-*` 通配形式表示模型系列。具体版本号以 [Anthropic 官方文档](https://docs.anthropic.com/en/docs/about-claude/models) 为准。
+> **注**：示例中使用 `claude-sonnet-4-5` 作为模型 ID 示例。实际可用的模型 ID 取决于配置的 vendor 与 `model_mapping` 规则，以 [Anthropic 官方文档](https://docs.anthropic.com/en/docs/about-claude/models) 和本地配置为准。
 
 ### 5.3 POST /v1/messages/count_tokens
 

{coding_proxy-0.2.1a3 → coding_proxy-0.2.3a1}/docs/zh-CN/README.md

@@ -29,7 +29,7 @@
 
 ## 🌟 核心特性 (Core Features)
 
-- **⛓️ N-tier 链式故障转移 (Failover)**：自动从 Claude 官方 Plans 依次降级至 GitHub Copilot、Google Antigravity，最后由智谱 GLM 兜底。
+- **⛓️ N-tier 链式故障转移 (Failover)**：自主降序序列，支持 Claude 官方 Plans，以及 GitHub Copilot、智谱、MiniMax、阿里千问、小米、Kimi、豆包等的 Coding Plan。
 - **🛡️ 智能弹性与容灾守卫**：每个供应商节点独立配备 **熔断器 (Circuit Breaker)** 与 **配额守卫 (Quota Guard)**，防雪崩、主动避险。
 - **👻 透明无感代理机制**：对客户端 **100% 透明**！无需修改任何代码，仅需一行配置覆盖 `ANTHROPIC_BASE_URL` 即可接入。
 - **🔄 跨模型与全格式转换**：原生支持 Anthropic ←→ Gemini 的请求与流式响应（SSE）双向转换，并支持自动/自助映射模型名称（如 `claude-*` 至 `glm-*`）。

{coding_proxy-0.2.1a3 → coding_proxy-0.2.3a1}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "coding-proxy"
-version = "0.2.1a3"
+version = "0.2.3a1"
 description = "A High-Availability, Transparent, and Smart Multi-Vendor Proxy for Claude Code. Support Claude Plans, GitHub Copilot, Google Antigravity, ZAI/GLM, MiniMax, Qwen, Xiaomi, Kimi, Doubao..."
 readme = "README.md"
 requires-python = ">=3.12"

{coding_proxy-0.2.1a3 → coding_proxy-0.2.3a1}/src/coding/proxy/cli/__init__.py

@@ -216,16 +216,50 @@ async def _run_usage(
 @app.command()
 def reset(
     port: int = typer.Option(8046, "--port", "-p", help="代理服务端口"),
+    vendor: str | None = typer.Option(
+        None,
+        "--vendor",
+        "-v",
+        help="提升/重排序 vendor 优先级（单个或逗号分隔多个）",
+    ),
 ) -> None:
-    """重置所有层级的熔断器和配额守卫（恢复使用最高优先级供应商）."""
+    """重置所有层级的熔断器和配额守卫.
+
+    可通过 -v 指定运行时 N-tier 链路重排序：
+
+    \b
+      -v zhipu               提升 zhipu 到最高优先级
+      -v zhipu,anthropic     替换整个 N-tier 链路顺序
+    """
     import httpx
 
+    # 构建请求 body
+    json_body: dict | None = None
+    if vendor:
+        parts = [v.strip() for v in vendor.split(",") if v.strip()]
+        if parts:
+            json_body = {"vendors": parts}
+
     try:
-        resp = httpx.post(f"http://127.0.0.1:{port}/api/reset", timeout=5)
+        resp = httpx.post(
+            f"http://127.0.0.1:{port}/api/reset",
+            json=json_body,
+            timeout=5,
+        )
         if resp.status_code == 200:
+            data = resp.json()
             console.print("[green]所有层级的熔断器和配额守卫已重置[/green]")
+            tier_order = data.get("tier_order")
+            if tier_order:
+                order_str = " → ".join(tier_order)
+                console.print(f"[cyan]当前链路顺序:[/] {order_str}")
         else:
-            console.print(f"[red]重置失败: {resp.status_code}[/red]")
+            try:
+                err = resp.json()
+                msg = err.get("error", {}).get("message", resp.text)
+            except Exception:
+                msg = resp.text
+            console.print(f"[red]重置失败: {msg}[/red]")
     except httpx.ConnectError:
         console.print("[red]代理服务未运行[/red]")
 

{coding_proxy-0.2.1a3 → coding_proxy-0.2.3a1}/src/coding/proxy/config/config.default.yaml

@@ -111,7 +111,7 @@ vendors:
     # 不配置 circuit_breaker → 自动成为终端层，不触发向下故障转移
     circuit_breaker:
       failure_threshold: 3
-      recovery_timeout_seconds: 300
+      recovery_timeout_seconds: 30
       success_threshold: 2
     quota_guard:
       enabled: true # 启用后按 Premium Requests 配额管理
@@ -421,6 +421,11 @@ pricing:
     input_cost_per_mtok: ¥0.80
     output_cost_per_mtok: ¥2.00
     cache_read_cost_per_mtok: ¥0.16
+  - vendor: zhipu
+    model: glm-4.7 # 待区分长短上下文定价
+    input_cost_per_mtok: ¥2.00
+    output_cost_per_mtok: ¥8.00
+    cache_read_cost_per_mtok: ¥0.40
   - vendor: zhipu
     model: glm-5v-turbo # 待区分长短上下文定价
     input_cost_per_mtok: ¥5.00

{coding_proxy-0.2.1a3 → coding_proxy-0.2.3a1}/src/coding/proxy/logging/__init__.py

@@ -118,7 +118,11 @@ def build_log_config(
         },
         "loggers": {
             "uvicorn": {"handlers": ["default"], "level": level, "propagate": False},
-            "uvicorn.error": {"level": level},
+            "uvicorn.error": {
+                "handlers": ["default"],
+                "level": level,
+                "propagate": False,
+            },
             "uvicorn.access": {
                 "handlers": ["access"],
                 "level": "INFO",

{coding_proxy-0.2.1a3 → coding_proxy-0.2.3a1}/src/coding/proxy/routing/quota_guard.py

@@ -56,6 +56,18 @@ class QuotaGuard:
         """滑动窗口小时数（供基线加载使用）."""
         return self._window / 3600
 
+    @property
+    def _window_label(self) -> str:
+        """人类可读的窗口周期短标签."""
+        w = self._window
+        if w >= 86400 and w % 86400 == 0:
+            return f"{w // 86400}d"
+        if w >= 3600 and w % 3600 == 0:
+            return f"{w // 3600}h"
+        if w >= 60 and w % 60 == 0:
+            return f"{w // 60}m"
+        return f"{w}s"
+
     def can_use_primary(self) -> bool:
         """判断是否可以使用主后端."""
         if not self._enabled:
@@ -68,7 +80,8 @@ class QuotaGuard:
                 ):
                     self._transition_to(QuotaState.QUOTA_EXCEEDED)
                     logger.warning(
-                        "Quota guard: WITHIN_QUOTA → EXCEEDED (%.1f%%)",
+                        "Quota guard [%s]: WITHIN_QUOTA → EXCEEDED (%.1f%%)",
+                        self._window_label,
                         self._total / self._budget * 100,
                     )
                     return False
@@ -80,12 +93,18 @@ class QuotaGuard:
                 and self._total < int(self._budget * self._threshold)
             ):
                 self._transition_to(QuotaState.WITHIN_QUOTA)
-                logger.info("Quota guard: EXCEEDED → WITHIN_QUOTA (usage dropped)")
+                logger.info(
+                    "Quota guard [%s]: EXCEEDED → WITHIN_QUOTA (usage dropped)",
+                    self._window_label,
+                )
                 return True
             now = time.monotonic()
             if now - self._last_probe >= self._effective_probe_interval:
                 self._last_probe = now
-                logger.info("Quota guard: allowing probe request")
+                logger.info(
+                    "Quota guard [%s]: allowing probe request",
+                    self._window_label,
+                )
                 return True
             return False
 
@@ -104,7 +123,10 @@ class QuotaGuard:
         with self._lock:
             if self._state == QuotaState.QUOTA_EXCEEDED:
                 self._transition_to(QuotaState.WITHIN_QUOTA)
-                logger.info("Quota guard: EXCEEDED → WITHIN_QUOTA (probe success)")
+                logger.info(
+                    "Quota guard [%s]: EXCEEDED → WITHIN_QUOTA (probe success)",
+                    self._window_label,
+                )
 
     def notify_cap_error(self, retry_after_seconds: float | None = None) -> None:
         """外部通知检测到用量上限错误.
@@ -125,7 +147,8 @@ class QuotaGuard:
                 )
             self._cap_error_active = True
             logger.warning(
-                "Quota guard: cap error detected → EXCEEDED (effective_probe=%ds)",
+                "Quota guard [%s]: cap error detected → EXCEEDED (effective_probe=%ds)",
+                self._window_label,
                 int(self._effective_probe_interval),
             )
 
@@ -139,12 +162,17 @@ class QuotaGuard:
             self._total += total_tokens
             if vendor:
                 logger.info(
-                    "Quota guard [%s]: loaded baseline %d tokens",
+                    "Quota guard [%s/%s]: loaded baseline %d tokens",
                     vendor,
+                    self._window_label,
                     total_tokens,
                 )
             else:
-                logger.info("Quota guard: loaded baseline %d tokens", total_tokens)
+                logger.info(
+                    "Quota guard [%s]: loaded baseline %d tokens",
+                    self._window_label,
+                    total_tokens,
+                )
 
     def reset(self) -> None:
         """手动重置为 WITHIN_QUOTA 状态."""
@@ -152,7 +180,10 @@ class QuotaGuard:
             self._transition_to(QuotaState.WITHIN_QUOTA)
             self._entries.clear()
             self._total = 0
-            logger.info("Quota guard: manually reset to WITHIN_QUOTA")
+            logger.info(
+                "Quota guard [%s]: manually reset to WITHIN_QUOTA",
+                self._window_label,
+            )
 
     def get_info(self) -> dict:
         """获取配额守卫状态信息."""

{coding_proxy-0.2.1a3 → coding_proxy-0.2.3a1}/src/coding/proxy/routing/router.py

@@ -68,6 +68,66 @@ class RequestRouter:
         """当前活跃供应商名称（由 Executor 在成功响应时写入）."""
         return self._active_vendor_name
 
+    # ── 运行时 N-tier 链路重排序 ─────────────────────────────
+
+    def get_vendor_names(self) -> list[str]:
+        """返回当前 tiers 的供应商名称列表（按优先级顺序）."""
+        return [t.name for t in self._tiers]
+
+    def reorder_tiers(self, vendor_names: list[str]) -> None:
+        """原地重排序 N-tier 链路.
+
+        使用切片赋值保持列表引用同一性，使 ``_RouteExecutor`` 立即可见。
+
+        Args:
+            vendor_names: 新的供应商名称顺序（必须包含所有当前 tier）。
+
+        Raises:
+            ValueError: 名称不存在、有重复、或未覆盖所有 tier。
+        """
+        name_to_tier = {t.name: t for t in self._tiers}
+        current_names = set(name_to_tier)
+
+        # 校验：重复
+        if len(vendor_names) != len(set(vendor_names)):
+            seen: set[str] = set()
+            dups = [n for n in vendor_names if n in seen or seen.add(n)]  # type: ignore[func-returns-value]
+            raise ValueError(f"vendor 名称重复: {', '.join(dups)}")
+
+        # 校验：名称存在性
+        unknown = [n for n in vendor_names if n not in current_names]
+        if unknown:
+            raise ValueError(
+                f"未知 vendor: {', '.join(unknown)}; "
+                f"可用: {', '.join(sorted(current_names))}"
+            )
+
+        # 校验：全量覆盖
+        provided = set(vendor_names)
+        if provided != current_names:
+            missing = current_names - provided
+            raise ValueError(f"缺少 vendor: {', '.join(sorted(missing))}")
+
+        self._tiers[:] = [name_to_tier[n] for n in vendor_names]
+
+    def promote_vendor(self, vendor_name: str) -> None:
+        """将指定 vendor 提升至最高优先级，其余保持相对顺序.
+
+        Args:
+            vendor_name: 要提升的供应商名称。
+
+        Raises:
+            ValueError: 名称不存在。
+        """
+        current_names = self.get_vendor_names()
+        if vendor_name not in current_names:
+            available = sorted(t.name for t in self._tiers)
+            raise ValueError(
+                f"未知 vendor: {vendor_name}; 可用: {', '.join(available)}"
+            )
+        new_order = [vendor_name] + [n for n in current_names if n != vendor_name]
+        self.reorder_tiers(new_order)
+
     # ── 公开路由接口（委托给 _RouteExecutor）───────────────
 
     async def route_stream(