Zhizhen He 9fcfbbdfee provider: back up unreadable saved accounts with valid JSON (#965) ...

A cold-start account add could replace logins.json without keeping its
credentials when the JSON was syntactically valid but could not decode as
saved accounts. Match readLogins' typed decoding in the backup check, so
invalid field types and a wrong root type are kept aside before a write.
Readable account files still need no backup.

TestUnreadLoginsFieldTypesKeptBeforeWrite fails without the change because
no original-file backup is made for a string boolean, invalid time or
object root. The fixed cases and the readable-file control pass, including
five race-enabled runs. Update the providers/accounts failure contract.

go vet, the full nogui Go suite, the native macOS build and Linux/Windows
cross-builds pass under a temporary HOME with pinned Go caches.

2026-10-06 11:28:26 +08:00

..

subsystems

provider: back up unreadable saved accounts with valid JSON (#965)

2026-10-06 11:28:26 +08:00

code-standards.md

docs: LESSONS.md keeps what the nightly review of merged work finds, and agents read it before changing code

2026-10-06 03:10:24 +08:00

contributors.md

docs: contributors.md lists lunar-me under authors reviewed with extra care (the maintainer chose not to block), with the evidence and what the extra care is

2026-10-06 04:52:27 +08:00

integrating.md

docs, site: Integrating your app or agent with magpie, at docs/integrating.md and usemagpie.ai/docs/integrate (#918, Magixyne)

2026-10-05 22:46:35 +08:00

reference.md

gateway: a gateway key can be held to some accounts (#905, LCorleone) — a key could burn any account a provider had: two coding plans of one vendor, and a key given to someone had them both. A key now keeps an optional list of accounts and keys (caller-keys.json "accounts", none = every account, so older files read as before): "<provider>/<account>", an account by its stable id — the login's, set once it is written and kept through renames (logins.json's savedLogin id, written by every write and stood in for by one made of the name until then, so an entry made before stands), a key by its fingerprint — every one a provider has when the list is set, and one gone later (a key rotated, an account signed out) kept as it is, matching nothing, holding the key closer, never wider. The command line and the menu name an account by who is signed in and keep its id. Routing holds a plan to the key's accounts beside its models: a candidate whose account the key may not use is left out — through a routing group the key names no less, for naming a group is not naming its accounts — the plan's order keeping step and its left-out list marking what the key held out (Weighed's held); magpie's own calls for the key — a web search, a picture described, a Codex title — are of the models the user picked, so the models don't hold them, but their spend lands on an account all the same, and the accounts hold them too. When every account or key a model has is one the key may not use, the request is refused with a 403 in the API's own error shape naming the model and the accounts the key may use, logged as a rejected call: after a usage cap's 429 and before an account barred for the model's, itself before the no-member 404. /v1/models and the Anthropic and Gemini lists show the key only the models an account or key it may use serves (a provider's account set not to serve one, #474, is none of the key's); a provider with no account and no key (a local ollama) is one the key names no account of — its models stay listed and its asks pass — while an entry kept after its provider lost its last account or key serves none, holding the key closer. The embeddings, images and videos endpoints hold their candidate to the key's accounts the same way, and counting tokens counts on those alone (the local estimate where it may use none). System One asks its decision model of an account or key the key may use — and sends on that key, of those in use, not the provider's first, which a key held to a later one was spent on; the videos and images keyed paths send on one the key may use too, held to a later key no longer refused for the first alone. Set it in the app's menu the models are picked in — the accounts after the models, an account by who is signed in with their plan in the note, a key by its fingerprint, what the CLI kept that no provider has now kept as "Not signed in now" — or magpie gateway-key accounts <id> codex/me@example.com openai/<key id> (all takes it off); gateway-key list has an ACCOUNTS column. en/zh/ja/de, the German "{n} accounts" main already had left to it rather than written twice. The images API's fan-out over a subscription's accounts is held to the key's accounts as one: one of the key's whose plan refuses to draw no longer hands the pen to an account it may not use, and the second in the order, when it is the key's, draws what the first may not (drawOnAccounts filters the candidates, the account pinned to with the account header told plainly when the key may not use it). The Routing view's left-out list says an account the key held out for what it is, not that its plan lacks the model, in Chinese, Japanese and German too; the key's badge names its accounts by who is signed in, not by the stable ids it keeps. (#932)

2026-10-06 10:51:50 +08:00