github yetone/magpie-releases v0.1.1108
magpie v0.1.1108

latest releases: v0.1.4682, v0.1.4681, v0.1.4680...
one month ago

Bug Fixes

  • Copilot accounts are now identified by both login and host, so the same GitHub login on github.com and enterprise *.ghe.com is kept as separate accounts.
  • Renaming a Copilot account with its host now preserves its proxy, models, cap, and concurrency settings.
  • Compressed request bodies (gzip or zstd) are now read on all gateway routes, preventing "expected a JSON object" errors for Codex with a custom provider on /v1/responses.
  • Fixed an issue where a full response after keepalives could be delivered as an "OK" error instead of a stream.
  • Fixed a timing issue that could incorrectly clear a 401 lapse mark for a plugin account.

Improvements

  • Updated Go to 1.26.8, including a fix for the race detector on macOS.

Install

Download from usemagpie.ai, or curl -fsSL https://usemagpie.ai/install.sh | sh. An installed magpie updates itself.

  • macOS (Apple Silicon): magpie-darwin-arm64.dmg
  • macOS (Intel): magpie-darwin-amd64.dmg
  • Windows: magpie-windows-amd64.exe (ARM: magpie-windows-arm64.exe)
  • Linux: magpie-linux-amd64 / magpie-linux-arm64 (needs GTK 3 and WebKitGTK 4.1)
  • Terminal only: magpie-cli-<os>-<arch>

错误修复

  • Copilot 账户现在同时通过登录名和主机进行标识,因此同一 GitHub 登录名在 github.com 和企业版 *.ghe.com 上会保留为单独的账户。
  • 在重命名 Copilot 账户(连同其主机)时,现在会保留其代理、模型、上限和并发设置。
  • 现在所有网关路由都会读取压缩的请求体(gzip 或 zstd),从而避免 Codex 在 /v1/responses 上使用自定义提供程序时出现“expected a JSON object”错误。
  • 修复了一个问题:在 keepalive 之后返回的完整响应可能被作为“OK”错误传递,而不是作为流传递。
  • 修复了一个时序问题,该问题可能导致插件账户的 401 失效标记被错误清除。

改进

  • 已将 Go 更新到 1.26.8,其中包括针对 macOS 上竞态检测器的修复。

安装

从 usemagpie.ai 下载,或运行 curl -fsSL https://usemagpie.ai/install.sh | sh。已安装的 magpie 会自动更新。

Don't miss a new magpie-releases release

NewReleases is sending notifications on new releases.