ViberMate v0.1.6
中文
ViberMate 0.1.6:修复 ChatGPT 上游账号替换与模型发现。
- 修复合法的空
turn_id被误判为invalid_exchange_request、请求尚未到达上游就失败的问题。 - 选择 ChatGPT 上游账号时使用原生 Codex 请求与模型发现地址,兼容其模型列表中的
slug标识;普通 OpenAI Responses 上游仍使用原有 API 地址。 - 替换账号时清除原客户端的账号头,并从所选 ChatGPT access token 中提取对应的账号标识;显式设置的账号头仍优先。
- App 和网页工作台同步显示实际模型发现地址,并补充 ChatGPT 凭据类型及过期后的处理说明。
- 增加回归测试,覆盖账号隔离、流式响应,以及“不记录内容”时脚本仍执行、内容不落盘的行为。
本次不修改已有账号、流量策略或历史记录,不包含 ACP 支持。
macOS 14+(Apple silicon / Intel)更新:
brew update
brew upgrade --cask vibe-agi/tap/vibermate首次安装使用 brew install --cask vibe-agi/tap/vibermate。Linux x86_64 / arm64 压缩包包含 Server、CLI 和 Web 工作台;参见安装与团队接入。下载后请校验对应的 SHA256SUMS 文件。
验证边界:已使用受控请求、响应和凭据测试兼容性,未使用真实 ChatGPT 账号做在线验收。保存的 ChatGPT access token 不会自动刷新,过期后需在上游账号中替换。未收录的客户端版本仍可能显示 Version unknown。
English
ViberMate 0.1.6 fixes ChatGPT upstream account replacement and model discovery.
- Accept valid empty optional
turn_idmetadata instead of rejecting the request locally withinvalid_exchange_request. - Use native Codex request and model-discovery paths for ChatGPT services, including model
slugidentifiers. Standard OpenAI Responses endpoints keep their existing API paths. - Remove the original client's account header when replacing credentials and derive the account identifier from the selected ChatGPT access token. Explicit account-header settings take precedence.
- Show the actual discovery URL and clarify credential type and expiry handling in the App and Web workbench.
- Add regression coverage for account isolation, streaming responses, and transforms continuing to run without retaining content when recording is off.
Existing accounts, traffic policies, and history are unchanged. ACP support is not included.
For macOS 14+ (Apple silicon / Intel), run brew update, then brew upgrade --cask vibe-agi/tap/vibermate. For a first installation, use brew install --cask vibe-agi/tap/vibermate.
Linux x86_64 / arm64 archives include the Server, CLI, and Web workbench. See the setup guide and verify downloads with the corresponding SHA256SUMS file.
Verification scope: compatibility was tested with controlled requests, responses, and credentials, not a live ChatGPT account. Stored ChatGPT access tokens do not refresh automatically; replace expired credentials in the upstream account. Uncataloged client builds may still display Version unknown.