elonnzhang
a2cd79da96
fix(gui): align provider status dots on providers page ( #146 )
...
Give the .key status pill a fixed min-width and hidden overflow so its
left edge (and the green ::before dot) lands at the same x on every
provider row, instead of shifting with label length.
2026-09-28 17:49:50 +08:00
yetone
b552027932
panel: a balance shows its provider's logo before its name (这里也要有Provider的Icon), the generic one for a provider without; the footer is even to the eye (底栏的上下间距是一致的吗) — its rule was a pixel of the space above and the panel's rim takes about one off the space below, 7 against 5 on the Mac, so it's 1+5 over and 7 under now; and a picker comes and goes like an iOS menu (Modal Selector的弹出跟关闭都要有丝滑的动画) — it grows out of the button's middle from .94 on a quick-to-answer curve with a long soft settle and no bounce, .42s, shown at once as it fades in over .18s, and closing leaves its likeness (scrolled and typed as it was, no ids, inert) to fade and sink back toward the button over .22s while the real one is put back at once; under reduced motion it only fades in
2026-09-28 17:49:07 +08:00
yetone
1ae838fc98
gateway: no Add to Cindy — the Gateway view's connect card no longer has a button for one app, which read as an advert and showed whether or not Cindy was installed; the link, its strings and the cindy:// allowance on /api/open go with it
2026-09-28 17:45:39 +08:00
yetone
ea6a5f53e7
agent: the Windows-only WSL test builds again — wslList returns the names and whether wsl.exe answered, and the test took it as the names alone
2026-09-28 17:43:10 +08:00
yetone
6294dd0ac5
provider: WorkBuddy usage shows up — send a WorkBuddy User-Agent and read string capacities (workbuddy 订阅的usage能显示出来吗)
...
copilot.tencent.com's gateway answers 10085 '请求不合法' to a request whose
User-Agent it doesn't know, so the resource-summary meter came back rejected
and the credits window stayed empty; every call to it — chat sign included,
not only billing — now goes out as WorkBuddy/<version>. And the meter sends
its capacities as JSON strings ('3300', '438.88000002'), which wouldn't
unmarshal into float64, so a wbNum type parses either a string or a number.
Verified against the live API (GET /console/accounts + POST
/billing/meter/get-user-resource-summary both 200 with the account's real
credits) from app.asar 5.5.6.
2026-09-28 17:40:12 +08:00
yetone
23f1db6dba
panel: the model's logo on a row's hover comes in on the row's spring (这里的icon出现的时候的动画有点太突兀了 / 像iOS的动画一样丝滑) — its box opens from nothing to a real width measured as the pointer comes onto the row, not a grid column going 0fr→1fr, which WebKit doesn't lay out frame by frame, so the logo jumped to its size over the words; the logo sits against the words and fades and grows in from their side a beat behind the box, .46s open, and goes first on the way out, .36s; the box's padding is counted in its width now, so the leftmost disc's ring is whole; none of it moves under reduced motion
2026-09-28 17:39:05 +08:00
yetone
e6e09aa348
panel: nothing is shaved at an edge (竟然有裁边 / 上面这个border也被裁掉了) — the model's logo on a row's hover comes in as its column opens from nothing to its own width, so a stack of three is as whole as one, with its clip padded past the discs' rings; and the tab's view, which scrolls and so clips at its own top, has the 2px the card's ring outside its box needs, taken from the gap under the tabs. usage: an account's last allowance read is kept (quotas.json beside magpie's settings) and shown in place of one that can't be read for a reason that says nothing about the account — Anthropic rate limiting its usage endpoint, a 5xx, a timeout — across restarts too, with its windows that have reset since starting again from nothing and a tooltip saying when it was read; a reading that comes back is used at once, and a sign-in gone bad is still said (因为rate limit获取不到用量的情况下，能否先暂时用上一次获取到的用量顶替着)
2026-09-28 17:34:08 +08:00
yetone
f8be98bc8a
gui: a dialog's head and buttons stay put and only the fields between them scroll — openModal lays an editor out as head, body, bar (the fields moved into .ebody, the only part that scrolls, and a re-render keeps its place), and the head and the button bar are the same 48px with what's in them centred, so they sit the same above and below (上边栏跟下边栏要固定着，只有内容区可以上下滚动 / 上下间距要保持一致)
2026-09-28 17:30:39 +08:00
yetone
5741e3fc95
provider: WorkBuddy credits are at /billing/meter/... — not /v2
...
The get-user-resource-summary meter, unlike the older /v2/billing meters,
has no /v2 gateway prefix; WorkBuddy's own client asks it at
/billing/meter/get-user-resource-summary on both desktop and web. magpie
was asking under /v2 and would have gotten nothing, so no credits showed.
2026-09-28 17:30:39 +08:00
yetone
9661b8f302
gui(routing): on a wide window the request list and Accounts and keys sit side by side at the same width — they were 1.25fr to 1fr, the left wider than the right (reported by @duanckham on X)
2026-09-28 17:28:14 +08:00
yetone
f6301b0837
panel: a shut agent row is its 36px again — the opening part now always there sat in a second grid row under the row's 9px row gap, so every row had a strip beneath it and its line sat high (每个Item的上下间距竟然不一致); the tab card glides — the panel's height changing on a tab was taken for a resize and the card put still, cutting its glide off, so now only the bar's width changing puts it; and a row opens and closes on a critically damped spring fitted to a cubic-bezier (.25,.3,.1,1), .48s open and .4s shut, with the panel's edge on the same curve and time: it sets off gently, settles without a tail, what's inside comes down into place as it clears and is gone first when it shuts (展开有点突兀，折叠有点油腻 / 像iOS动画一样)
2026-09-28 17:24:14 +08:00
yetone
3f3cdff119
stats: magpie counts its users — once a day a running app or magpie serve sends PostHog (the Magpie project) one "magpie active" event under a random id made up on this computer (~/.config/magpie/install-id), with the version, the system and the architecture and nothing else, no person profile kept; off in Settings → Privacy → Count me as a user, or with DO_NOT_TRACK=1 or MAGPIE_NO_STATS=1, and never from a build from source; the README says what goes
2026-09-28 17:23:41 +08:00
yetone
7dff31fc46
agent: a WSL distro that isn't running is never started to be looked at — any access to its files through \\wsl.localhost starts it — so only running distros (wsl.exe -l --running -q) are probed, once each, and those Codex is in are kept in wsl.json beside magpie's settings (not the stash, which profiles and backups carry) with their fields as last read; a stopped one stays listed as magpie last saw it, with a notice saying so, no path, and nothing checked, synced or migrated, so the minute's list, Detected and Current never open it; picking a value is the user asking, so it starts the distro with wsl.exe -d <distro> -e true first (opening a stopped distro's files is aborted rather than waited for) and then writes, keeping what it wrote at once; a distro no longer installed is forgotten, and one without Codex isn't kept. Tested on the Windows box with a throwaway Alpine distro: listed while running, then after wsl --terminate listed with its last model and effort by magpie ls and magpie codex@wsl:<distro> with wsl -l -v still showing it Stopped, then a model set on it started it, wrote its config and updated wsl.json
2026-09-28 17:22:30 +08:00
yetone
52b3ad3a9e
agent: on Windows, Codex installed in a WSL distro is an agent of its own, codex@wsl:<distro> ("Codex · WSL Ubuntu") — the distros are listed with wsl.exe -l -q (UTF-16LE, or UTF-8 under WSL_UTF8), each asked once through proc for its $HOME, its ~/.codex, a codex on its PATH and its default route, and shown only where Codex is; its files are Codex's own reading and writing (codexIn, at a place rather than a home) through \\wsl.localhost\<distro> (\\wsl$ before that), with the catalog path written in as the distro spells it and what was there stashed under the distro's agent; the gateway written in is 127.0.0.1 when .wslconfig has networkingMode=mirrored and otherwise the Windows host by the distro's default route, with a notice that NAT needs the gateway beyond loopback and through Windows' firewall and that mirrored is the way; its requests stay counted as Codex's, and a profile key is split at its last dot for distro names like Ubuntu-24.04. Nothing runs off Windows. Kimi CLI isn't an agent magpie has yet, so there is no Kimi in WSL. Tested on a Windows box under NAT with a throwaway Alpine distro: detected (the real distros without Codex left out), a magpie model set and reset from the CLI and a test binary, the catalog read inside WSL at /root/.codex; mirrored networking tested only in unit tests
2026-09-28 17:22:30 +08:00
yetone
0984edaa03
cursor: the Run goes to the agent API Cursor's server config names for the account — ServerConfigService/GetServerConfig on api2.cursor.sh, whose agentUrlConfig cursor-agent reads to pick agentUrl in privacy mode (which the Run always asks for) and agentnUrl otherwise — asked once a token, kept by the token's hash so another account asks again, asked afresh and the Run tried once more after a region error, and the global agentn.global.api5.cursor.sh while the config can't be had (retried after a minute), as a team served in one region only was turned away by the global API with 'This region is not yet available for your team'; Cursor's errors have words of their own, no longer Devin's: an unauthenticated or expired sign-in says to sign in to Cursor again in magpie, a region or team restriction says so plainly with a 403 and doesn't ask for a sign-in; and Cursor's expanded ids (grok-4.7-low … grok-4.7-xhigh-fast, Claude with and without thinking, gpt-5.5-extra-high) are offered as one model a family, with the efforts it really has, named as Cursor names its default without the effort and holding what the least of its variants holds, fast and thinking families of their own (GPT-5.5 is 1M, GPT-5.5 Fast isn't said to be) and a family of one kept as Cursor's id — the list saved stays Cursor's own, and the gateway turns model and effort (and Codex's Fast) back into the variant at that effort, Cursor's default for one between those it has, else the nearest, while any of Cursor's own ids still goes as it is
2026-09-28 17:14:07 +08:00
4df6cd14ac
provider: a Claude account's Fable week is read and routed on ( #139 ) — /api/oauth/usage gives a week's allowance per model only in its limits[] array, which readClaudeWindows didn't parse, so magpie accounts, magpie quota and the app never showed Fable's, often the first to run out on Max, and routing went on sending Fable requests to an account whose Fable week was used up. Each weekly_scoped item with a scope.model.display_name is now a window "7 days · <name>", counted in percent, renewing at resets_at, a week long and counting only its model (the name lowercased, spaces and dots as dashes, so "Fable" counts every claude-fable-*), which Allowance.For and Full already weigh against that model alone, as they do the Opus and Sonnet weeks; one without a scope (seven_day again) or one for a model seven_day_opus/seven_day_sonnet already told is left out. Claude Code's rate_limit_event names the same window seven_day_overage_included, its "Fable limit" (in 2.1.283's bundle, for its allowlist Fable, Fable 5, Fable 5.1); claudeKinds takes it too, so the Fable week stays known while the usage endpoint turns magpie away. Reported by Cyb3rN8
...
Co-authored-by: Cyb3rN8 <99947149+Cyb3rN8@users.noreply.github.com >
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com >
2026-09-28 17:12:12 +08:00
44acea90db
gateway: a subagent Codex's MultiAgentV2 spawns from a magpie-served lead gets its task ( #141 ) — a namespaced call (spawn_agent, send_message, followup_task) now carries "encrypted_function_args": [], since Codex reads a call without that list as sealed and handed spawn_agent's plain message on as encrypted_content, which OpenAI could not decrypt for a gpt-6 subagent; and the agent_message item V2 hands a subagent its task in, and agents their messages to each other, is read as the receiving agent's user turn instead of being dropped, so a magpie-served subagent no longer started with nothing to do (an item with no content adds no turn). Top-level calls and the other encoders are as before. Checked end to end with Codex 0.155.1 and features.multi_agent_v2=true in a sandbox HOME against a scripted upstream: before, the subagent's request held only the environment context; after, it holds "Message Type: NEW_TASK … Payload: …" and answers it. Patch and tests by relus-cy, who found and reported both gaps
...
Co-authored-by: relus-cy <14657224+relus-cy@users.noreply.github.com >
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com >
2026-09-28 17:12:11 +08:00
yetone
25aae87511
panel: things move as they change — the tab picked has a card that glides to it; an agent's effort is a drawn slider whose knob and fill glide from stop to stop; a row opens and closes by easing its height, the panel's edge moving with it over the same time and curve; hovering an agent brings in its model's logo beside the name; Add provider scrolls the window to the sheet it opens; and a reply that isn't JSON shows its own words rather than WebKit's "The string did not match the expected pattern" (切换Tab不是丝滑的左右滑动 / 这又是啥报错 / 展开折叠也要有丝滑的动画 / hover显示模型图标 / 自动滚动到展开内容顶部)
2026-09-28 17:08:29 +08:00
yetone
3dabb56ac9
sessions: history by day in the CLI and the TUI — magpie sessions lists the latest Claude Code and Codex sessions (when, agent, folder, first prompt, tokens, cost; --limit, --json with the resume commands), and with --days N|today|all (stats alone is 7) prints the range's totals (tokens, list-price cost, cache read and hit rate, active time and on how many days), a line a day with its tokens, cost, cache read, active time and a bar, then the top models and folders; --model and --folder narrow either, matched exactly, by base name or by a unique part, an unknown one naming those there are. The TUI gets a sessions page after usage (5; the library is 6 now) with the ranges today, 7, 30, 90 days and all (←→, t w m A), M and f to pick a model or a folder from those the range has, x to clear them, the totals, and a chart of the days in block characters, a week a column when the days don't fit, of tokens or, with c, cost. Both sum sessions.StatsFor as GET /api/sessions/stats does, through Stats.Sum, which rolls the days up under a model and a folder as the app's view does — active time not kept by model, so none under one
2026-09-28 17:06:33 +08:00
Leon Zhao
82b0239dd0
fix: keep session filter menus open while scrolling ( #140 )
2026-09-28 16:56:10 +08:00
yetone
acd00dc4fb
panel: an open agent's effort is the effort picker's slider — its name and level over a thin track with a dot per stop, the ends named under it; a level shows at once, the row's bars with it, and is written after in order, so the agent's slow config write no longer holds the control for a second and a half (巨卡 / 变成之前的那种滑轨样式)
2026-09-28 16:51:53 +08:00
yetone
add95706d3
panel: the tabs lose their grey track — only the tab picked is a card, the others plain text on the panel (能否去掉背景的灰色)
2026-09-28 16:48:52 +08:00
yetone
b990735823
agent: RTK isn't given to OpenCode 2 — rtk init --opencode writes a plugin shaped for OpenCode 1 (a named export, no default {id, effect|setup}), which OpenCode 2 refuses to load with 'Plugin must export a default definition with an id and an effect or setup function' ( rtk-ai/rtk#4311 , still so in rtk 0.50.0); with opencode --version at 2 or later the Library shows 'Not for OpenCode 2' and won't switch it on, while a plugin already there can still be switched off and taken out (ARNO)
2026-09-28 16:36:01 +08:00
yetone
5f73e4f4fc
agent: OpenCode's magpie models name the reasoning levels each really has as variants ({level: {reasoningEffort: level}}, an empty set for a model without any) — OpenCode 2 otherwise makes low, medium and high of its own for every openai-compatible model (packages/core/src/variant.ts), so a model with none/high/max or none at all was offered levels it doesn't take; OpenCode 1 merges the same variants as before (kkgg)
2026-09-28 16:36:01 +08:00
yetone
e753cbafc5
panel: as drawn in A and C, strictly — the tabs stay put above what scrolls; an agent's line is its icon, name, model in words, its effort as three bars (faint when default) and a chevron that turns down when open, all in fixed columns; open, it shows a Model field with its label and a segmented effort control under the name; Show N more sits left, as a quiet line; the footer is one hairline over even padding, with when usage was fetched on its left on the Usage tab; usage vendors are small caps headings with their accounts or plan on the right, each account a card with its reset times under it and a ring per window, balances two to a row (你没有严格按照设计稿来实现呀 / 底栏中上下间距竟然都不一致)
2026-09-28 16:34:58 +08:00
yetone
9687f3d297
provider: WorkBuddy is a subscription — Tencent's CodeBuddy plan, signed in as WorkBuddy does, its own account read too
...
WorkBuddy (CodeBuddy Code's desktop app) keeps its signed-in session in
<shared data>/auth/workbuddy-desktop.info, plain JSON while credential
protection is off (its default); magpie reads that account, never writes
it, and skips it when the tokens are encrypted at rest. Further accounts
are signed in with WorkBuddy's own external-link flow (auth/state, then
auth/token polled until ready, then login/account) and kept in
logins.json. The plan is served OpenAI-compatibly at copilot.tencent.com
/v2 under the account's access token, with its id and domain in headers
(X-User-Id, X-Domain), exactly as WorkBuddy sends them; a near-expired
JWT is refreshed as WorkBuddy does, and a magpie-signed-in one's refresh
is written back beside it while WorkBuddy's own file is left untouched.
The models are its CLI agent's coding picks, and the credits come from
its resource summary as one window.
A card in Providers' subscription list signs in and shows the accounts;
the Provider is one of the account ids and joins the usage rollup.
2026-09-28 16:31:11 +08:00
Ns2Kracy
3bc9a744c8
Fix Settings segmented controls replaying thumb animations ( #135 )
...
* Fix segmented-control animation replay in settings
Scope the sliding-thumb cache to each control instead of sharing it across controls with identical options. Keep an existing thumb in place during rapid clicks so CSS continues its transition from the current position; a newly rendered control starts from its own last selection.
* Preserve thumb slide across control redraws
2026-09-28 16:25:04 +08:00
yetone
b9a240864b
settings: a theme picked while the window's state was on its way stays picked — coming back to the window reads its state, which can take seconds, and a read that a change of settings overtook put the old theme back when it came in, the picker showing the new (Light chosen, still dark); such a read now keeps the settings the page has. Saves go one after another, each sending what the page was drawn with plus its own choice over those before it: two quick ones (a theme, then the language) each sent the page as drawn, the second undoing the first, and their answers could land in either order
2026-09-28 16:19:00 +08:00
yetone
ebc33c721b
tray: a click on the bird flaps it — the wing beats twice and the tail flicks up once, 16 frames over about half a second (build/icon/gen.go tray-flap bends the outline about the tail's root and the shoulder, eased, so it stays one line); and the usage beside it no longer sits hard against it, a thin space between (Image #13 : 图标与用量之间没有任何的间距)
2026-09-28 16:15:40 +08:00
yetone
ec10f99113
panel: three tabs — Agents, Usage, Profiles, the one last open kept; an agent is one quiet line, its model in words and its effort as bars, that opens in place to its pickers (one at a time); usage is each vendor's accounts as cards under its name, a ring per window (amber from 90%) with the plan and when each window starts again under the account, balances as figures two to a row; the Usage tab only when there is usage to show, and the window view is as it was (A+C)
2026-09-28 16:09:55 +08:00
yetone
9e0fbd6ef7
ui: a segmented control's thumb slides only when it is the one picked — where a thumb was is kept per control, known by its place, not per set of options: every Off/On on Settings had the same, so a click on one, or opening the page, slid the others in from where it had been
2026-09-28 16:03:36 +08:00
yetone
3472235772
panel: usage rows all the same height — the account over one quiet line (when the plan ends, when its fullest window starts again, or what went wrong), its windows' names and shares over their bars in two columns, a hairline between accounts; reset times per window and long errors move to the tooltips, and a balance spans both columns, right-aligned, so its label isn't cut (还是乱呀)
2026-09-28 15:52:33 +08:00
yetone
29c706d1e7
provider: Tencent Cloud Token Plan is a preset — TokenHub's coding subscription (its general and Hy plans on one sk-tp- key, from console.cloud.tencent.com/tokenhub/tokenplan), served at its own endpoints under api.lkeap.cloud.tencent.com/plan: v3 for chat completions and anthropic for messages, no Responses (its Codex page asks for wire_api chat); models.dev lists only its Hy models, so the preset gives the plan's (tc-code-latest, GLM 5–5.3, Kimi K3 and K2.7 Code, DeepSeek V4, MiniMax M3 and M2.7, hy4-preview, hy3) until the plan's own list is fetched, and an entry imported at those endpoints is the preset
2026-09-28 15:41:57 +08:00
yetone
a285354560
panel: usage lines up — every account's windows sit in two columns shared down the list, each a name and share over its bar with when it starts again under it; one window takes the last column, a balance too, and what went wrong spans both, over two lines at most (Wey Gu: 有点点乱)
2026-09-28 15:36:10 +08:00
yetone
23847a8a56
library: hundreds of skills no longer make the Skills tab crawl — they're grouped by the GitHub repository they came from (owner/repo, how many, an Update N for those a check found changed, which agents have all or some of them, and a link to the repository), those on this computer in a group of their own, each group folded to its heading line and opened with a click, remembered in the browser; with more than 40 skills from several places the groups start folded. A filter over the skills (name, description, repository) shows when there are more than 8, opening the groups that have matches, and a filter or a fold draws only the groups again, not the page. Every row was drawn with a chip for each agent, 4400 icons for 400 skills, and each redraw, scroll and hover laid out and painted all of them: a row out of view is now skipped by the browser (content-visibility) and an agent's icon is made once and copied rather than made afresh (and probed) for every chip. On 400 skills from 6 repositories and 100 local ones, drawing the tab went from 131ms to 17ms folded (55ms with every group open), a pointer sweeping the list from 1.4–1.65s of main-thread work to 0.4s (0.67s all open), and a 6000px scroll from 0.65–0.71s to 0.29s (0.49s)
2026-09-28 15:35:54 +08:00
yetone
cd373b19fb
panel: the agents' names have their room back — since a row's squares sat side by side ( af840b0) the pickers grew by Codex's second square, and on the tray's panel every name was cut to its first two letters (Co…, Ge…, Op…); there the pickers keep the width they had and the model's column gives the square its room
2026-09-28 15:24:59 +08:00
minuque
35fca05b95
provider: a Devin subscription's own token limits are what agents are told — devin models list gives each variant max_context_tokens and max_output_tokens, and magpie parsed neither, taking the window and the reply cap from models.dev by bare id instead: swe-2's 262000/128000 were written as nothing at all, glm-5.2 at 1M where Devin gives 200K, gpt-5.4 at 922K where Devin gives 272K, grok-4-7's replies at 500K where Devin gives 100K, and gemini-3-8-flash at 1M/65536 from the one provider spelling it that way where Devin gives 1048576/65535 (215 of the 277 variants magpie serves were wrong). The CLI list's numbers are parsed and used, a family's taken from the variant its id follows, a variant without numbers from its family, and models.dev kept for what Devin's list doesn't name or a variant fetched before it was given its family's; a saved list takes Devin's numbers over what an older magpie wrote. Checked against Devin's own model configs, 277 of 277 variants now carry the subscription's numbers ( #133 )
2026-09-28 15:15:26 +08:00
Aronnax and Claude Opus 5.5
7931723d79
cli: 新增 magpie webdav，在终端里开启、修改和触发 WebDAV 同步 / add magpie webdav to turn on, change and run WebDAV sync from the terminal ( #127 )
...
* cli: magpie webdav — WebDAV sync from the terminal, what Settings › WebDAV sync does, for a machine with no window (WSL, a server over SSH)
magpie webdav shows it; on <address> [user=…] [password=…] [keys=no] [agents=no] [library=no] turns it on and syncs at once, asking for the passphrase (and the password, when a user has none); set k=v… changes what is given and keeps the rest; now, dismiss and off are the page's Sync now, OK and Turn off. Through the same davsync.Configure, Now, Dismiss and Off.
A sync, Off and Dismiss hold a lock the system keeps on sync.lock (flock; LockFileEx on Windows): the gateway's sync every 3 minutes and one from a terminal — or from the app's window while magpie serve has the gateway — would each save sync-state.json over the other's. The system lets it go when the magpie holding it ends, however it ends.
Configure keeps the saved password only for the same server (scheme and host) and user: an address moved to another server, or another user, no longer takes it there — in the app too, where a new address with the password left empty was sent the old one.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com >
* davsync, cli: from the review of #127 — the setup read again under the lock, Configure locked too, the password never an argument, one left behind asked for, a wait that runs out said in the status
Now reads the setup again once it has the lock: one that waited while another magpie turned sync off went on with the setup it had read, and saved sync-state.json back after the Off. Configure takes mu and the lock too, after a sync in progress.
magpie webdav takes neither the password nor the passphrase as an argument: password= asks for it, as passphrase= does.
Configure with the saved password left behind — another server or user, the password empty — says to type it and saves nothing, where the Settings page dropped it and the sync failed with 401 under a field that still said saved.
A wait for the lock that runs out is davsync.ErrBusy. Dismiss returns it, and the davsync routes put ErrBusy from a sync in the status they answer with, where the page shows a sync's failures; Save's own errors stay in its form, what was typed in it kept.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com >
* davsync, cli: the lock before mu, a wait bounded under the page's, one called off not called busy, the password rule in one place, a bare address with = in it
The lock comes before mu everywhere, so a wait for another magpie never holds mu, and Configure, Off and Dismiss wait for it 30 seconds at most, less than the Settings page gives a request: before, a request could hang on mu and then on the lock for minutes.
A wait for the lock called off, as when the page is closed or the gateway stops, is its context's error, not ErrBusy: nothing said another magpie was syncing.
What becomes of the saved password is decided in one place, davsync.SavedPassword, which Configure and magpie webdav both go by, where the two had rules of their own that had come apart: an account with a password and no user name, moved to another server, had its password dropped with nothing asked, and the sync failed with 401. It is asked for now, as for an account with a user.
magpie webdav takes a bare argument with :// in it as the address, = in it or not: https://host/dav?token= … was read as a field.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com >
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com >
2026-09-28 14:54:04 +08:00
yetone
f3db861b63
agents: Codex's sign-in picker shows each choice's whole explanation, under its name, rather than cut off after a few words; the Chinese reads which one is the default and what the Codex app shows
2026-09-28 14:40:32 +08:00
yetone
af840b012f
agents: a row's small squares sit side by side — Codex's sign-in square wrapped under its subagents one (the extras column held one); the squares share one cell, the column as wide as the row with the most
2026-09-28 14:37:09 +08:00
yetone
91aacfba1c
tray: the menu bar's usage says what the panel does — a subscription's quotas are served stale while they refresh behind, and the menu bar, reading them every few minutes, showed each refresh only a tick later (53% beside a panel's 57%); it reads them again the moment a refresh lands
2026-09-28 14:16:42 +08:00
yetone
6e677aabb6
codex: a thread started with magpie as Codex's provider opens again, and Codex can be kept in its API state ( #129 ) — signed in to ChatGPT, a magpie model is routed with openai_base_url ( c3931c9), and moving there from magpie as the provider (an older magpie's wiring, or one made while the account had used its allowance up, bd5bf42) took [model_providers.magpie] away, so the Codex app, which resumes a thread on the provider it was started on, said "Model provider magpie not found" for every one of them and came back signed in to ChatGPT. The table now stays once written, a base-URL wiring writes it too, and a sync puts back one an older magpie took away. Codex gets a sign-in field (magpie codex login api, a small square beside its pickers): api keeps magpie as Codex's provider while it is signed in, the app in its API state with magpie's models only; ChatGPT, the default, is as before
2026-09-28 14:11:17 +08:00
yetone and relus-cy
d53f90e746
gateway: Codex's namespaced tools reach a model magpie serves — spawn_agent, wait_agent and the rest of collaboration come inside a Responses namespace, which was dropped whole; each of its functions is offered as <namespace>__<name> (cut to 64 with a hash when longer), a past call with a namespace is read back under that name, and a call to one goes back to Codex with its name and namespace, streamed or not ( #130 )
...
Co-authored-by: relus-cy <14657224+relus-cy@users.noreply.github.com >
2026-09-28 14:01:27 +08:00
yetone
4eead4d4e0
agents: the effort picked for Cline and Qoder is the one they use — Cline's reasoning is written {enabled:true,effort} ({enabled:false} for none), as its own pickers leave an enabled false that drops an effort beside it, and such a one reads as none; Cline's VS Code extension (4.x), which takes its provider, model, base URL and key from globalState.json and secrets.json before providers.json, has those set too where they are, stashed and put back on the way out, and $CLINE_DATA_DIR is honoured. Qoder (1.1.6x) keeps each model's effort in model.preferences and moves model.reasoningEffort there once: magpie sets the model's preference (a model id with dots too), carries the effort in use to a model with none of its own, and keeps reasoningEffort for older Qoders. Cline's desktop app keeps its composer's model and effort in its web view's storage, which magpie leaves alone; its notice says to pick there
2026-09-28 13:41:31 +08:00
yetone
e02d3f28d7
library: a project's agents can have some of the library's skills as the project's own — under Skills, In projects takes a folder (the system's picker in the app, a typed path anywhere) and each of its skills gets agents' chips; magpie links the skill into <project>/.claude/skills for Claude Code and <project>/.agents/skills for Codex, Gemini CLI, OpenCode, Pi, Cursor and Copilot (the agents documented to read it; MiMo Code, Crush, ZCode, DeepSeek Harness and oh-my-pi aren't, so they're left out), or copies it when the project asks for copies, a copy made again whenever the library's skill changes (updates included). What it places is listed between magpie's marks in the project's .gitignore, made if there was none; taking a skill or the project away removes only what magpie placed, its lines and the folders it made once empty, and a folder of the same name that isn't magpie's is left as it is and said so. The home folder, or one whose project skills folder is an agent's own, can't be added
2026-09-28 13:34:17 +08:00
yetone
87a8330115
ui: Hide emails, once on, is a shade darker and no more — the purple fill and ring made a page tool the loudest thing on Routing and Usage; its struck eye and its words already say it is on
2026-09-28 13:29:54 +08:00
yetone
4cbd96a3e4
gateway: a model Claude Code names that magpie doesn't serve goes to the one it is set to use for that tier — claude-haiku-4-5-… for a title or a small task goes to its haiku tier's model, opus and sonnet to theirs, a name of no tier to its main model, rather than to some provider that happens to list the name and wasn't picked for it. Other agents, and ids magpie shows, are sent as asked
2026-09-28 13:25:25 +08:00
yetone
41cbe54a14
library: which skills from GitHub have changed there can be checked — Check for updates asks GitHub for the last commit to each skill's folder (one request per folder, a repository's skills together; once GitHub limits requests the rest are left unknown, each skill's trouble its own) and a changed one carries an Update available pill whose tooltip has the commit's summary and date, a click opening the changes on GitHub; Update N fetches just those. The library keeps a hash of a skill's files as fetched and, once a check finds GitHub's files to be the same, the commit they're at, so a later check needs only the API; a skill installed before this is compared by its files, the repository fetched once
2026-09-28 13:11:25 +08:00
yetone
c5e7955937
i18n: tokens reads token in Chinese on the usage tiles as well — a second entry for it, the routing rules', said tokens and won
2026-09-28 13:06:24 +08:00
yetone
e3984b2442
sessions: history by day — the Sessions view gets a range (today, 7, 30, 90 days or all), model and folder pickers, tiles for the range's cost, tokens, cache read and active time, and a daily bar chart of tokens or cost (weekly past 92 days). Each session file's cached reading now keeps its usage per local date and model, a message counted on the day of its timestamp, so a session that runs past midnight splits across both days and a file read on from where it stopped adds only what's new; Claude Code's repeated usage for one message moves with it to its last block's day. Totals come from every session file in the range, not the latest 200 the list shows: GET /api/sessions/stats?days=N returns each day's rows by agent, folder and model with their cost, so the view filters without asking again, and files last written before the range aren't read at all. Active time is the sum of gaps under five minutes between one line and the next in a session's main file (subagents run alongside it, so theirs aren't added), credited to the later line's day. The cache is version 2 and records the time zone, a change of which reads the files again; the list no longer drops the cached readings of files it doesn't show, only of files that are gone, and changed files are parsed in parallel. On 4000 synthetic files (880MB, 180 days) a cold read takes 0.74s, a warm one 22ms, a reload from the 4.7MB cache 49ms
2026-09-28 13:05:56 +08:00
elonnzhang