coding-proxy 0.5.1a7__tar.gz → 0.5.2__tar.gz
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.
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/CHANGELOG.md +50 -1
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/PKG-INFO +5 -6
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/README.md +3 -4
- coding_proxy-0.5.2/assets/logo.svg +1 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/docs/.agents/issue.md +122 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/docs/.agents/knowledge-map.md +9 -19
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/docs/arch/design-patterns.md +2 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/docs/guide/api-reference.md +2 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/docs/guide/cli-reference.md +2 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/docs/guide/dashboard.md +14 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/docs/zh-CN/README.md +2 -3
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/pyproject.toml +1 -1
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/config/config.default.yaml +55 -34
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/config/session_policy.py +35 -1
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/model/__init__.py +2 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/model/vendor.py +15 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/routing/executor.py +78 -14
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/routing/quota_guard.py +31 -7
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/routing/retry.py +13 -4
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/routing/router.py +2 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/server/app.py +1 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/server/dashboard.py +355 -31
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/server/routes.py +48 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/vendors/antigravity.py +5 -2
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/vendors/base.py +2 -1
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/vendors/copilot.py +2 -1
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/vendors/zhipu.py +43 -35
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_antigravity.py +45 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_app_routes.py +219 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_quota_guard.py +68 -2
- coding_proxy-0.5.2/tests/test_retry.py +98 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_router_executor.py +366 -1
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_session_aware.py +24 -0
- coding_proxy-0.5.2/tests/test_vendor_helpers.py +107 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_zhipu.py +223 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/uv.lock +1 -1
- coding_proxy-0.5.1a7/AGENTS.md +0 -58
- coding_proxy-0.5.1a7/CLAUDE.md +0 -1
- coding_proxy-0.5.1a7/docs/.agents/browser-validation.md +0 -172
- coding_proxy-0.5.1a7/docs/.agents/reference-specifications.md +0 -16
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/.github/workflows/ci.yml +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/.github/workflows/coverage.yml +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/.github/workflows/release.yml +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/.gitignore +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/.pre-commit-config.yaml +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/LICENSE +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/assets/dashboard-v0.4.0.png +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/assets/model-calling-v0.5.0.png +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/assets/session-v0.4.0.png +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/docs/arch/config-reference.md +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/docs/arch/convert.md +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/docs/arch/routing.md +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/docs/arch/testing.md +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/docs/arch/vendors.md +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/docs/framework.md +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/docs/guide/monitoring.md +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/docs/guide/quickstart.md +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/docs/guide/vendors.md +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/docs/ops/ci-cd.md +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/docs/user-guide.md +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/__init__.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/__init__.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/__main__.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/auth/__init__.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/auth/providers/__init__.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/auth/providers/base.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/auth/providers/github.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/auth/providers/google.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/auth/runtime.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/auth/store.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/cli/__init__.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/cli/auth_commands.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/cli/banner.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/compat/__init__.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/compat/canonical.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/compat/session_store.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/config/__init__.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/config/auth_schema.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/config/loader.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/config/resiliency.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/config/routing.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/config/schema.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/config/server.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/config/vendors.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/convert/__init__.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/convert/anthropic_to_gemini.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/convert/anthropic_to_openai.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/convert/gemini_sse_adapter.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/convert/gemini_to_anthropic.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/convert/openai_to_anthropic.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/convert/vendor_channels.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/logging/__init__.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/logging/db.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/logging/formatters.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/logging/stats.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/model/auth.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/model/compat.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/model/constants.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/model/pricing.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/model/token.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/native_api/__init__.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/native_api/config.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/native_api/extractors/__init__.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/native_api/extractors/anthropic.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/native_api/extractors/gemini.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/native_api/extractors/openai.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/native_api/handler.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/native_api/operation.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/native_api/routes.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/native_api/usage_registry.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/pricing.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/routing/__init__.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/routing/circuit_breaker.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/routing/error_classifier.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/routing/model_mapper.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/routing/rate_limit.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/routing/session_manager.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/routing/session_policy.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/routing/tier.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/routing/usage_parser.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/routing/usage_recorder.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/server/__init__.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/server/factory.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/server/responses.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/streaming/__init__.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/streaming/anthropic_compat.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/vendors/__init__.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/vendors/alibaba.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/vendors/anthropic.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/vendors/concurrency.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/vendors/copilot_models.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/vendors/copilot_token_manager.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/vendors/copilot_urls.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/vendors/doubao.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/vendors/kimi.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/vendors/minimax.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/vendors/mixins.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/vendors/native_anthropic.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/vendors/token_manager.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/src/coding/proxy/vendors/xiaomi.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/__init__.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/e2e/__init__.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/e2e/conftest.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/e2e/test_e2e_http.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/e2e/test_e2e_token.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/e2e/test_e2e_vendor.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_auto_login.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_banner.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_circuit_breaker.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_cli_usage.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_compat.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_concurrency_monitor.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_config_init.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_config_loader.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_convert_request.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_convert_response.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_convert_sse.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_copilot.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_copilot_convert_request.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_copilot_convert_response.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_copilot_models.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_copilot_urls.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_currency.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_error_classifier.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_executor_in_flight_tracking.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_logging_dual_write.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_mixins.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_model_auth.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_model_compat.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_model_constants.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_model_mapper.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_model_pricing.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_model_token.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_model_vendor.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_native_api_base_url_override.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_native_api_extractors.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_native_api_handler.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_native_api_operation.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_native_api_routes.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_native_vendors.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_parse_usage.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_parse_usage_gemini.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_pricing.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_rate_limit.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_router_chain.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_runtime_reauth.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_schema.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_streaming_anthropic_compat.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_tier.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_tiers_config.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_time_range.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_token_logger.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_token_logger_native_columns.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_token_manager.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_types.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_vendor_channels.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_vendor_streaming.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_vendors.py +0 -0
- {coding_proxy-0.5.1a7 → coding_proxy-0.5.2}/tests/test_zhipu_concurrency.py +0 -0
|
@@ -2,13 +2,62 @@
|
|
|
2
2
|
|
|
3
3
|
本文件基于 [Keep a Changelog](https://keepachangelog.com/zh-CN/) 规范维护,版本号遵循 [语义化版本](https://semver.org/lang/zh-CN/)。
|
|
4
4
|
|
|
5
|
-
## [
|
|
5
|
+
## [v0.5.2](https://github.com/ThreeFish-AI/coding-proxy/releases/tag/v0.5.2) - 2026-09-10
|
|
6
6
|
|
|
7
|
+
- fix(quota-guard): `coding-proxy reset` / `POST /api/reset` 不再清空配额守卫的滑动窗口用量——根因是 `QuotaGuard.reset()` 把「状态机复位」与「用量计数清零」耦合在一个方法里(`_entries.clear()` + `_total = 0`),而窗口基线 `load_baseline()` 的唯一调用点在进程启动的 lifespan 钩子中、运行期不再回填,导致 Dashboard 的 `1d配额 45%` 徽章复位后永久停在 0%;现 `reset()` 只保留 `_transition_to(WITHIN_QUOTA)`(该方法本身已清 `_cap_error_active` 并还原探测间隔),CLI / API / Dashboard 三条路径经单一事实源同时修复。语义取舍为**如实**:用量确已超过 `token_budget × threshold_percent` 时守卫保持 `QUOTA_EXCEEDED`(不伪造用量数字),但仍清除上游 cap 错误卡死标志并把被 `Retry-After` 拉长的探测间隔还原为默认值——刻意不走 WITHIN_QUOTA → QUOTA_EXCEEDED 回环,因为 `_transition_to(EXCEEDED)` 会把 `_last_probe` 刷成当前时刻,令探测恢复凭空推迟一个 probe_interval,反复复位即可饿死探测(PR 评审发现的回归,补 2 条用例锁定);文档口径(`cli-reference.md` / `api-reference.md`)同步补明「仅复位状态、不清用量」;
|
|
8
|
+
- feat(dashboard): Overview 页「供应商状态」卡片标题栏右侧新增 **⟲ 状态复位** 按钮,一键把处于熔断 / 限流等异常态的供应商复位为可正常访问——调用无 body 的 `POST /api/reset`,因此**不触发重排序、不改动供应商优先级**,配合上述配额修复亦**不清空额度用量**;新增 `.btn-card-action` 卡片标题栏控件通用类(复用 `.card-title` 既有的 `justify-content: space-between`,零布局 CSS 改动)并纳入 `:focus-visible` 焦点环列表;交互沿用 `persistTierOrder` 的 in-flight 防并发范式与 `copyFromParent` 的瞬时反馈范式(复位中… → ✓ 已复位 / ✗ 失败,1.5s 还原),成功后定向重渲染供应商列表而不必等 10 分钟轮询;定向刷新 `/api/status` 失败时单独吞掉、不误报「✗ 失败」诱导重复点击(复位已生效,刷新失败仅影响展示)(实机验证);
|
|
9
|
+
- fix(dashboard): 修复「限速中」徽章从未渲染的问题——前端读 `rlInfo.limited`,而后端 `VendorTier.get_rate_limit_info()` 产出的键是 `is_rate_limited`,键名不匹配使 Rate Limit 异常态在 UI 上完全不可观测;补前端守卫测试锁定键名;
|
|
10
|
+
|
|
11
|
+
> [!NOTE]
|
|
12
|
+
> 本版为 v0.5.2 周期(v0.5.2a1–a8)的正式收口版,完整变更见上方各 alpha 段落;以下条目为 v0.5.2a8 之后的增量(#279)。
|
|
13
|
+
|
|
14
|
+
## [v0.5.2a8](https://github.com/ThreeFish-AI/coding-proxy/releases/tag/v0.5.2a8) - 2026-07-06
|
|
15
|
+
|
|
16
|
+
- fix(vendor-logging): 修复流式 4xx/5xx 错误日志中文乱码——根因是 `logger.warning("...body=%s...", error_body[:500])` 对 `bytes` 走 `repr()`,非 ASCII 的 UTF-8 字节被转义为 `\xe6\x82\xa8` 之类不可读序列(上游限流/鉴权等中文错误信息无法辨认);新增 `decode_error_body(raw, limit=500)` 工具(`errors="replace"` 容错解码、先整体解码再按字符截断以避免在多字节 UTF-8 边界切断产生二次乱码,`limit` 语义为字符数),`base.py` / `copilot.py` / `antigravity.py` 三处流式错误日志统一收敛,并经 `model/__init__` 与 `vendors/base` 导出复用 (#278);
|
|
17
|
+
- fix(vendor-antigravity): 流式 scope 检测改用完整解码 body,与日志展示的 500 字符截断解耦——此前 `decode_error_body` 截断后的文本被同时喂给 `_mark_scope_error_if_needed` 子串检测,当 `ACCESS_TOKEN_SCOPE_INSUFFICIENT` 标记位于第 500 字符之后时会被截断丢弃,token 不再标记 `needs_reauth` 而持续以 scope 不足的凭证重试;现检测改用 `error_body.decode("utf-8", errors="replace")` 完整文本、日志展示仍用 500 截断,恢复与非流式路径(`send_message` 传完整 `response.text`)的行为一致性;补回归测试(构造标记位于 500 字符之后的 403 错误体,断言检测仍触发,旧截断实现下该用例失败)(#278);
|
|
18
|
+
|
|
19
|
+
## [v0.5.2a7](https://github.com/ThreeFish-AI/coding-proxy/releases/tag/v0.5.2a7) - 2026-07-04
|
|
20
|
+
|
|
21
|
+
- style(dashboard): Overview 页 6 张 KPI 卡片(今日请求数 / Token 总量 / 输出 Token / 费用估算 / 故障转移 / 平均延迟)固定单行不折行——`.kpi-grid` 由 `repeat(auto-fit, minmax(200px, 1fr))`(视口 < ~1289px 即减列换行)改为 `repeat(6, minmax(0, 1fr))`,`minmax(0,…)` 覆盖 grid 默认 `min-width:auto` 杜绝内容撑列引发的横向溢出,桌面/笔记本/平板横屏(≥1024px)恒定 6 列单行;`gap` 由 off-grid 的 `5px` 归一为 `--gap-section`(12px);`.kpi-value` 采用 `clamp(20px, 2.2vw, 32px)` 平滑缩放使中宽度不裁剪数值,费用卡 `#kpi-cost-today` 允许在 `" + "` 处换行使双币种始终完整可见;新增 ≤1023px→3 列、≤480px→2 列 优雅降级,`header` 补 `flex-wrap` 修复窄屏横向溢出(Playwright 8 档宽度实测:1440/1280/1024px 均 6 列单行、无横向滚动、无数值裁剪)(#276);
|
|
22
|
+
- a11y(dashboard): 为 `.range-btn` / `.btn-refresh` / `.page-btn` / `.copy-btn` 补 `:focus-visible` 键盘焦点环,统一交互元素键盘可达性;新增 `@media (prefers-reduced-motion: reduce)` 降级 `fadeInUp` 动画与 hover 过渡,照顾前庭敏感用户 (#276);
|
|
23
|
+
- fix(dashboard): 补定义 `--bg-secondary` / `--text-muted` 两个此前**未定义**的 CSS 变量(消除 `.mc-model-row` / `.mc-empty` 背景与文字色回退瑕疵);Google Fonts 补载 JetBrains Mono `700` 字重,修正 `.kpi-value` 合成粗体渲染 (#276);
|
|
24
|
+
- docs(readme): 页脚补充作者主页(ThreeFish-AI)与 Apache License 2.0 开源协议超链接;
|
|
25
|
+
|
|
26
|
+
## [v0.5.2a6](https://github.com/ThreeFish-AI/coding-proxy/releases/tag/v0.5.2a6) - 2026-07-04
|
|
27
|
+
|
|
28
|
+
- style(branding): 品牌图标(logo/favicon)迭代至「通透青绿圆环 + Tabler prompt `>_` 笔划」(方案 d05):全透明底 + 青绿渐变(`#22d3ee` → `#2dd4bf`)细圆环(stroke 0.5,仅原 1/3、通透若隐)+ 饱和青绿渐变 `>_`(stroke 2.5),极细环与饱和笔划形成权重对比、`>_` 为视觉主角,青绿承载终端/代码语义;基础笔划改用 Tabler prompt(chevron `M5 7l5 5l-5 5` + 下划线 `M13 17l6 0`,下划线长 6 单位、不会小尺寸点化);渐变改 `gradientUnits="userSpaceOnUse"` 绝对坐标,修复纯水平下划线(包围盒高度 0)在默认 objectBoundingBox 渐变下不着色而「消失」的问题;`_LOGO_DEFS` / `_PROMPT_PATHS` 单一事实源统一供 SVG favicon、ICO 回退(省略 0.5px 细环、保留饱和笔划)与页面 logo 消费;`.logo` 容器改全透明、SVG 内嵌圆环 + 青绿 drop-shadow 辉光(实机验证)(#274);
|
|
29
|
+
- style(branding): 品牌图标醒目度前置优化(同主题演进过程,已并入本版):容器由「淡色磨砂卡片」改为「玻璃雾卡」(半透明白 + hairline 描边环)与深色毛玻璃 header 语言统一、消除「亮白贴片」压制感,`>_` 笔划加粗 stroke-width 2→2.5 并撑开间距避免粘连、防止下划线小尺寸退化为圆点 (#274);
|
|
30
|
+
|
|
31
|
+
## [v0.5.2a5](https://github.com/ThreeFish-AI/coding-proxy/releases/tag/v0.5.2a5) - 2026-07-04
|
|
32
|
+
|
|
33
|
+
- fix(dashboard): 供应商队列拖拽由原生 HTML5 DnD 改为 Pointer Events 实现,修复 v0.5.2a4 引入的拖拽排序功能在浏览器中无法拖动的问题;引入 4px 拖拽阈值、乐观实时重排与指针捕获机制,同步支持触屏设备;拖拽完成后顺序立即影响 cc 运行时供应商优先级调度(实机验证);为 `/dashboard` 响应增加 `Cache-Control: no-cache`,防止浏览器缓存旧内联脚本;补齐前端守卫测试断言 (#271);
|
|
34
|
+
- style(branding): 重设计 logo/favicon 为 `#f5f6fb` 淡色磨砂卡片 + 品牌渐变(`#667eea` → `#764ba2`)`>_` 笔划 + 半透明细描边环,轮廓成为视觉主角、小尺寸下更清晰(Linear/Vercel 风);抽取 `_LOGO_DEFS` 作为品牌渐变 `<defs>` 单一事实源,统一供 SVG favicon、ICO 回退与页面 logo 消费 (#272);
|
|
35
|
+
|
|
36
|
+
## [v0.5.2a4](https://github.com/ThreeFish-AI/coding-proxy/releases/tag/v0.5.2a4) - 2026-07-03
|
|
37
|
+
|
|
38
|
+
- feat(dashboard): 供应商状态模块支持拖拽调整供应商优先级,新增纯重排序端点 `PUT /api/tier-order`(复用 `router.reorder_tiers`,不重置熔断器/配额守卫/rate limit),拖拽后配额与用量统计保持当日值不变;与 `reset -v` 同源、运行时内存生效,失败自动回滚至服务端真实顺序 (#269);
|
|
39
|
+
- feat(session): 扩充标题豁免前缀,新增 `[Session]` 过滤注入式 Prompt 候选;
|
|
40
|
+
- chore(pricing): 更新智谱 GLM-5.2 模型定价配置;
|
|
41
|
+
|
|
42
|
+
## [v0.5.2a3](https://github.com/ThreeFish-AI/coding-proxy/releases/tag/v0.5.2a3) - 2026-07-02
|
|
43
|
+
|
|
44
|
+
- fix(session): 标题豁免前缀扩展至全层级兜底标题,修复 `[Session] <model>` 等 Level 4 合成标题无法豁免(原 `title_exempt_prefixes` 仅 Level 1 生效);改为在 `_extract_session_title` 编排层对 L1/L2/L3/L4 候选统一拦截,命中回退、全豁免返回空串待后续真实输入回填,默认行为零影响 (#267);
|
|
45
|
+
|
|
46
|
+
## [v0.5.2a2](https://github.com/ThreeFish-AI/coding-proxy/releases/tag/v0.5.2a2) - 2026-07-02
|
|
47
|
+
|
|
48
|
+
- feat(session): 新增 Session 标题豁免前缀配置 `title_exempt_prefixes`,过滤注入式 Prompt(典型如 "Write the title in the language the user wrote in...")被误用为 Session 标题;首条 user 输入经噪声剥离后命中豁免前缀则跳过、继续向后查找 title 候选,Level 2/3/4 回退不受影响 (#265);
|
|
49
|
+
|
|
50
|
+
## [v0.5.2a1](https://github.com/ThreeFish-AI/coding-proxy/releases/tag/v0.5.2a1) - 2026-06-30
|
|
51
|
+
|
|
52
|
+
- fix(zhipu): 将 429/529 兜底退避抖动从 Full Jitter 改为 Equal Jitter(`[0, ceiling]` → `[ceiling/2, ceiling]`),修复 529 过载重试延迟非单调(实测 418.8→1857.7→961.6→3769.7ms)问题,重试延迟呈单调非递减指数形态;429 与 529 共用退避路径同步受益,server `retry-after` 优先级不变 (#263);
|
|
7
53
|
- feat(dashboard): Model Calling 实时监控扩展至全 vendor / 全 model(仅 CC 场景),其他 vendor 在 monitor 模式下仅计数不限流,Zhipu 保留 limited 模式 + FIFO 排队;
|
|
8
54
|
- feat(concurrency): 新增 `peak_pending_recent` 最近 10s 排队峰值追踪,瞬时排队释放后前端仍可见"曾排队 N" 余晖徽章;
|
|
9
55
|
- perf(dashboard): Model Calling 轮询间隔由 5000ms 缩短至 1500ms,提升瞬时排队可观测性;
|
|
10
56
|
- refactor(vendors): `ModelConcurrencyLimiter` 重构为 `ModelConcurrencyController`,统一 monitor / limited 双模式抽象(保留旧名别名);并发控制由 vendor 内部迁移至 executor 层 `track_in_flight` 包裹,行为对所有 vendor 一致;
|
|
11
57
|
|
|
58
|
+
> [!NOTE]
|
|
59
|
+
> 本版另补记 v0.5.1 Release Note 遗漏的 4 项并发与监控改动(feat/perf/refactor,代码已随 v0.5.1 上线,文档此前未记录)。
|
|
60
|
+
|
|
12
61
|
## [v0.5.0](https://github.com/ThreeFish-AI/coding-proxy/releases/tag/v0.5.0) - 2026-05-27
|
|
13
62
|
|
|
14
63
|
> [!IMPORTANT]
|
|
@@ -1,6 +1,6 @@
|
|
|
1
|
-
Metadata-Version: 2.
|
|
1
|
+
Metadata-Version: 2.5
|
|
2
2
|
Name: coding-proxy
|
|
3
|
-
Version: 0.5.
|
|
3
|
+
Version: 0.5.2
|
|
4
4
|
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...
|
|
5
5
|
Project-URL: Source Code, https://github.com/ThreeFish-AI/coding-proxy
|
|
6
6
|
Project-URL: User Guide, https://github.com/ThreeFish-AI/coding-proxy/blob/master/docs/user-guide.md
|
|
@@ -29,7 +29,7 @@ Description-Content-Type: text/markdown
|
|
|
29
29
|
|
|
30
30
|
<div align="center">
|
|
31
31
|
|
|
32
|
-
#
|
|
32
|
+
# <img src="assets/logo.svg" alt="coding-proxy" width="32" height="32" align="absmiddle"> coding-proxy
|
|
33
33
|
|
|
34
34
|
**A High-Availability, Transparent, and Smart Multi-Vendor Proxy for Claude Code**
|
|
35
35
|
|
|
@@ -152,7 +152,7 @@ graph RL
|
|
|
152
152
|
|
|
153
153
|
Client["💻<br/>Client (Claude Code)"]:::client
|
|
154
154
|
|
|
155
|
-
subgraph CodingProxy["
|
|
155
|
+
subgraph CodingProxy["coding-proxy"]
|
|
156
156
|
direction RL
|
|
157
157
|
|
|
158
158
|
Router["RequestRouter<br/><code>routing/router.py</code>"]:::router
|
|
@@ -202,7 +202,6 @@ To ensure this project outlives us all (long-term maintainability), we offer exh
|
|
|
202
202
|
|
|
203
203
|
- 📖 **[User Guide](./docs/user-guide.md)** — From installation and bare-minimum configs to the semantic breakdown of every `config.yaml` field and common troubleshooting manuals. (Currently in Chinese)
|
|
204
204
|
- 🏗️ **[Architecture Framework](./docs/framework.md)** — A meticulous decoding of underlying design patterns (Template Method, Circuit Breaker, State Machine, etc.), targeted at devs who want to peek into the matrix or contribute new vendors. (Currently in Chinese)
|
|
205
|
-
- 🤝 **[Engineering Guidelines (AGENTS.md)](./AGENTS.md)** — The systemic context mindset and AI Agent collaboration protocol. It preaches **refactoring, reuse, and orthogonal abstractions** and serves as the ultimate guiding light for all development in this repository.
|
|
206
205
|
|
|
207
206
|
---
|
|
208
207
|
|
|
@@ -216,5 +215,5 @@ During our chaotic yet rewarding exploration of engineering practices, we were h
|
|
|
216
215
|
---
|
|
217
216
|
|
|
218
217
|
<div align="center">
|
|
219
|
-
<sub>Built with 🧠, ❤️, and an absurd amount of coffee by ThreeFish-AI </sub>
|
|
218
|
+
<sub>Built with 🧠, ❤️, and an absurd amount of coffee by <a href="https://github.com/ThreeFish-AI">ThreeFish-AI</a> · Released under the <a href="./LICENSE">Apache License 2.0</a>.</sub>
|
|
220
219
|
</div>
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
<div align="center">
|
|
4
4
|
|
|
5
|
-
#
|
|
5
|
+
# <img src="assets/logo.svg" alt="coding-proxy" width="32" height="32" align="absmiddle"> coding-proxy
|
|
6
6
|
|
|
7
7
|
**A High-Availability, Transparent, and Smart Multi-Vendor Proxy for Claude Code**
|
|
8
8
|
|
|
@@ -125,7 +125,7 @@ graph RL
|
|
|
125
125
|
|
|
126
126
|
Client["💻<br/>Client (Claude Code)"]:::client
|
|
127
127
|
|
|
128
|
-
subgraph CodingProxy["
|
|
128
|
+
subgraph CodingProxy["coding-proxy"]
|
|
129
129
|
direction RL
|
|
130
130
|
|
|
131
131
|
Router["RequestRouter<br/><code>routing/router.py</code>"]:::router
|
|
@@ -175,7 +175,6 @@ To ensure this project outlives us all (long-term maintainability), we offer exh
|
|
|
175
175
|
|
|
176
176
|
- 📖 **[User Guide](./docs/user-guide.md)** — From installation and bare-minimum configs to the semantic breakdown of every `config.yaml` field and common troubleshooting manuals. (Currently in Chinese)
|
|
177
177
|
- 🏗️ **[Architecture Framework](./docs/framework.md)** — A meticulous decoding of underlying design patterns (Template Method, Circuit Breaker, State Machine, etc.), targeted at devs who want to peek into the matrix or contribute new vendors. (Currently in Chinese)
|
|
178
|
-
- 🤝 **[Engineering Guidelines (AGENTS.md)](./AGENTS.md)** — The systemic context mindset and AI Agent collaboration protocol. It preaches **refactoring, reuse, and orthogonal abstractions** and serves as the ultimate guiding light for all development in this repository.
|
|
179
178
|
|
|
180
179
|
---
|
|
181
180
|
|
|
@@ -189,5 +188,5 @@ During our chaotic yet rewarding exploration of engineering practices, we were h
|
|
|
189
188
|
---
|
|
190
189
|
|
|
191
190
|
<div align="center">
|
|
192
|
-
<sub>Built with 🧠, ❤️, and an absurd amount of coffee by ThreeFish-AI </sub>
|
|
191
|
+
<sub>Built with 🧠, ❤️, and an absurd amount of coffee by <a href="https://github.com/ThreeFish-AI">ThreeFish-AI</a> · Released under the <a href="./LICENSE">Apache License 2.0</a>.</sub>
|
|
193
192
|
</div>
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24"><defs><linearGradient id="cpBrand" gradientUnits="userSpaceOnUse" x1="4" y1="4" x2="20" y2="20"><stop offset="0" stop-color="#22d3ee"/><stop offset="1" stop-color="#2dd4bf"/></linearGradient></defs><circle cx="12" cy="12" r="11" fill="none" stroke="url(#cpBrand)" stroke-width="0.5" stroke-opacity=".55"/><g fill="none" stroke="url(#cpBrand)" stroke-width="2.5" stroke-linecap="round" stroke-linejoin="round"><path d="M5 7l5 5l-5 5" /><path d="M13 17l6 0" /></g></svg>
|
|
@@ -4,6 +4,128 @@
|
|
|
4
4
|
|
|
5
5
|
---
|
|
6
6
|
|
|
7
|
+
## `coding reset` 误清配额窗口用量(Dashboard 配额百分比归零且不自愈)
|
|
8
|
+
|
|
9
|
+
**问题描述**
|
|
10
|
+
|
|
11
|
+
执行 `coding-proxy reset`(含 `-v anthropic,zhipu` 形态)后,Dashboard「供应商状态」卡片里 zhipu 的「1d配额 45%」徽章掉到 **0%**,且不会随时间恢复。用户预期该指令只复位熔断等异常状态,不应触碰额度记录。
|
|
12
|
+
|
|
13
|
+
**表因**
|
|
14
|
+
|
|
15
|
+
`/api/status` 的 `quota_guard.usage_percent` 由 `QuotaGuard.get_info()` 从内存字段 `_total` 计算,reset 后 `_total` 为 0。
|
|
16
|
+
|
|
17
|
+
**根因**
|
|
18
|
+
|
|
19
|
+
`QuotaGuard.reset()`(`routing/quota_guard.py`)把**状态机复位**与**用量计数清零**两件正交的事耦合在了一个方法里:
|
|
20
|
+
|
|
21
|
+
```python
|
|
22
|
+
self._transition_to(QuotaState.WITHIN_QUOTA)
|
|
23
|
+
self._entries.clear() # ← 连带清空滑动窗口
|
|
24
|
+
self._total = 0 # ← 用量归零
|
|
25
|
+
```
|
|
26
|
+
|
|
27
|
+
之所以「不自愈」,是因为窗口基线 `load_baseline()` 的**唯一**调用点在 `server/app.py` 的 lifespan 启动钩子里 —— 进程运行期间不会再回填,只能靠新请求从 0 重新累加。文档口径(`cli-reference.md` / `api-reference.md`)自始至终只承诺「配额守卫**状态** → WITHIN_QUOTA」,从未声明会清空用量,**实现与契约不一致**。
|
|
28
|
+
|
|
29
|
+
CLI `reset` 只是 `POST /api/reset` 的瘦 HTTP 客户端,`/api/reset` 又对全部 tier 调 `quota_guard.reset()` + `weekly_quota_guard.reset()`,故 CLI 与 API 两条路径同时中招。
|
|
30
|
+
|
|
31
|
+
**处理方式**
|
|
32
|
+
|
|
33
|
+
在 `QuotaGuard.reset()` 中删除 `_entries.clear()` / `_total = 0` 两行,只保留 `_transition_to(QuotaState.WITHIN_QUOTA)`(该方法本身已负责清 `_cap_error_active` 并还原 `_effective_probe_interval`)。**单一事实源修复**:CLI、`/api/reset`、Dashboard 新增的「状态复位」按钮三条路径自动同时受益,无需各自加 `--keep-quota` 之类开关。
|
|
34
|
+
|
|
35
|
+
语义取舍:用量确已超过 `budget × threshold` 时,复位后守卫**保持** `QUOTA_EXCEEDED`(即「点了没反应」)。这是**如实**行为 —— 宁可不放行,也不伪造用量数字;但仍会清除 cap 错误卡死标志(`_cap_error_active`,正是 5h 限额型 vendor 的主要卡死来源)并把被 `Retry-After` 拉长的探测间隔还原为默认值。
|
|
36
|
+
|
|
37
|
+
**评审回归(PR #279)**:初版修复让 `reset()` 无条件 `_transition_to(WITHIN_QUOTA)`,用量仍超阈值时下一次判定再回落 `QUOTA_EXCEEDED` —— 而该回环会把 `_last_probe` 刷成当前时刻,令探测恢复凭空推迟一个 `probe_interval`(默认 300s),反复点击「状态复位」可**无限饿死探测**(旧实现清零用量,不存在此回环)。教训:**改「复位」语义时必须检查状态机每条转移的附带副作用**(`_transition_to` 不是纯赋值,EXCEEDED 分支带 `_last_probe = now`),修复后的 `reset()` 在用量仍超阈值时只清 `_cap_error_active` 与 `_effective_probe_interval`、不触发任何状态转移;补 `test_reset_does_not_delay_probe_when_over_budget`(mock 时钟断言探测点不被推后)与 `test_reset_still_clears_cap_stall_when_over_budget` 两条回归用例。
|
|
38
|
+
|
|
39
|
+
**后续防范**
|
|
40
|
+
|
|
41
|
+
- **写操作测试须补「不误伤其他运行时状态」守卫断言**:`tests/test_app_routes.py::test_tier_order_preserves_quota_guard` 早已是这一范式的样板,但 `/api/reset` 侧长期缺失同类断言,缺陷才得以潜伏。新增写端点时,除「改了什么」外必须同时断言「没改什么」。
|
|
42
|
+
- **警惕「状态机复位」与「计数清零」的耦合**:`reset()` 这类命名天然模糊。凡是同时持有状态字段与累计计数的组件(`CircuitBreaker` 的 `_failure_count` 属于状态、`QuotaGuard` 的 `_total` 属于观测数据),复位语义须显式区分二者。
|
|
43
|
+
- **旧测试固化了错误行为**:`test_reset_clears_all_state` 曾断言 `window_usage_tokens == 0`,等于把缺陷写成契约。修复时应先让新测试在旧实现下 FAIL,确认其真正咬住缺陷。
|
|
44
|
+
|
|
45
|
+
**同类问题影响与处理注意事项**
|
|
46
|
+
|
|
47
|
+
- **不可用线上进程验证**:`/api/reset` 会永久抹掉运行中进程的配额基线(直到重启)。验证须另起隔离实例(独立端口 + `/tmp` 数据库),严禁对用户正在使用的代理进程执行 reset。
|
|
48
|
+
- **`weekly_quota_guard` 复用同一个类**,修复自动覆盖周级守卫,无需单独处理。
|
|
49
|
+
- **`-v` 的重排序语义未变**:`-v` 仍是「提升/替换 N-tier 链路顺序」,不是「只复位这几个 vendor」的过滤器;Dashboard 按钮走无 body 路径,因此不触碰优先级。
|
|
50
|
+
|
|
51
|
+
**关联缺陷(同批修复)**
|
|
52
|
+
|
|
53
|
+
Dashboard 的「限速中」徽章读 `rlInfo.limited`,而后端 `VendorTier.get_rate_limit_info()` 产出的键是 `is_rate_limited` —— 键名不匹配导致该徽章**从未渲染过**,Rate Limit 异常态在 UI 上完全不可观测。已同步修正为 `rlInfo.is_rate_limited`。
|
|
54
|
+
|
|
55
|
+
## Session 标题豁免前缀对 `[Session]` 兜底标题不生效(豁免仅 Level 1 生效)
|
|
56
|
+
|
|
57
|
+
**问题描述**
|
|
58
|
+
|
|
59
|
+
用户在 `session_policies.title_exempt_prefixes` 配置中加入 `"[Session]"`,期望过滤掉 `[Session] claude-opus-4-8` 这类不预期标题(此前已用同机制成功豁免 `Write the title in the language ...` 注入式 Prompt)。但配置后无效——`[Session] claude-opus-4-8` 仍被写入 Session 标题。
|
|
60
|
+
|
|
61
|
+
**表因**
|
|
62
|
+
|
|
63
|
+
`[Session] claude-opus-4-8` **不是用户输入**,而是标题提取 Level 4 元数据兜底(`_extract_title_from_metadata`,`f"[Session] {request.model}"`)的产物。用户误以为它来自 user 文本,故尝试用 `title_exempt_prefixes` 豁免。
|
|
64
|
+
|
|
65
|
+
**根因**
|
|
66
|
+
|
|
67
|
+
`_extract_session_title`(`routing/executor.py`)采用 4 层回退,但 `exempt_prefixes` **仅在 Level 1**(`_extract_title_from_user_text`)消费——这是原始设计:v0.5.2a1 #265 引入该配置时仅覆盖 L1,docstring 明写「Level 2/3/4 不参与豁免」。Level 2/3/4 的合成标题(`[Tool output]` / `[N Image]` / `[Tool call]` / `[Session]`)完全不查询豁免名单。故用户配的 `"[Session]"` 只进到 L1,对 L4 兜底标题毫无作用——这是「配了却不生效」的根本原因,**非配置错误**。
|
|
68
|
+
|
|
69
|
+
**处理方式**
|
|
70
|
+
|
|
71
|
+
在 `_extract_session_title` 编排层引入 `_is_exempt` 闭包,对 L1/L2/L3/L4 每层候选统一做大小写敏感 `startswith` 拦截,命中则向下一层回退、全豁免返回空串。返回空串触发调用方 `if title:` 跳过写库,标题保持空,待后续请求带真实 user 文本时经 `update_empty_session_title` 回填。L1 内部「逐条消息跳过」语义不变,外层闭包作一致性兜底;并补入参空串前缀防御。**默认行为零影响**(不添加前缀则不豁免);**不**把合成前缀塞进默认 config,避免误杀正常 `[Tool output]` 标题。新增 8 个回归测试(含 mock recorder 验证写库跳过)。
|
|
72
|
+
|
|
73
|
+
**后续防范**
|
|
74
|
+
|
|
75
|
+
- **新增合成兜底标题须纳入豁免链路**:未来若在 L2/L3/L4 增加新的 `f"[Xxx] ..."` 合成标题,编排层的 `_is_exempt` 自动覆盖(无需改子函数),但应在 `config.default.yaml` 注释里补充示例前缀,提示用户可豁免。
|
|
76
|
+
- **空串前缀恒真陷阱**:`"".startswith` 恒真会豁免一切。配置层 field_validator、构造器、模块函数入参已三重过滤,任何新增的 startswith 豁免/绑定逻辑都须保留空串防御。
|
|
77
|
+
|
|
78
|
+
**同类问题影响与处理注意事项**
|
|
79
|
+
|
|
80
|
+
- **`[Session] <model>` 触发条件**:请求无可提取的 user TEXT / TOOL_RESULT / IMAGE / tool_names,只剩 model 字段(典型如首条消息全是 `<system-reminder>` 噪声、或仅 assistant 消息的续接请求)。排查此类标题应优先确认请求体内容,而非怀疑配置。
|
|
81
|
+
- **豁免语义边界**:豁免 =「跳过该候选、继续向下一层回退」,非「替换为别的标题」。L4 是最后一层,被豁免只能落到空串;依赖标题触发 `_apply_title_based_policy` 供应商自动绑定的场景,空标题不会触发绑定(预期副作用,语义自洽)。
|
|
82
|
+
- **不要把合成前缀写进默认配置**:`[Tool output]` 等对用户有信息量,默认豁免会造成正常工具结果摘要标题消失的回归。
|
|
83
|
+
|
|
84
|
+
---
|
|
85
|
+
|
|
86
|
+
## Zhipu 529 过载重试退避非单调(对齐 429 指数退避语义)
|
|
87
|
+
|
|
88
|
+
**问题描述**
|
|
89
|
+
|
|
90
|
+
cc 调用 zhipu 返回 529 过载触发重试时,延迟序列呈非单调形态(实测 `418.8ms → 1857.7ms → 961.6ms → 3769.7ms`,第 3 次反而短于第 2 次),不像 429 那样呈现干净的指数退避。
|
|
91
|
+
|
|
92
|
+
**表因**
|
|
93
|
+
|
|
94
|
+
`src/coding/proxy/routing/retry.py::calculate_delay` 的兜底抖动为 **Full Jitter**:`delay = random.uniform(0, ceiling)`,每次延迟是 `[0, ceiling]` 区间均匀随机值,本质非单调。实测值逐项精确匹配 `attempt 0/1/2/3` 的 `uniform(0,1000)/(0,2000)/(0,4000)/(0,8000)`。
|
|
95
|
+
|
|
96
|
+
**根因**
|
|
97
|
+
|
|
98
|
+
关键认知修正:429 与 529 在代码层面**早已共用同一退避路径** `ZhipuVendor._compute_retry_delay_from_headers`(`vendors/zhipu.py:230-247`),并非"两套规则"。感知差异来自两个因素叠加:
|
|
99
|
+
|
|
100
|
+
1. **服务端响应头不对称**:429(限流)响应通常携带 `Retry-After` 头 → 走确定性 server-guided 路径(`retry_after * 1.1`),看起来"干净递增";529(过载)响应通常**不携带**该头 → 落入 Full Jitter 兜底分支。
|
|
101
|
+
2. **Full Jitter 本身非单调**:即使 429 也一样,只是 429 多数情况有 `Retry-After` 遮蔽了该问题。
|
|
102
|
+
|
|
103
|
+
故真正修复对象是共享的抖动策略,而非给 529 单独加逻辑。
|
|
104
|
+
|
|
105
|
+
**处理方式**
|
|
106
|
+
|
|
107
|
+
将 `calculate_delay` 从 Full Jitter 改为 **Equal Jitter**(AWS M. Brooker, "Exponential Backoff And Jitter," 2015):
|
|
108
|
+
|
|
109
|
+
```
|
|
110
|
+
temp = min(initial * backoff^attempt, max)
|
|
111
|
+
delay = temp/2 + random.uniform(0, temp/2) # [temp/2, temp]
|
|
112
|
+
```
|
|
113
|
+
|
|
114
|
+
Zhipu 配置下区间变为 `[500,1000] → [1000,2000] → [2000,4000] → [4000,8000]`,相邻区间仅边界相切,延迟几乎必然单调非递减;保留抖动以防惊群;429/529 同步受益;`retry-after` 优先级链不动。同步更新 `retry.py` / `zhipu.py` 共 4 处 "Full Jitter" docstring,新增 `tests/test_retry.py` 独立单元测试与 `test_zhipu.py::test_529_equal_jitter_delay_in_expected_band`。
|
|
115
|
+
|
|
116
|
+
**后续防范**
|
|
117
|
+
|
|
118
|
+
- **单调性是配置相关的弱保证**:依赖 `backoff_multiplier >= 2.0` 且未触及 `max_delay_ms` 封顶。封顶后(`initial*2^attempt >= max`)各 attempt 区间退化为同一 `[max/2, max]`,单调性丧失。当前 Zhipu `max_retries=4` 触及不到,但未来调参须注意。函数 docstring 已写明此契约边界。
|
|
119
|
+
- **诚实权衡(Brooker 反方观点)**:Brooker 2015 分布式吞吐基准显示 Full Jitter 优于 Equal Jitter。但本场景是单代理(CC)低并发过载恢复,诉求是可解释性(日志递增可预测)而非分布式吞吐最优,CC 并发量级远未达"海量",差异在噪声内。若未来观测到并发过载下的惊群回归,应优先要求 server 提供 `retry-after` 或评估 Decorrelated Jitter,而非回退 Full Jitter。
|
|
120
|
+
|
|
121
|
+
**同类问题影响与处理注意事项**
|
|
122
|
+
|
|
123
|
+
- **双 `RetryConfig` 死代码(重要遗留债)**:仓库存在两个 `RetryConfig`——`routing/retry.py:25`(活跃 dataclass,仅 Zhipu 用)与 `config/resiliency.py:15`(Pydantic 死代码,`config/routing.py:285` 注册为 `retry` 字段但 `VendorTier.retry_config` 从未赋值,全仓库 `grep "retry_config="` 为空)。`docs/arch/routing.md:22` 与 `config-reference.md:95` 引用了不同的 `RetryConfig`,构成认知陷阱。本次修复**未触碰**死代码(超出范围),后续应单独清理。这也是本次"为何选方案 A(直改 `calculate_delay`)而非方案 B(加可配置 jitter_strategy 字段)"的决定性理由——方案 B 会扩大 schema 与运行时的裂缝。
|
|
124
|
+
- **`calculate_delay` 唯一消费者确证**:经全仓库 grep,仅 `vendors/zhipu.py:247` 调用(`routing/__init__.py` 仅 re-export,`tier.retry_config` 字段未激活)。修改其抖动策略爆炸半径仅限 Zhipu,安全。
|
|
125
|
+
- **测试缺口已补**:修复前 `calculate_delay` 无任何独立单元测试(仅通过 zhipu 集成测试间接覆盖,且那些测试要么禁用 jitter、要么走 retry-after 路径),现已新建 `tests/test_retry.py`。
|
|
126
|
+
|
|
127
|
+
---
|
|
128
|
+
|
|
7
129
|
## streaming usage parse failed: 'NoneType' object has no attribute 'get'
|
|
8
130
|
|
|
9
131
|
**问题描述**
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Knowledge Map(知识索引)
|
|
2
2
|
|
|
3
|
-
>
|
|
3
|
+
> 项目所有文档的统一入口与权威索引。文档目录变更时**必须**即时同步更新本文件。
|
|
4
4
|
>
|
|
5
5
|
> **使用方式**:按"受众 × 目的"二维定位所需文档;不确定起点时,从「入口导航」开始。
|
|
6
6
|
|
|
@@ -59,31 +59,21 @@
|
|
|
59
59
|
|
|
60
60
|
---
|
|
61
61
|
|
|
62
|
-
## 5. Agent
|
|
62
|
+
## 5. Agent 协作与问题档案([docs/.agents/](./))
|
|
63
63
|
|
|
64
|
-
>
|
|
64
|
+
> 面向 AI Agent 协作与跨上下文问题沉淀的支撑文档。
|
|
65
65
|
|
|
66
|
-
| 文档
|
|
67
|
-
|
|
|
68
|
-
| [agents/knowledge-map.md](./knowledge-map.md)
|
|
69
|
-
| [agents/
|
|
70
|
-
| [agents/browser-validation.md](./browser-validation.md) | 浏览器验证协议(连通性自检、凭证管理、E2E) |
|
|
66
|
+
| 文档 | 主旨 |
|
|
67
|
+
| --------------------------------------------------- | --------------------------------------------- |
|
|
68
|
+
| [agents/knowledge-map.md](./knowledge-map.md) | 本文件——项目文档统一索引 |
|
|
69
|
+
| [agents/issue.md](./issue.md) | 已处理 Issue 摘要档案(表因、根因、防范) |
|
|
71
70
|
|
|
72
71
|
---
|
|
73
72
|
|
|
74
|
-
## 6.
|
|
73
|
+
## 6. 工程规范(顶层)
|
|
75
74
|
|
|
76
75
|
| 文档 | 主旨 |
|
|
77
76
|
| --------------------------------- | ----------------------------------------------------- |
|
|
78
|
-
| [docs/issue.md](../issue.md) | 已处理 Issue 摘要档案(表因、根因、防范) |
|
|
79
|
-
|
|
80
|
-
---
|
|
81
|
-
|
|
82
|
-
## 7. 工程规范(顶层)
|
|
83
|
-
|
|
84
|
-
| 文档 | 主旨 |
|
|
85
|
-
| --------------------------------- | ----------------------------------------------------- |
|
|
86
|
-
| [AGENTS.md](../../AGENTS.md) | 工程行为准则与 AI Agent 协作协议(与 CLAUDE.md 同源) |
|
|
87
77
|
| [CHANGELOG.md](../../CHANGELOG.md)| 版本历史与变更日志 |
|
|
88
78
|
|
|
89
79
|
---
|
|
@@ -91,5 +81,5 @@
|
|
|
91
81
|
## 维护约束
|
|
92
82
|
|
|
93
83
|
1. **同步原则**:新增/删除/重命名 `docs/` 下任意 .md 文件时,**必须**同步本索引。
|
|
94
|
-
2. **路径基准**:本文件位于 `docs
|
|
84
|
+
2. **路径基准**:本文件位于 `docs/.agents/`,所有相对路径以此为基准(向上一级 `../` 访问 `docs/`,向上两级 `../../` 访问仓库根)。
|
|
95
85
|
3. **链接验证**:维护者修改本文件后应通过 grep 自检:所有 `[...](path)` 中的 `path` 文件存在。
|
|
@@ -541,6 +541,8 @@ $$
|
|
|
541
541
|
|
|
542
542
|
> **参数默认值**:参见 [配置参考 -- RetryConfig](./config-reference.md#elastic-params)
|
|
543
543
|
|
|
544
|
+
**Vendor 级应用(Zhipu 429/529 内部退避重试)**:[`vendors/zhipu.py`](../../src/coding/proxy/vendors/zhipu.py) 复用 `RetryConfig` / `calculate_delay()`,在 `send_message` / `send_message_stream` 内对 **429 Rate Limit(限流)** 与 **529 Overloaded(并发过载)** 两类服务端瞬态过载信号做就地指数退避重试(共用 `_BACKOFF_RETRY_STATUS = {429, 529}` 作单一事实源,max=5、1s→2s→4s→8s、Full Jitter,优先尊重 server `retry-after`)。耗尽重试后将状态码原样返回,交由上层 `should_trigger_failover`(§3.6 VendorTier)与 [CircuitBreaker](#circuit-breaker) 处理,从而降低 failover 频率。
|
|
545
|
+
|
|
544
546
|
---
|
|
545
547
|
|
|
546
548
|
## 3.13 Rate Limit Deadline Tracking(速率限制截止追踪)
|
|
@@ -277,6 +277,8 @@ curl -X POST http://127.0.0.1:3392/api/reset \
|
|
|
277
277
|
|
|
278
278
|
**重置范围**:circuit_breaker(→ CLOSED)、quota_guard(→ WITHIN_QUOTA)、weekly_quota_guard(→ WITHIN_QUOTA)、rate_limit deadline(→ 清除)。
|
|
279
279
|
|
|
280
|
+
> **仅复位状态,不清用量**:配额守卫的滑动窗口用量计数(`window_usage_tokens` / `usage_percent`)**原样保留**。该基线仅在进程启动时从数据库回填,一旦清零,Dashboard 的配额百分比会永久停在 0% 直到重启。若某 vendor 窗口用量确已超过 `token_budget × threshold_percent`,守卫**保持** `QUOTA_EXCEEDED`(不伪造用量),但仍会清除上游 cap 错误卡死标志并把被 `Retry-After` 拉长的探测间隔还原为默认值;真正被解开的是熔断、Rate Limit 与 cap 错误卡死标志。
|
|
281
|
+
|
|
280
282
|
## 7. GET /api/copilot/diagnostics
|
|
281
283
|
|
|
282
284
|
返回 Copilot 认证与交换链路的脱敏诊断信息。
|
|
@@ -160,6 +160,8 @@ coding-proxy reset [OPTIONS]
|
|
|
160
160
|
|
|
161
161
|
**重置范围**:所有层级的熔断器状态(→ CLOSED)、配额守卫状态(→ WITHIN_QUOTA)、周级配额守卫状态(→ WITHIN_QUOTA)、Rate Limit 截止时间(→ 清除)。
|
|
162
162
|
|
|
163
|
+
> **仅复位状态,不清用量**:配额守卫的滑动窗口用量计数(`window_usage_tokens` / `usage_percent`)**原样保留**。该基线仅在进程启动时从数据库回填,一旦清零,Dashboard 的配额百分比会永久停在 0% 直到重启。若某 vendor 窗口用量确已超过 `token_budget × threshold_percent`,守卫**保持** `QUOTA_EXCEEDED`(不伪造用量),但仍会清除上游 cap 错误卡死标志并把被 `Retry-After` 拉长的探测间隔还原为默认值;真正被解开的是熔断、Rate Limit 与 cap 错误卡死标志。
|
|
164
|
+
|
|
163
165
|
## 5. coding-proxy auth login
|
|
164
166
|
|
|
165
167
|
执行 OAuth 浏览器登录,获取供应商访问凭证。
|
|
@@ -35,6 +35,20 @@ http://127.0.0.1:3392/dashboard
|
|
|
35
35
|
| Token 时间线(按供应商) | 各供应商按天的 Token 消耗堆叠图 |
|
|
36
36
|
| Token 时间线(按供应商+模型) | 细粒度的模型级 Token 消耗堆叠图 |
|
|
37
37
|
|
|
38
|
+
### 供应商状态复位
|
|
39
|
+
|
|
40
|
+
「供应商状态」卡片标题栏右侧提供 **⟲ 状态复位** 按钮,用于把处于熔断 / 限流等异常态的供应商一键复位为可正常访问。等价于 [`POST /api/reset`](./api-reference.md#6-post-apireset) 的**无 body** 形态:
|
|
41
|
+
|
|
42
|
+
| 复位 | 保留 |
|
|
43
|
+
| ---------------------------------------------------------- | ------------------------------------------------------------ |
|
|
44
|
+
| 熔断器状态(→ CLOSED,「熔断 ×N」徽章转「正常」) | 配额窗口用量(「1d配额 45%」徽章数值不变) |
|
|
45
|
+
| 配额守卫状态(用量未超阈值 → WITHIN_QUOTA;确已超阈值 → 保持 EXCEEDED,但仍清除 cap 卡死标志并还原探测间隔) | 供应商优先级顺序(无 body 即不触发重排序) |
|
|
46
|
+
| Rate Limit 冷却截止时间(→ 清除,「限速中」徽章消失) | 数据库用量记录(`coding-proxy usage` 统计不受影响) |
|
|
47
|
+
|
|
48
|
+
执行期间按钮进入禁用态并显示「复位中…」,成功后短暂显示「✓ 已复位」并立即重渲染供应商列表(不必等 10 分钟轮询),失败显示「✗ 失败」,详情见浏览器控制台。
|
|
49
|
+
|
|
50
|
+
> 若某供应商的窗口用量**确实**已超过配额阈值,复位不会放行它 —— 用量数字不会被伪造,守卫保持 `QUOTA_EXCEEDED`;但 cap 错误卡死标志会被清除、探测间隔还原为默认值,探测恢复不会被推迟。
|
|
51
|
+
|
|
38
52
|
### 时间范围选择器
|
|
39
53
|
|
|
40
54
|
页面右上角提供时间范围选择:
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
<div align="center">
|
|
4
4
|
|
|
5
|
-
#
|
|
5
|
+
# <img src="../../assets/logo.svg" alt="coding-proxy" width="32" height="32" align="absmiddle"> coding-proxy
|
|
6
6
|
|
|
7
7
|
**面向 Claude Code 的多供应商高可用透明智能代理**
|
|
8
8
|
|
|
@@ -125,7 +125,7 @@ graph RL
|
|
|
125
125
|
|
|
126
126
|
Client["💻<br/>Client (Claude Code)"]:::client
|
|
127
127
|
|
|
128
|
-
subgraph CodingProxy["
|
|
128
|
+
subgraph CodingProxy["coding-proxy"]
|
|
129
129
|
direction RL
|
|
130
130
|
|
|
131
131
|
Router["RequestRouter<br/><code>routing/router.py</code>"]:::router
|
|
@@ -175,7 +175,6 @@ graph RL
|
|
|
175
175
|
|
|
176
176
|
- 📖 **[用户操作指引 (User Guide)](../user-guide.md)** — 从安装、最小配置要求,到每一项配置文件(`config.yaml`)的具体语义和常见排障指南。
|
|
177
177
|
- 🏗️ **[架构设计与工程方案 (Architecture Framework)](../framework.md)** — 详细解码底层设计模式(Template Method、Circuit Breaker、State Machine 等),适用于希望深入了解源码或贡献新供应商的开发者。
|
|
178
|
-
- 🤝 **[工程准则 (AGENTS.md)](../../AGENTS.md)** — 系统的上下文心法和 AI Agent 协作协议,强调**重构、复用与正交抽象**,是本仓库一切开发的指导方针。
|
|
179
178
|
|
|
180
179
|
---
|
|
181
180
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
[project]
|
|
2
2
|
name = "coding-proxy"
|
|
3
|
-
version = "0.5.
|
|
3
|
+
version = "0.5.2"
|
|
4
4
|
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..."
|
|
5
5
|
readme = "README.md"
|
|
6
6
|
requires-python = ">=3.12"
|
|
@@ -228,51 +228,51 @@ failover:
|
|
|
228
228
|
# === 模型映射 ===
|
|
229
229
|
model_mapping:
|
|
230
230
|
# GitHub Copilot 可用模型(通过 /api/copilot/models 诊断获取)
|
|
231
|
-
- pattern: "claude-sonnet-.*"
|
|
232
|
-
vendors: ["copilot"]
|
|
233
|
-
target: "claude-sonnet-4.6"
|
|
234
|
-
is_regex: true
|
|
235
231
|
- pattern: "claude-opus-.*"
|
|
236
232
|
vendors: ["copilot"]
|
|
237
233
|
target: "claude-opus-4.6"
|
|
238
234
|
is_regex: true
|
|
235
|
+
- pattern: "claude-sonnet-.*"
|
|
236
|
+
vendors: ["copilot"]
|
|
237
|
+
target: "claude-sonnet-4.6"
|
|
238
|
+
is_regex: true
|
|
239
239
|
- pattern: "claude-haiku-.*"
|
|
240
240
|
vendors: ["copilot"]
|
|
241
241
|
target: "claude-haiku-4.5"
|
|
242
242
|
is_regex: true
|
|
243
243
|
# Google Antigravity 模型映射
|
|
244
|
-
- pattern: "claude-sonnet-.*"
|
|
245
|
-
vendors: ["antigravity"]
|
|
246
|
-
target: "Claude Sonnet 4.6"
|
|
247
|
-
is_regex: true
|
|
248
244
|
- pattern: "claude-opus-.*"
|
|
249
245
|
vendors: ["antigravity"]
|
|
250
246
|
target: "Claude Opus 4.6 Thinking"
|
|
251
247
|
is_regex: true
|
|
248
|
+
- pattern: "claude-sonnet-.*"
|
|
249
|
+
vendors: ["antigravity"]
|
|
250
|
+
target: "Claude Sonnet 4.6"
|
|
251
|
+
is_regex: true
|
|
252
252
|
- pattern: "claude-haiku-.*"
|
|
253
253
|
vendors: ["antigravity"]
|
|
254
254
|
target: "Gemini 3 Flash"
|
|
255
255
|
is_regex: true
|
|
256
256
|
# 智谱 GLM 映射(官方原生 Anthropic 兼容端点)
|
|
257
257
|
# glm-5v-turbo 完整承载 Claude Code 满血能力(tool calling / thinking / 多模态)
|
|
258
|
-
- pattern: "claude-
|
|
258
|
+
- pattern: "claude-opus-.*"
|
|
259
259
|
vendors: ["zhipu"]
|
|
260
|
-
target: "glm-
|
|
260
|
+
target: "glm-5.2"
|
|
261
261
|
is_regex: true
|
|
262
|
-
- pattern: "claude-
|
|
262
|
+
- pattern: "claude-sonnet-.*"
|
|
263
263
|
vendors: ["zhipu"]
|
|
264
264
|
target: "glm-5.1"
|
|
265
265
|
is_regex: true
|
|
266
266
|
- pattern: "claude-haiku-.*"
|
|
267
267
|
vendors: ["zhipu"]
|
|
268
|
-
target: "glm-
|
|
268
|
+
target: "glm-5.1"
|
|
269
269
|
is_regex: true
|
|
270
270
|
# MiniMax 模型映射(原生 Anthropic 兼容端点)
|
|
271
|
-
- pattern: "claude-
|
|
271
|
+
- pattern: "claude-opus-.*"
|
|
272
272
|
vendors: ["minimax"]
|
|
273
273
|
target: "minimax-m2.7"
|
|
274
274
|
is_regex: true
|
|
275
|
-
- pattern: "claude-
|
|
275
|
+
- pattern: "claude-sonnet-.*"
|
|
276
276
|
vendors: ["minimax"]
|
|
277
277
|
target: "minimax-m2.7"
|
|
278
278
|
is_regex: true
|
|
@@ -281,11 +281,11 @@ model_mapping:
|
|
|
281
281
|
target: "minimax-m2.7"
|
|
282
282
|
is_regex: true
|
|
283
283
|
# 阿里 Qwen 模型映射(原生 Anthropic 兼容端点)
|
|
284
|
-
- pattern: "claude-
|
|
284
|
+
- pattern: "claude-opus-.*"
|
|
285
285
|
vendors: ["alibaba"]
|
|
286
286
|
target: "qwen3.6-plus"
|
|
287
287
|
is_regex: true
|
|
288
|
-
- pattern: "claude-
|
|
288
|
+
- pattern: "claude-sonnet-.*"
|
|
289
289
|
vendors: ["alibaba"]
|
|
290
290
|
target: "qwen3.6-plus"
|
|
291
291
|
is_regex: true
|
|
@@ -294,11 +294,11 @@ model_mapping:
|
|
|
294
294
|
target: "qwen3.6-plus"
|
|
295
295
|
is_regex: true
|
|
296
296
|
# 小米 MiMo 模型映射(原生 Anthropic 兼容端点)
|
|
297
|
-
- pattern: "claude-
|
|
297
|
+
- pattern: "claude-opus-.*"
|
|
298
298
|
vendors: ["xiaomi"]
|
|
299
299
|
target: "mimo-v2-pro"
|
|
300
300
|
is_regex: true
|
|
301
|
-
- pattern: "claude-
|
|
301
|
+
- pattern: "claude-sonnet-.*"
|
|
302
302
|
vendors: ["xiaomi"]
|
|
303
303
|
target: "mimo-v2-pro"
|
|
304
304
|
is_regex: true
|
|
@@ -307,11 +307,11 @@ model_mapping:
|
|
|
307
307
|
target: "mimo-v2-pro"
|
|
308
308
|
is_regex: true
|
|
309
309
|
# Kimi 模型映射(原生 Anthropic 兼容端点)
|
|
310
|
-
- pattern: "claude-
|
|
310
|
+
- pattern: "claude-opus-.*"
|
|
311
311
|
vendors: ["kimi"]
|
|
312
312
|
target: "kimi-k2.5"
|
|
313
313
|
is_regex: true
|
|
314
|
-
- pattern: "claude-
|
|
314
|
+
- pattern: "claude-sonnet-.*"
|
|
315
315
|
vendors: ["kimi"]
|
|
316
316
|
target: "kimi-k2.5"
|
|
317
317
|
is_regex: true
|
|
@@ -339,6 +339,12 @@ model_mapping:
|
|
|
339
339
|
# 未配置定价的模型在统计中 Cost 列显示 "-"
|
|
340
340
|
pricing:
|
|
341
341
|
# ── Anthropic Claude ──
|
|
342
|
+
- vendor: anthropic
|
|
343
|
+
model: claude-fable-5
|
|
344
|
+
input_cost_per_mtok: $10.0
|
|
345
|
+
output_cost_per_mtok: $50.0
|
|
346
|
+
cache_write_cost_per_mtok: $12.50
|
|
347
|
+
cache_read_cost_per_mtok: $1.00
|
|
342
348
|
- vendor: anthropic
|
|
343
349
|
model: claude-opus-4-8
|
|
344
350
|
input_cost_per_mtok: $5.0
|
|
@@ -527,20 +533,10 @@ pricing:
|
|
|
527
533
|
cache_read_cost_per_mtok: $0.05
|
|
528
534
|
# ── 智谱 GLM ──
|
|
529
535
|
- vendor: zhipu
|
|
530
|
-
model: glm-
|
|
531
|
-
input_cost_per_mtok: ¥
|
|
532
|
-
output_cost_per_mtok: ¥
|
|
533
|
-
cache_read_cost_per_mtok: ¥
|
|
534
|
-
- vendor: zhipu
|
|
535
|
-
model: glm-4.7 # 待区分长短上下文定价
|
|
536
|
-
input_cost_per_mtok: ¥2.00
|
|
537
|
-
output_cost_per_mtok: ¥8.00
|
|
538
|
-
cache_read_cost_per_mtok: ¥0.40
|
|
539
|
-
- vendor: zhipu
|
|
540
|
-
model: glm-5v-turbo # 待区分长短上下文定价
|
|
541
|
-
input_cost_per_mtok: ¥5.00
|
|
542
|
-
output_cost_per_mtok: ¥22.00
|
|
543
|
-
cache_read_cost_per_mtok: ¥1.20
|
|
536
|
+
model: glm-5.2 # 待区分长短上下文定价
|
|
537
|
+
input_cost_per_mtok: ¥8.00
|
|
538
|
+
output_cost_per_mtok: ¥28.00
|
|
539
|
+
cache_read_cost_per_mtok: ¥2.00
|
|
544
540
|
- vendor: zhipu
|
|
545
541
|
model: glm-5.1 # 待区分长短上下文定价
|
|
546
542
|
input_cost_per_mtok: ¥6.00
|
|
@@ -556,6 +552,21 @@ pricing:
|
|
|
556
552
|
input_cost_per_mtok: ¥4.00
|
|
557
553
|
output_cost_per_mtok: ¥18.00
|
|
558
554
|
cache_read_cost_per_mtok: ¥1.00
|
|
555
|
+
- vendor: zhipu
|
|
556
|
+
model: glm-5v-turbo # 待区分长短上下文定价
|
|
557
|
+
input_cost_per_mtok: ¥5.00
|
|
558
|
+
output_cost_per_mtok: ¥22.00
|
|
559
|
+
cache_read_cost_per_mtok: ¥1.20
|
|
560
|
+
- vendor: zhipu
|
|
561
|
+
model: glm-4.7 # 待区分长短上下文定价
|
|
562
|
+
input_cost_per_mtok: ¥2.00
|
|
563
|
+
output_cost_per_mtok: ¥8.00
|
|
564
|
+
cache_read_cost_per_mtok: ¥0.40
|
|
565
|
+
- vendor: zhipu
|
|
566
|
+
model: glm-4.5-air # 待区分长短上下文定价
|
|
567
|
+
input_cost_per_mtok: ¥0.80
|
|
568
|
+
output_cost_per_mtok: ¥2.00
|
|
569
|
+
cache_read_cost_per_mtok: ¥0.16
|
|
559
570
|
# ── MiniMax ──
|
|
560
571
|
- vendor: minimax
|
|
561
572
|
model: minimax-m2.7
|
|
@@ -693,3 +704,13 @@ session_policies:
|
|
|
693
704
|
title_vendor_bindings:
|
|
694
705
|
- prefix: "# 目标"
|
|
695
706
|
vendor: "zhipu"
|
|
707
|
+
# Session 标题豁免前缀:标题提取每一层(user 文本 / 工具结果 / 图片 / 元数据兜底)
|
|
708
|
+
# 产出的候选以任一前缀开头则跳过,继续向下一层回退。既用于过滤注入式 Prompt
|
|
709
|
+
# (如示例语言指令),也可豁免无信息量的合成兜底标题。大小写敏感 startswith。
|
|
710
|
+
# 例:添加 "[Session]" 可让 [Session] <model> 这类兜底标题不再写入,
|
|
711
|
+
# session 标题保持空,待后续真实输入经延迟补写回填。
|
|
712
|
+
# ⚠️ 自定义 yaml 中该字段为整体替换(loader 的 list 合并约定,非追加合并);
|
|
713
|
+
# 写空列表即关闭豁免。加载时会自动 strip + 去空 + 去重。
|
|
714
|
+
title_exempt_prefixes:
|
|
715
|
+
- "Write the title in the"
|
|
716
|
+
- "[Session]"
|