gproxy v2.0.20

v2.0.20

Improves first-run provisioning and Console identity management, restores complete streaming and live operations on supported edge runtimes, expands self-update coverage, and corrects cross-protocol prompt-cache defaults.

English

Added

• First-run provider and API-key setup. The Windows, macOS, Linux, and Android launchers can now create enabled providers for selected built-in channels, seed their default routing rules, and generate an administrator API key during initial setup. Generated keys are displayed or copied once by the installer, while repeated setup remains idempotent.
• User and key management. Administrators can edit users directly from the user list, and authenticated administrators and portal users can view their complete stored API keys instead of only a digest prefix. Stored keys remain encrypted when a master key is configured.
• Streaming edge requests. Cloudflare Workers, Netlify Edge, and Deno Deploy now relay upstream SSE as real streaming responses, including per-frame protocol conversion, interruption accounting, and response capture.
• Live edge operations. Edge deployments can fetch upstream model catalogues, initialize provider routing in a single database operation, read live credential usage, and consume supported rate-limit reset credits.

Fixed

• Prompt-cache conversion defaults. OpenAI Chat Completions and Responses requests no longer gain a Claude request-level cache_control unless they explicitly select implicit mode. In the reverse direction, Claude requests converted to OpenAI now default to prompt_cache_options.mode = "implicit"; explicit block breakpoints continue to survive conversion within each protocol's limit.
• Native self-update targets. Self-update now distinguishes GNU and musl Linux artifacts and supports both portable Android binaries and verified APK hand-off to Android's system package installer.
• Staging update notifications. Rolling builds compare the commit identity embedded in the binary with the signed staging manifest, and dismissing an update banner suppresses that specific build without hiding later updates.
• Console data consistency. Mobile usage cards now expose the same input, output, cache-write, and cache-read details as desktop tables. Provider cards show channel families, user cards show password state, and related mobile and desktop views use consistent data.
• Cross-platform build hygiene. Native, Android, edge-Wasm, packaging, and deployment builds no longer emit the addressed target-specific warnings; edge Wasm is emitted explicitly as a cdylib by the release workflow.

Changed

• Supported edge targets. Release artifacts and documentation now focus on Cloudflare Workers, Netlify Edge, and Deno Deploy. The incomplete Supabase, EdgeOne Pages, and Appwrite Deno bundles have been removed.

简体中文

新增

• 首次安装 Provider 与 API Key 初始化。 Windows、macOS、Linux 和 Android 启动器现在可在首次设置时为选中的内置 Channel 创建已启用的 Provider、写入默认路由规则，并生成管理员 API Key。安装器只展示或复制一次生成的 Key，重复执行初始化不会创建重复数据。
• 用户与密钥管理。 管理员现在可直接在用户列表中编辑用户；经过身份验证的管理员和 Portal 用户可以查看完整的已存储 API Key，而不再只看到摘要前缀。配置 Master Key 时，密钥仍以加密形式保存。
• Edge 流式请求。 Cloudflare Workers、Netlify Edge 和 Deno Deploy 现在会把上游 SSE 作为真正的流式响应转发，并支持逐帧协议转换、中断计费结算与响应记录。
• Edge 在线操作。 Edge 部署现在可以获取上游模型目录、通过单次数据库操作初始化 Provider 路由、查询 Credential 实时用量，以及消费受支持的限流重置额度。

修复

• 提示缓存转换默认值。 OpenAI Chat Completions 和 Responses 请求不再默认获得 Claude 请求级 cache_control，只有明确选择 implicit 模式时才会添加。反向转换时，Claude 请求转为 OpenAI 现在默认使用 prompt_cache_options.mode = "implicit"；显式块级断点仍会在各协议限制内保留。
• 原生自更新目标。 自更新现在能区分 Linux GNU 与 musl 产物，并同时支持 Android 便携二进制和经过校验后交给 Android 系统安装器处理的 APK 更新。
• Staging 更新提示。 滚动构建现在比较二进制内嵌的 Commit 标识与签名 Staging Manifest；关闭更新提示后只会忽略该次构建，后续更新仍会再次提示。
• Console 数据一致性。 移动端用量卡片现在与桌面表格一样展示输入、输出、缓存写入和缓存读取数据；Provider 卡片增加 Channel Family，用户卡片显示密码状态，相关移动端与桌面端视图的数据保持一致。
• 跨平台构建清理。 Native、Android、Edge Wasm、打包和部署构建不再产生已处理的目标平台警告；Release Workflow 会显式以 cdylib 形式生成 Edge Wasm。

调整

• 支持的 Edge 目标。 Release 产物和文档现在集中支持 Cloudflare Workers、Netlify Edge 与 Deno Deploy；尚不完整的 Supabase、EdgeOne Pages 和 Appwrite Deno Bundle 已移除。