26 Commits

Include renames

Author	SHA1	Message	Date
yetone	08309e8c04	providers: Test models sends each model agents see a tiny request of its own, on the endpoint it's served on and with a key that sees it, and marks its chip with a dot — green with how long it took, red with what the vendor said — so a relay whose other models answer can't hide one that doesn't (magpie provider test <id> <model>… does it in the terminal). Usage has Hide emails too, one setting with Routing's, to screenshot the subscription cards	2026-09-27 12:26:00 +08:00
yetone	d7999aefc7	providers: a balance endpoint named on a provider can be asked with an access token of its own (balance.token), with the provider's headers — a new-api relay's /api/user/self tells the whole account's quota to its access token and New-Api-User, not to a key: magpie provider set my-relay balance=…/api/user/self balance.path='$data.quota / 500000' balance.token=… header.New-Api-User=…	2026-09-27 02:30:55 +08:00
yetone	6fd85894ea	routing: Jev (TypeSafe's System One) as a group's classifier — asked once as a turn begins which of the rules' intents the message is, with how sure it is, and, for a group with effort auto, how hard the turn is to think about; the turn's requests then ask their model for that reasoning, where the agent asked for any. TypeSafe is a decision provider: it serves no conversation and is no group's member	2026-09-27 01:53:04 +08:00
yetone	f12a75899d	providers: a subscription whose models come from its own CLI (Kiro, Devin, Cursor …) has no host, so magpie provider models said its models were fetched "from" nothing; it names the provider. Kiro signed in with Google or GitHub says so, not SocialGoogle. Checked against a real Kiro account: plain and streamed text, a tool call and its result, OpenAI chat with another model, and Claude Code reading a file through Kiro	2026-09-27 00:51:17 +08:00
yetone	47e12df418	models: a provider's model can go by a name of the user's, and offer only some of its reasoning levels — Claude Opus 5.5 · Claude Code can be Opus 5.5, and a model with six levels can offer just low, medium and high. Both are kept in settings.json by provider/model (modelNames, modelEfforts), apart from the vendor's list, so a Refresh, a restart or an upgrade leaves them, and the same model from another provider keeps its own; a provider renamed takes them along. They are applied where the catalog is made, so the gateway's /v1/models, the lists magpie writes into the agents (Codex's model catalog, ZCode, Pi, OpenCode, OMP …) and magpie's own pages all show them, and a change rewrites the agents' lists as any other change of the catalog does. Only what is shown changes: the id, where requests go, and the levels the vendor is asked at stay as they were; a found routing group keeps the model's own name. The provider's editor has Names & levels under its models — a name typed in place, a tick per level, Restore default — and the terminal has magpie model name <provider/model> <name>|--reset and magpie model efforts <provider/model> low,medium,high|--reset. Issue #92	2026-09-26 23:23:45 +08:00
yetone	c4268e524f	providers: a provider's id can change — its editor has an ID field (magpie provider set <id> id=<new> in the CLI), and renaming it moves what named it by the old one: the agents on its models (each spelled its own way, recorded as magpie's), the routing groups' members, rules and classifier, other providers' fallbacks, which agents are shown it, and the vendor's fetched list. The old id stays with it, so an agent still running on the old config reaches it, a profile saved before applies to the new id, and its usage so far is counted under the new one. Asked on Discord	2026-09-26 20:22:30 +08:00
yetone	9b06c30790	balance: a custom provider's balance field can name several amounts, each with a label, apart by ";" — Command Code's credits reply is 5h: windowLimits.fiveHour.used / windowLimits.fiveHour.cap %; week: windowLimits.weekly.used / windowLimits.weekly.cap %; $credits.monthlyCredits, shown as "5h 0% · week 3.4% · $70.00" wherever the balance is (Usage, magpie provider, magpie quota). Asked on Discord	2026-09-26 18:41:01 +08:00
yetone	73be42eca8	models: each agent can be shown only some of them — a provider or group gets a family (magpie provider set relay-x family=relay), and magpie visible zcode relay shows zcode only that family's models (or named providers and groups): in the files magpie writes for it and in what /v1/models answers it, told apart by its User-Agent; magpie models zcode lists what it is shown and what is kept from it, and magpie visible zcode all shows it everything again. A model kept from an agent is still served when asked for by name. Asked for on Discord	2026-09-26 16:02:29 +08:00
yetone	c83e03d5c7	provider: how long a request a model takes can be set — magpie provider set <id> context=272k (all its models) or context.<model>=1m, and magpie group set <id> context=… for a group, which otherwise takes its shortest model's; agents are told it (Pi's contextWindow, ZCode, Codex's catalog, Grok, omp, dsh) over what the vendor or models.dev says, and the Providers and Routing views keep it when saved. An empty value clears it	2026-09-26 14:39:55 +08:00
yetone	5f839eae99	provider: saved Claude or Codex accounts that are not offered say why — under a HOME where the agent is not signed in (a magpie serve with its own HOME, no ~/.codex/auth.json or ~/.claude/.credentials.json there) they went missing without a word; magpie serve, magpie providers and the Providers view now tell	2026-09-26 14:32:48 +08:00
yetone	6b39a69bf4	provider: a balance field can be a sum — paths into the reply and numbers with + - * / and brackets, "(1 - credits.monthlyCredits / 70) %" for what is left of a plan, a "%" after it showing a percent of 1; "data.total / 500000" and "$data.x" read as before	2026-09-26 14:26:28 +08:00
yetone	c330e20231	provider: an account's "only through routing groups" holds, and one removed stays removed — All() merged a signed-in account's picks without Unlisted, so provider listed claude no saved but claude/* stayed in /v1/models; and any save of an account rebuilt its entry without Hidden, so a removed one came back; a save now keeps it removed, and Add it back (and magpie provider add <account>, which made claude-2) goes through ShowAccount, keeping its picks; and magpie provider set <id> k=v… changes a provider with add's pairs (the v0.1.77 notes named it, it didn't exist)	2026-09-26 01:38:37 +08:00
yetone	81342b1b05	provider: a custom provider can list its models from a URL of its own — Xiaomi MiMo's plans are served at their own hosts while the list is at api.xiaomimimo.com/v1/models, so fetching models from the base URL found nothing; More endpoints has a Models URL (模型列表地址), asked with the key and nowhere else, and magpie provider set <id> models.url=… sets it (#67)	2026-09-25 22:16:11 +08:00
yetone	925e4a6ccd	provider: a provider can serve only through routing groups — ticked, its models leave the list agents pick from (and /v1/models) while the groups they are in, and a request naming provider/model, still reach them (magpie provider listed <id> no); the routing groups come first in the list; a model list fetched from the vendor can be forgotten; magpie group add under a name in use replaces that group; and the Library gives MCP servers to Claude Desktop, the ones it runs as a command — a remote one is added in its Connectors, which the page says	2026-09-25 20:11:29 +08:00
yetone	35ebc94d58	provider: a preset's provider takes request headers of the user's own, and a preset can be added more than once (#50) — which workspace a key that reaches several is for (anthropic-workspace-id), or who the app is to OpenRouter, could only be said by a custom provider, so it meant giving up the preset's endpoints and catalog; the editor now shows headers for presets as well, offering the ones the vendor documents with their values left to fill in, and "Add another" makes one more provider of a preset under an id of its own (anthropic-2) where adding again replaced the first; the same key, host and headers twice is refused as the one already there, and importers keep a preset's headers and its preset when they split an entry off to a free id	2026-09-25 09:36:42 +08:00
yetone	520a2425fc	gateway(routing groups, affinity) + gui(routing): routing groups — several models, from one provider or many, that an agent picks as one (group/<id>), routed over all their members' keys and accounts together, smart, in order, in turn or least used first; a model more than one provider serves is a group magpie finds on its own, and becomes the user's once changed. Affinity keeps a conversation with the key or account that answered it — for the session, within a turn, never, or by default while what the vendor read from its cache is worth keeping and not yet cold — so the prompt cache holds; in turn now spreads turns rather than requests, a turn's tool results staying where it began. The Routing view shows each agent's requests in its own colour, the magpie flying them through the gateway's box rather than jumping across it, groups and why a conversation stayed or moved; and a Hide emails switch blurs the email addresses on the page, for a screenshot to share	2026-09-25 04:07:40 +08:00
yetone	2b1e9e8619	usage: the Usage page shows what is left on an API key beside the subscriptions' allowances — DeepSeek, Kimi, OpenRouter and SiliconFlow are asked by their hosts, and any custom provider can name its balance endpoint and where the amount sits in the reply (Balance URL / field in the editor, balance= / balance.path= in the CLI), each key it has on asked with itself; magpie provider <id> prints it too (#40)	2026-09-25 01:12:18 +08:00
yetone	435d65882b	gateway: fallback — when a provider is out of quota, rate limited or down, a request goes to the next model you listed for it, before any of the reply is sent; set it in the provider editor or with magpie provider fallback	2026-09-24 14:04:42 +08:00
yetone	61004668ac	provider: a custom provider can have its own icon — a picture of yours (PNG, JPEG, SVG…) or any built-in one, in the editor or with magpie provider icon (#12)	2026-09-24 13:10:45 +08:00
elonnzhang	3ffebeebb6	provider: custom request headers for custom providers ... Extra HTTP headers, typed by the user, ride on every request magpie makes to a plain key+URL provider — forwarded calls, connectivity tests, and model-list fetches — applied after the auth headers. Presets and signed-in agent accounts ignore them. Editable in the GUI (with a JSON value mode) and via the CLI as header.X-Foo=bar.	2026-09-24 12:50:51 +08:00
yetone	d77e14701b	provider: a signed-out Claude Code account goes away, and any account can be removed (#9) ... Logging out of Claude Code can leave its credentials behind; claude auth status now decides. Removing a Claude, Codex or Copilot account hides it from magpie (the agent stays signed in); Add it back, or magpie provider add <id>, restores it.	2026-09-24 12:42:14 +08:00
yetone	4bd3f3a4b5	import: magpie://import links add a provider after the user confirms ... A vendor or relay can hand out a ready-made provider as a link. The app registers the magpie scheme (Info.plist on macOS, HKCU on Windows, a .desktop handler on Linux), a second launch hands the link to the running one, and the window shows what the link would add, with the hosts the prompts and key would go to, before anything is saved. `magpie import` does the same in a terminal.	2026-09-24 12:17:45 +08:00
yetone	402a96c39d	Rename dial to magpie, with a magpie for a logo ... The product, module path (github.com/yetone/magpie), binaries, env vars (MAGPIE_ADDR, MAGPIE_DEV_UI, MAGPIE_THEME, MAGPIE_DEBUG), config and cache folders (~/.config/magpie, ~/.cache/magpie), bundle id (com.yetone.magpie), gateway provider id and token, and every UI string now say magpie. On first run magpie copies ~/.config/dial and ~/.cache/dial to the new folders when they don't exist yet (copy, not move, so a still-running dial keeps working; the old folders can be deleted by hand later). The logo is a small round magpie in profile: one path for the header and the tray, and the app tile adds the white belly and the blue-green tail. The header mark is drawn in ink rather than the accent colour, which fought the text in light mode.	2026-09-23 23:55:11 +08:00
yetone	9174a6510b	provider: signed-in agents (Codex, Copilot) become providers ... A Codex (ChatGPT) or Copilot login is a subscription with models behind it, so dial offers it as a provider: every other agent can use its models through the gateway. The agent's own credential file is read each time, tokens are refreshed the way the agent does it, and only the model picks are stored. Claude Code is found but deliberately not offered (Anthropic's terms), and the CLI and API say so. The gateway signs upstream requests through the provider (Sign/Prepare), translates non-streaming requests for backends that only stream, and now recognises an event stream by its body when the vendor sends no Content-Type, which is what the ChatGPT backend does.	2026-09-23 15:25:05 +08:00
yetone	8fb93f8fc2	Make dial a local LLM gateway with preset providers and one catalog ... dial now serves OpenAI chat completions, OpenAI Responses and the Anthropic Messages API on 127.0.0.1:3425 and forwards each request to the vendor that serves the model, translating between the APIs when the vendor speaks a different one (streaming, tool calls and reasoning included). Every agent points at that one URL; models are spelled provider/model. Providers are added from presets (vendors, relays, local servers) with just an API key, or as custom OpenAI/Anthropic-compatible endpoints. Keys live in ~/.config/dial/providers.json; nothing is read from the shell environment. Each provider chooses which of its models to expose. Agents get gateway wiring instead of vendor-specific tables: Claude Code via the env block, Codex via a dial model provider plus a model catalog file, OpenCode/Pi/Crush via a dial provider entry; native settings are stashed and restored when a native model is picked again. The Providers page shows the gateway, each provider with the agents on it, an inline editor with model chips, and an add sheet of preset tiles. CLI: dial presets | providers | provider add|key|models|test|rm | models | serve.	2026-09-22 22:43:51 +08:00
yetoneandClaude	0a234ce41d	dial: one dial for every coding agent's model ... Wails v3 tray panel and window, TUI and CLI. Switches model, effort and provider for Claude Code, Codex, Gemini CLI, OpenCode, Pi, Goose, Cursor, Copilot CLI and Crush with format-preserving config edits. Providers page and registry, stored keys, live vendor model lists, profiles. Co-Authored-By: Claude <noreply@anthropic.com>	2026-09-22 21:47:29 +08:00