"CC Switch just met its strongest rival": magpie has 44 days and 30k stars; the only same-type project launched the same day has 533
What it is A local model gateway with a menu-bar app: switch the model for 70 multiple coding agents with one click, reuse your existing Claude / ChatGPT / Copilot subscriptions across other agents, and auto-switch accounts when quota runs out.
Why it took off The author, yetone, has pull in the Chinese developer circle on X. In the first week after launch, a cluster of KOLs reposted "the strongest rival to CC Switch." It also landed at the peak of demand for multi-subscription, multi-agent setups and cheap Chinese models. The product merged config editing, the gateway, and subscription sharing into one 15MB native app, with one-click migration from CC Switch. The later "fully AI-maintained" controversy brought a second wave.
CHow you could ride it Don't build another copy of the gateway. If you want stars, build its plugins and merch, or build the stable and team versions it hasn't done well, then copy its launch playbook: one-click migration from the big player, a one-line pitch, and partners with a reason to promote pushing it in their READMEs.
- Data (updated daily) · Repo created 2026-09-23 · 31,778 stars · 7 days +4,858
GitHub · stars Data 2026-09-28 → 2026-11-08 (42 days, 31 observations). Points before 10-28 come from deeply / archive backfill, not every day has one
In 2026 September 29, magpie, which had only been created 6 days earlier, was named in two tweets at once in the Chinese developer community on X. One called it "the terminator of model-switching tools", the other said "CC Switch has met its strongest rival in history". By Nov 6, this menu-bar tool for switching models across all coding agents had 31,097 stars. It didn't create a new category; it simply combined the work of three existing tools into one app, and the traction came mainly from the author himself.
Two posts, one question
Sep 29 11:14 (UTC), LinearUncle (about 16k followers) posted:
CCSwitch just met its strongest rival: yetone's magpie lives in the menu bar, switches models for Claude Code / Codex / and 20+ other agents with one click, and includes a local gateway (reverse proxy). Also, a question: if I use it to have Codex call Opus through my Claude subscription, is there a risk my Claude account gets banned?
This post got 190k views, 1,017 bookmarks, more than its likes (775) (X data, 11-06). Two hours later, Laogui (@laogui) posted a long thread: "Holy crap, @yetone's Magpie is the terminator of model-switching tools," listing four API protocols, model-pool routing, and the pitch "under 15 MB", with 45k views.
The question at the end of the first post, "will it get banned?", became the most-asked question in the comments later on. What people really wanted was to use subscriptions they had already paid for as an API.
What it is
A model gateway running on your machine, wrapped in a menu-bar app. The README's first line states the pitch:
Claude Code on Kimi. Codex on DeepSeek. Gemini CLI on GLM. OpenCode on your ChatGPT plan.
What it actually does:
- Switch any model for any agent: supports 70 agents including Claude Code, Codex, and Gemini CLI. magpie only changes the one setting in each agent's config file that matters, keeps comments intact, and notices when another tool has edited the config.
- Use subscriptions across agents: the Claude, ChatGPT, and Copilot subscriptions you're logged into can serve other agents. For Claude subscriptions, it actually calls the official
claudeprogram locally rather than forging request headers. Users generally feel this is less likely to get banned than server-side reverse proxies (this is users' view, with no official statement). - Auto-switch when quota runs out: if the same model is offered by several providers, it's merged into one pool, and when one account's quota is used up it switches to the next, so the agent doesn't error out.
Written in Go with Wails. The installer is about 15 MB, not Electron. It runs on macOS, Windows, Linux, Docker, and Termux, with GUI, TUI, and CLI interfaces.
Why this one, and why now
The author is the channel. yetone wrote avante.nvim and openai-translator, and now has about 104k followers on X (about 89k at the end of September). In the first week after launch, a batch of Chinese KOLs reposted it, with article titles like "Comparing CC Switch" and "Replace CC Switch." The clearest evidence is a control group: AstrLink launched one day before magpie with nearly the same pitch, also a local gateway with unified subscriptions and smart routing, and has only 533 stars so far, about one-sixtieth of magpie.
It hit at the moment of most pain. In the second half of 2026, a developer often held several subscriptions at once: Claude Max, ChatGPT Plus, Copilot, and used cheap models like DeepSeek V4, Kimi K3, and GLM-5.3, with several agents open simultaneously. "This subscription only works in one agent" and "it cuts off when quota runs out" were everyday frustrations.
Existing tools each cover one piece; it combines several. Config-editing tools (CC Switch) and gateway tools (CLIProxyAPI, new-api, LiteLLM) were separate. magpie puts config editing, protocol translation, subscription reuse, and multi-account switching into one lightweight app, and can import CC Switch configs in one click, so switching costs users almost nothing. That also gave people something to write about: how it beats CC Switch fits in one post.
The controversy fed a second wave. It ships dozens of versions a day (someone counted 19 days with 1,204 releases), doesn't accept PRs, and hands every issue to AI to fix. Peers called it "fast-food service." In Oct 13, yetone publicly shared the workflow: Claude Code with Opus 5.5, three loops running in parallel, "a little time each night to clean up the mess." That post got 500k views and 4,280 bookmarks, and Baoyu and @wquguru wrote long pieces on "AI maintaining the project itself." This round of discussion brought another batch of stars.
How the stars grew
| Date | star | Notes |
|---|---|---|
| 09-23 | 0 | Repo created |
| 09-28 | 1,275 | web archive |
| 10-09 | 6,733 | web archive |
| 10-16 | 13,379 | |
| 10-27 | 23,016 | Highest single-day gain in the observation window, +1,663 |
| 11-06 | 30,419 | GitHub API in the afternoon showed 31,097 |
Source: GitHub daily star records and web archives.
Since Oct 9, it has gained 500 to 1,660 stars a day, with no tens-of-thousands spikes. It gained 7 in the last 5,085 days, versus 7 in the previous 6,591 days, so it's cooling off, though still around 700 a day. The repo is under 60 days old and didn't clear GitHub trending's threshold, so the whole climb came from reposts and tutorials, not trending.
Plenty of interested parties are pushing it too. The README header carries a "Thanks to Kimi" line and sponsor slots for five API relay sites. The relays offer an "Add to magpie" one-click import link and list magpie in their own integration docs, so they have every reason to send traffic its way. Below that come tutorials on Zhihu, CSDN, cnblogs, HelloGitHub and Bilibili, and then English aggregator accounts picked it up (LinkedIn, Reddit, Substack). There are no posts about it on Hacker News or Product Hunt.
Another indirect signal: within minutes to a few hours of each release, the installer gets 400 to 950 downloads, mostly from the client's auto-update. Going by that, active installs are at least in the tens of thousands (inferred, not verified).
Who it's competing with
| Project | Scale (11-06) | How it differs |
|---|---|---|
| CC Switch | 152k stars, +2,042 over the last 7 days | Batch-edits config files only. No gateway, subscriptions can't be shared across agents, and it breaks once quota runs out. |
| OmniRoute | 85k stars, +2,283 over the last 7 days | A gateway built around a free model pool. Its pitch is "free riding." |
| CLIProxyAPI | 58k stars | A server-side reverse proxy that wraps subscriptions as an API. You host it yourself, and it relies on spoofed request headers. |
| new-api / one-api | 51k / 37k stars | A self-hosted gateway for distributing to relays and teams. |
| claude-code-router | 38k stars, +101 over the last 7 days | Initially only covered Claude Code. Now mostly stalled, and its description was just rewritten to lean toward magpie's framing. |
| AstrLink | 533 star | Nearly the same positioning, launched a day earlier, but its author has no audience. |
This category is already crowded. The leaders have tens of thousands to over a hundred thousand stars each. Around magpie, a ring of plugins has grown: a free model pack (310 stars), a Gemini web-version connector (157 stars), a usage display screen built by ESP32, and its official plugin repo has 203 stars. Similar tools that launched around the same time (antirion at 538 stars, respan-gateway at 570 stars, model-relay at 107 stars) haven't taken off.
If it were you
Verdict: don't build a copy. This slot already has a leader at 150k stars and several gateways with tens of thousands of stars each. magpie itself only broke in thanks to its author's 100K followers. Without that audience, even a near-perfect clone will most likely end up with a few hundred stars, like AstrLink.
Good fit for: developers who use Claude Code / Codex every day and want to build a small project that can reach a few hundred or a few thousand stars. There are three realistic paths:
- Build plugins and add-ons for it. magpie has a plugin repo and a user base in the tens of thousands. Build a free model pack, a connector for a specific model or relay, or a usage dashboard, and ride its users for stars. Someone has already done this and got 300 stars. Low cost, but the ceiling is low too.
- Fill the gap it leaves. It ships dozens of versions a day with AI-driven merges, and it has 3,289 open issues that keep growing. Stability and predictability are its weak points. You could build a "slow and stable" version that supports only three or four of the most-used agents, with pinned versions and clear rollback. Or build a team edition with shared keys and per-person usage stats. These gaps are inferred, and demand for them hasn't been validated.
- Copy its launch playbook for your own project: support one-click migration from the incumbent on day one; compress the pitch into one sentence a screenshot can carry; publish the controversial parts (like AI maintenance) and let the debate spread it for you; get partners with a traffic incentive (model vendors, relays) listed in the README.
Bad fit for: anyone with no technical audience who wants to build "yet another model gateway." Also a poor bet for anyone counting on subscription reuse. If Anthropic or OpenAI tighten their terms, that selling point could disappear overnight.
How to get users: push into the Chinese developer circles on X, plus CSDN and Zhihu tutorials. magpie has already proven this route works. Titles like "vs / alternative to XX" make search traffic easier to win than a name you invent yourself.
When the window closes: if you want to build plugins or add-ons, do it while magpie is still growing, roughly before early 2027. Once it cools off, or the official project builds these features itself, the opening is gone (inferred).
What would prove this read wrong: if an obscure author's similar gateway reaches tens of thousands of stars within a few months from organic traffic alone, that would show demand is strong enough to grow without a famous author behind it. At that point, going head-to-head with a replacement becomes worth serious consideration.
Research notes: competitor table, acquisition evidence, full research report
- Competitors
Name Where Launched Scale How it differs from this one CC Switch Open source 2025-08 152k stars, +2,042 in the last 7 days Batch-edits agent configs only. No protocol-translation gateway, no subscription reuse, and it breaks once quota is exhausted. magpie can import its config with one click. CLIProxyAPI Open source 2025-07 58K stars Server-side reverse proxy with spoofed request headers. You have to deploy and configure it yourself. magpie is a local GUI, and its Claude subscription path runs the real claude binary. claude-code-router Open source 2025-02 38k stars, +101 in the last 7 days Initially served only Claude Code, configured through config files. Stalled. new-api / one-api Open source 2023 51k / 37k stars Self-hosted secondary distribution aimed at relays. magpie is a personal local tool and has absorbed its middleware. LiteLLM Open source 2023-07 63K stars Enterprise gateway configured in YAML. Doesn't manage agent configs and doesn't reuse subscriptions. OmniRoute Open source 2026-02 85k stars, +2,283 in the last 7 days Pitched on a free model pool ("free riding"). magpie focuses on managing your own subscriptions and keys, with a native GUI. AstrLink Open source 2026-09-22 533 stars Nearly identical positioning, but without the author's influence, it sits at only about 1/60 stars. That shows distribution is the key. OpenRouter Web 2023 Big A cloud pay-as-you-go unified API. It can't reuse subscriptions you already bought, and it doesn't change agent configs. - Where users come from
- Confirmed The author posted on X (about 89k followers), plus Chinese KOL reposts: @laogui 9-29 "the end of model-switching tools," @LinearUncle "CCSwitch meets its strongest rival," Agili Tech Radar 9-24, @VersunPan gateway comparison.
- Confirmed Controversy-driven second wave: after peers attacked it as "fast-food service," @wquguru 10-12 and @dotey published long posts analyzing AI auto-maintenance, and yetone 10-13 publicly shared the /loop workflow.
- Confirmed Chinese tutorials, reviews, and videos (SEO): Zhihu, cnblogs 10-12 / 10-28, CSDN 10-18 / 10-29, middlefun, HelloGitHub, Bilibili, and YouTube "vs CC Switch" content.
- Confirmed Migration from CC Switch: built-in import of CC Switch / Claude Code / Codex / Alma configs; several posts titled "Migrating from CC-Switch" and "Replacing CC Switch."
- Confirmed Sponsored traffic from model vendors and relays: the README lists Kimi support and 5 sponsoring relays; there are Add to magpie import links; APIYi and Aiberm have integration docs; partner clicks go through usemagpie.ai/go/ tracking.
- Confirmed The product asks for stars: the README ends with "a ⭐ helps others find it."
- Confirmed English aggregator accounts: LinkedIn, Instagram, Facebook, Reddit r/LovingAIAgents, Substack, pyshine. No related posts in the Hacker News or Product Hunt libraries.
- Inferred Paid ads: none found.
Why yetone/magpie took off
Source: GitHub · research day 2026-11-06 · data card /home/ljr/fanout/why/cards/gh_yetone__magpie.json
One line
magpie is a local LLM gateway built by yetone (author of avante.nvim and openai-translator, about 89k followers on X). It ships with a menu-bar app and lets you switch models in one click for 70 coding agents, including Claude Code, Codex, and Gemini CLI. It can also route your existing Claude / ChatGPT / Copilot subscriptions to other agents and switch accounts automatically when quota runs out. It took off for three reasons stacked together: the author's pull within the Chinese developer community on X; a wave of demand from people running several agents and several subscriptions at once, plus cheap Chinese models; and a product that combines CC Switch, CLIProxyAPI and new-api into one, light enough to install easily. Growth came from Chinese KOL reposts and tutorials, then spread to English aggregator accounts. It did not come from GitHub Trending, and there was no paid advertising.
1. Data: 30k stars in 44 days, steady growth with no spikes.
- Repo created 2026-09-23 (first commit 9-22). Wayback archives show 1,275 stars at 9-28, 6,733 stars at 10-09, 23,016 stars at 10-27, 30,419 stars at 11-06 (our github repo_day). By the afternoon of 11-06, the GitHub API showed 31,006 stars, 2,693 forks and 3,273 open issues.
- Since 10-09 it has gained 500–1,660 stars a day, peaking at 1,663 on 10-27. Over the last 7 days it gained 5,085, compared with 6,591 in the 7 days before that. It is cooling slowly, but still adds about 700 a day (data card / repo_day).
- The curve is flat, with no single-day spikes of tens of thousands. The fork-to-star ratio is about 8.7%, versus a median of about 11% for peer repos of similar age and size. The suspect flag in the repo library is empty.
- The repo is only 44 days old, short of the roughly 60 days needed to qualify for GitHub Trending, so none of this growth came from Trending exposure (measured finding from the github repo schema).
- Indirect evidence of usage: the signed installers are published to yetone/magpie-releases, with 50–60 releases a day (1,204 tags in 19 days, see @wquguru's analysis). Installed clients auto-update, so each release gets 400–950 downloads within minutes to a few hours, mainly the Windows exe and macOS arm64 builds (GitHub API, v0.1.3108–3110, v0.1.2986–2988). By this estimate, active installs are in the tens of thousands or more. This is an estimate, not verified.
2. Competitors
| Competitors | Form | Launched | Scale (GitHub repo 11-06) | How magpie differs |
|---|---|---|---|---|
| CC Switch(farion1231/cc-switch) | Open-source desktop app | 2025-08 | 152k stars, +2,042 in the last 7 days | Batch-edits each agent's config files (swapping providers / keys). It has no protocol-translation gateway, so "run Codex on a Claude subscription" isn't possible, and it breaks once quota runs out. magpie can import its config directly, which removes the switching cost entirely. |
| CLIProxyAPI(router-for-me) | Open-source server / reverse proxy | 2025-07 | 58K stars | Wraps Codex / Claude Code / Antigravity subscriptions as an API. You have to deploy it and configure each agent yourself, and it relies on spoofed request headers. When magpie uses a Claude subscription, it actually drives the local claude binary, which is considered lower ban risk. |
| claude-code-router(musistudio) | Open source CLI | 2025-02 | 38k stars, +101 in the last 7 days | Initially only supported Claude Code, configured by editing JSON. Now stalled. |
| new-api / one-api | Open-source self-hosted gateway | 2023 | 51k / 37k stars | Aimed at secondary distribution for relays or teams, requires a server to deploy. magpie is a personal local tool and has also brought new-api's middleware (param_override, model_mapping) over. |
| LiteLLM | Open-source SDK / gateway | 2023-07 | 63K stars | Enterprise gateway that needs YAML configuration. It has no layer for "change agent configs, reuse subscriptions." |
| OmniRoute(cheaper-inference) | Open-source gateway | 2026-02 | 85k stars, +2,283 in the last 7 days | Built around a free model pool with 375 providers, and its pitch is "free riding." magpie's pitch is "manage your own subscriptions and keys," and it ships with a native GUI. |
| free-claude-code / 9router | Open source | 2026-01 | 67k / 32k stars | Marketed as "use Claude Code for free," which sits in a grayer zone. |
| AstrLink(Calcium-Ion) | Open-source local gateway | 2026-09-22 (one day before magpie) | 533 stars | Nearly identical positioning (local gateway + unified subscriptions + smart routing + privacy), but without the author's influence. It sits at about 1/60 stars, compared with magpie's. |
| OpenRouter | Commercial web service | 2023 | Big | A cloud unified API billed pay-as-you-go. It can't reuse subscriptions you already bought, and it doesn't change agent configs. |
| Built-in model switching in each agent | Big-company features | — | — | Only switch to your own model or your own API format |
Verdict: this niche is crowded, and CC Switch (150k stars) is the big incumbent. magpie didn't open a new category. It combined already-proven ones and made them a better product.
3. Growth levers (by evidence)
- The author posted on X, and Chinese KOLs followed with reposts (confirmed, main channel). yetone has about 89k followers on X (x-radar), and his magpie-related tweets get about 34k views each. 9-29 laogui (@laogui) wrote "the ultimate killer of model-switching tools," LinearUncle wrote "CCSwitch just met its strongest rival," 9-24 Agili Tech Radar reviewed it, and @0xGky and @VersunPan compared 4 gateways. 10-12 By 10-13, 宝玉 (@dotey) and @wquguru wrote long posts on "AI maintaining the project itself," which turned it into a topic.
- Controversy marketing (confirmed): some peers called it "fast-food service" and said they "don't dare use it." yetone publicly shared his workflow: Claude Code with Opus 5.5, three /loop runs in parallel, AI writing, reviewing, merging, and shipping on its own, dozens of releases a day. The debate itself became a second wave of spread (tweets from @wquguru 10-12 and @yetone 10-13).
- Chinese tutorials and reviews (confirmed): Zhihu, Cnblogs (10-12 "local AI gateway," 10-28 iTech "23k stars in five weeks"), CSDN (10-18 "Migrating from CC-Switch to magpie," 10-29 "7 days, 2600 stars"), middlefun "I replaced CC Switch with magpie," HelloGitHub listing, and Chinese Bilibili and YouTube videos "Comparing CC Switch: three limitations."
- Pulling users from CC Switch (confirmed): one-click import of provider configs from CC Switch / Claude Code / Codex / Alma; many pieces are titled "compare with / replace CC Switch."
- Ecosystem and relay-station partners (confirmed): the README lists Kimi support and five relay-station sponsors (APINEBULA, 零词元, APIKEY.FAN, WandAPI, AIGoCode). An "Add to magpie" one-click import link lets relay stations write magpie into their own docs (API易 and Aiberm already have integration docs). In the app's add page, partners rank first, and clicks go through usemagpie.ai/go/ counting. Relay stations have a reason to send traffic its way.
- Asking for stars inside the product (confirmed): the README says "If magpie saved you from editing one more config file, a ⭐ helps others find it."
- Secondary spread from English aggregator accounts (confirmed, but small): LinkedIn, Instagram reels, Facebook ("This 23.7K-star repo…"), Reddit r/LovingAIAgents, a Substack "GitHub Top 3 AI Coding Agent Router," a pyshine source walkthrough, and aicoder.com 10-03 news. Our HN and Product Hunt libraries have no magpie posts.
- Ads: no evidence found. Our ad libraries only track products on the list, so not finding anything doesn't mean no ads were run.
4. Why it took off
- Timing: the second half of 2026. Most developers hold several subscriptions at once, such as Claude Max, ChatGPT Plus, and Copilot, plus cheap Chinese models like DeepSeek V4, Kimi K3, and GLM-5.3, and many run several agents. "This subscription only works in one agent" and "it cuts off when the quota runs out" are daily pains. The most common comment question is "will my account get banned?", which itself shows the demand is for using subscriptions as APIs.
- The author's credibility: avante.nvim (about 18k stars, figure from the iTech Cnblogs post), openai-translator, and Alma are all well known in this circle. Chinese developers on X trust "yetone the master," and dozens of KOL reposts came in the first week after launch.
- Product strength: native Go + Wails, an installer of about 15 MB, no Electron. GUI, TUI, CLI, Docker, and Termux are all supported. Config edits preserve comments, write atomically, and detect when another program has changed the config (drift). One gateway speaks four protocols at once. Claude subscriptions run through the real
claudebinary, which users see as the least likely to get banned. Route groups smart / pace schedule around quota reset times, pitched as "don't waste your subscription quota." Privacy redaction. Usage and cost tracked per key. Almost no setup: one feature, done, install and use. - Iteration speed as a selling point: issues get fixed the same day, with dozens of releases daily. PRs aren't accepted; AI handles everything in a closed loop. User requests show up in the product quickly, so issues keep piling up (3,273 open), and community stickiness keeps growing.
- Reasons people stay: once every agent points at the local gateway, with route groups and multiple accounts configured, switching away is costly. Auto-update adds to this, and active installs keep rising (estimated from release download counts).
5. Differentiation
Similar tools either only edit configs (CC Switch, claude-code-router) or only run gateways (LiteLLM, new-api, CLIProxyAPI). magpie is the first to put "edit each agent's config, a local protocol-translating gateway, reuse existing subscriptions, and auto-switch across multiple accounts" into one lightweight native menu bar app. The subscription-reuse part takes the seemingly safer route of actually running the official CLI.
Is that why it took off? Half of it. AstrLink, launched the same day with nearly the same positioning, has only 533 stars, which shows differentiation alone isn't enough. Differentiation gives people a concrete "how is it better than CC Switch" to discuss. What actually lit the fuse was the author's influence and the Chinese KOL network. So the accurate story: the author's resources ignited it, product differentiation gave the reposts something to talk about, and it got users to actually move over from CC Switch.
6. Visibility and copycat risk
- Visibility: widely discussed. 31k stars. Top Chinese developer accounts on X (宝玉, laogui, and others), Zhihu, CSDN, Cnblogs, Bilibili, and YouTube have all covered it, and English aggregators have reshared it. Revenue isn't public: the product is free and MIT-licensed, and the only visible monetization is relay-station sponsorships, Kimi support, and partner click referrals, with amounts unknown.
- Copycats and parasitic ecosystem: plugins and add-ons around magpie have already appeared, such as mu-zi-lee/magpie-our-free-model (310 stars), magpie-intelligence-check, BUKOWSKIREAL/magpie-gemini-web (157), key-to-magpie, magpie-usage-display (ESP32 usage screen), and magpie-muse-web. The official magpie-community/plugins repo has 203 stars. Similar tools launched around the same time include cablate/model-relay (10-17,107 stars), antirion (10-17,538 stars), and respan-gateway (9-25,570 stars). claude-code-router also changed its tagline to "One local control plane for every AI agent," moving toward magpie's positioning. No meaningful direct clones spotted.
7. What others can learn
- Enter a proven category where existing tools each cover only one piece, and build "the combination plus a native lightweight GUI," with one-click migration from the incumbent on day one.
- The selling point fits in one line: "Claude Code on Kimi, Codex on DeepSeek." The screenshot is the marketing asset.
- Make the workflow of "AI maintaining the project itself" public, so the controversy becomes a second wave of spread.
- Recruit relay stations and model vendors as sponsors and channels. They have a referral incentive, and the open-source tool gets promotion and revenue from it.
- Use issues as the request intake, and AI loops for fast delivery, so users feel "file it and it ships."
8. Still unclear
- Real active user count: release download counts mix in auto-updates, so it's hard to convert. The client does daily anonymous reporting, but the data isn't public.
- How much sponsorship and referral revenue there is, and whether Kimi's "support" is cash or credits.
- ToS risk of subscription reuse: if Anthropic or OpenAI tighten rules, the core selling point could stop working.
- How good the quality and stability are given very high release frequency and automatic AI merges (open issues keep rising, and peers have raised doubts).
- Unverified how many stars come from in-product star requests and one-off KOL reposts versus real usage.
Sources
- Data card /home/ljr/fanout/why/cards/gh_yetone__magpie.json; our github library repo_profile / repo_day (2026-11-06); hackernews and producthunt libraries (no related posts)
- GitHub API: repos/yetone/magpie, repos/yetone/magpie-releases/releases (2026-11-06)
- README: github.com/yetone/magpie; website usemagpie.ai/zh/
- X: x.com/yetone/status/2109855710444237018, x.com/yetone/status/2104042148496842898, x.com/laogui/status/2104924921654648959, x.com/LinearUncle/status/2104892506282537240, x.com/wquguru/status/2109650264601117141, x.com/dotey/status/2110084393255514268, x.com/VersunPan/status/2103297487486513598
- Chinese articles: www.cnblogs.com/itech/p/23463165, www.cnblogs.com/codechen8848/p/23262129, tianqi.csdn.net/6ad4ceff536f457592b0b9d0.html, blog.csdn.net/gitblog_00006/article/details/160524977, middlefun.com/posts/bgj7fdg9/, hellogithub.com/repository/yetone/magpie, channel.agi.li/posts/91, www.bilibili.com/video/BV1pMHs68EVb/
- English: pythonlibraries.substack.com/p/magpie-github-top-3-ai-coding…, aicoder.com/news/news-20261003-yetone-magpie-agent-model-rou…, www.reddit.com/r/LovingAIAgents/comments/1x40k9h/, pyshine.com/Magpie-Every-Agent-Model-One-Menu-Bar-Source-Tou…