What's new
-
Import from other apps. The add sheet's Import… lists the providers already set up in Alma and CC Switch (its database, or the older config.json). It only reads them. Pick what to bring over, per app or with Select all:
- A vendor magpie already has can join it as another key.
- An id already in use can be kept beside the existing one, or replace it.
- Sign-ins, Azure, Gemini-protocol relays and entries that point back at magpie are shown but can't be picked.
-
Several Grok subscriptions. Grok now works like Claude and Codex: add more accounts and tick the ones to use. Each extra account signs in with
grok loginin a home of magpie's own, so the Grok CLI's own sign-in is never touched. The gateway uses the first account; when it runs out of quota, the next one takes over. -
Routing. A provider with several keys or accounts turned on gets a Routing choice:
- In order: requests go to the first; the next takes over on quota, rate limit or failure.
- In turn: each request goes to the next one (round robin).
- Least used first: a subscription is ranked by the share of its allowance used, a key by the tokens magpie sent it lately.
With any of the three, a key or account that just failed waits a minute before it is tried again.
新功能
-
从其他应用导入：在添加面板点「导入…」，可以读取 Alma、CC Switch 里已经配置好的供应商。magpie 只读取，不做任何修改。可以逐个勾选，也可以按应用全选：
- magpie 里已有的供应商，可以把导入的密钥作为另一个密钥加进去。
- id 已被占用的，可以两者并存，也可以替换原有的。
- 登录类账号、Azure、Gemini 协议的中转，以及指向 magpie 自身的条目，只显示，不能导入。
-
Grok 支持多个订阅账号：和 Claude、Codex 一样，可以添加多个账号，勾选的会同时启用。新增的账号在 magpie 自己的目录里用
grok login登录，不会改动 Grok CLI 本身的登录。网关优先用第一个账号，它额度用完时自动换下一个。 -
路由：某个供应商启用了多个密钥或账号时，可以选择请求怎么分配：
- 按顺序：先走第一个，额度用完、被限流或出错时由下一个接手。
- 轮流：每个请求依次发给下一个。
- 用量少的优先：订阅按已用额度比例排序，密钥按最近经 magpie 的 token 数排序。
无论选哪种，刚出错的密钥或账号都会先歇一分钟再用。