Stringers
lili-luo/dsh-plugin-bundle · lili-luo

"No reverse proxy, no account bans": a DSH plugin got 311 stars in 8 days from two forum posts, and also put itself on the ban list

What it is A free, open-source DeepSeek Harness plugin bundle. It uses the official agy command-line tool on your machine to plug the Gemini 4 and Claude Opus 5.5 models from a Google AI Pro/Ultra subscription in as native DSH models, plus a script that unlocks context from 256K to roughly 1M.

Why it blew up The Chinese-speaking community had just stockpiled cheap Google subscriptions. The official client is hard to use, and reverse proxies were getting accounts banned in droves. The author first posted a research thread on LINUX DO, then a promotional post saying "no reverse proxy, no bans," then a major update thread three days later. Those two posts line up with the two steps in the star curve.

CHow you could follow it Don't build yet another plugin that wires a subscription into a framework. That lane is crowded and violates Google's terms. Copy the distribution rhythm instead: in a Chinese developer community where you have credibility, post a research thread, a promo thread, and a major update thread timed to replies, for a compliant project that fills a gap left by a new popular host.

Grade C: the three-post rhythm is learnable and copyable, but this position already has a dozen similar projects. Google has publicly named this kind of integration as a violation and started blocking and banning accounts, so late followers will get fewer stars and carry a ban risk. What's circulating in small circles
Data (updated daily) · Repo created 2026-11-06 · 344 stars · 7 days +42
GitHub · stars
020040011-0711-1011-1311-1711-20344
Data 2026-11-07 → 2026-11-20 (14 days, 14 observations). Points before 10-28 come from deeply / archive backfill, not every day has one

On the night of Nov 6, a 22-year-old product manager posted on LINUX DO, plugging the Google subscription he couldn't use up into DeepSeek Harness. Two days later the repo gained 122 stars in a single day, and reached 311 in 8 days. Functionally it wasn't the first to do this; a similar plugin, August, already existed. It won on picking the right community, hitting the right timing, and writing the right title. That same title started backfiring on it a week later.

A post whose title says "no bans"

In 2026 Nov 6 21:59 (Beijing time), LINUX DO user @23375 posted under the "open-source promotion" tag a post titled "No reverse proxy, no bans: Antigravity via the ACP protocol, perfectly embedded in the DeepSeek harness." The post opens with screenshots of other people's banned accounts, captioned "bans have been increasing a lot lately"; it ends with "if you're interested, give the repo a star." The GitHub repo lili-luo/dsh-plugin-bundle was created in the same hour.

The replies went through at least 7 pages. The most common were "urgent, my Haiku quota is basically unusable" and "bookmarked, will set it up tomorrow" ("Haiku" is a forum nickname for Gemini). Some also reported bugs, asking why Gemini 4 didn't show up on the Pro account.

This didn't come out of nowhere. Three days earlier (11-03), the same person had posted a technical thread, "Don't waste the Turkish-region gemini20x you just bought: research on antigravity context limits & a method to unlock a million-token context," which got 1.6k views and included an unlock script. He first gathered readers annoyed that Google's official client "cuts off context," then posted the formal promo.

What it is

DeepSeek Harness (DSH) is an agent framework DeepSeek open-sourced in Aug 13. The main repo now has 280k stars. Google's AI Pro / Ultra subscriptions include quota for Gemini 4 Argon and Carbon as well as Claude Opus 5.5, but it can only be used in Google's own Antigravity client and the command-line tool agy.

The repo ships two things:

  • dsh-llm-antigravity-acp: Launches the official agy acp process locally and talks to it over ACP (Agent Client Protocol), so your subscription models show up in DSH's model picker alongside the built-in ones. Login stays in the official process and the system keychain; the plugin never touches it. DSH's tools, sub-agents and context compression all keep working. There's a "quota pill" next to the input box showing your weekly quota and the 5-hour quota. Later it added a multi-account pool (auto-switches accounts when quota runs out, with a proxy configurable per account) and "dumbing-down" detection (auto-retries when it detects a reply has been cut at 128K).
  • agy-context-unlock: A script that patches the local agy binary, raising the official 256K context cap to roughly 1M.

MIT license, free, 16 commits, written by one person.

stars followed the posts

Date11-0711-0811-0911-1011-1111-1211-1311-14
Cumulative stars23145180243277283302311

(GitHub daily star records)

Both steps line up with post times. The launch post for 11-06 brought +122 on 11-08; on 11-09 the author posted a follow-up, "No reverse proxy! No bans! ... Big update (bug fixes, simplified agy prompts, dumbing-down mitigation, multi-account import, UI polish, per-IP proxy config, etc.)", responding point by point to the previous post's requests (student accounts, multiple accounts, per-account proxies to avoid bans), and ending with another ask for a star: "Burned through over 2 billion tokens on this, so if you're interested, drop a star". The second step is +63 from 11-10.

Beyond that, reach was thin. A 11-12 X alt account reposted the forum title and got 3,499 views and 7 replies, with one commenter throwing cold water: "It's still just agy CLI, no real difference, just a new frontend." No media coverage, and it never made Trendshift's top 25. No dedicated write-ups on HN, Reddit, Bilibili or Zhihu. Stars came almost entirely from LINUX DO.

This isn't the author's first time playing this game. Their other repo, aicoding-cookbook, has 685 stars, also driven by a LINUX DO tutorial post at the end of 2025. The account has long posted Codex and Claude Code tips on the forum, with single posts pulling 1k to 4.7k views. The credibility built up on the forum is their distribution channel.

Why this week

A few things happened to line up:

  1. Plenty of people had unused quota. In November, one of the hottest LINUX DO topics was "Turkish-region 410-yuan Ultra 20x", along with a post on claiming "Google One's free 24 months of Gemini Pro". Many people bought or claimed it, then had nowhere convenient to use it.
  2. The official client was getting roasted. Around the same time, several complaint threads said agy hard-capped at 256K and got dumber after compression, and there were matching GitHub issues.
  3. Reverse proxies were being banned in large numbers. Taking subscription credentials and connecting directly to Google's endpoints (known in the scene as "reverse proxying") was getting accounts banned in batches, and some users said free Pro accounts "died the moment they were touched". The phrase "no reverse proxy, no bans" spoke directly to that fear.
  4. The DSH ecosystem was hot. A framework that only went open source in August, and Chinese developers were already hunting for ways to plug stronger models into it. Questions like "how do I use Gemini Ultra inside DSH?" were already common.

At least a dozen others were doing the same thing

ProjectLaunchedstar(11-14)Difference
NoeFabris/opencode-antigravity-auth2025-1211,041Host is OpenCode, direct OAuth connection, a reverse-proxy approach
amlyczz/dsh-agy-link2026-08-19173 (+21 the same week)Calls the same agy, launched three months earlier, English-language, no multi-account pool and no 1M unlock
AITabby/dockyard-dsh2026-0879Multi-provider account pool, not focused on Antigravity
chaos-03x/dsh-agy, LiZhenNet/dsh-antigravity, etc.2026-084–69OAuth or reverse-proxy approach
KouzakiUmi / dannndouglas's dsh-antigravity-acp2026-1010 / 6Same official ACP route, similar features, English, nobody promoted it
DylanLIiii/opencode-antigravity-bridge2026-1048Same idea, host swapped to OpenCode

The most telling row is KouzakiUmi and dannndouglas: an English plugin on the same official ACP route with similar features, sitting at 10 stars, versus this one's 6. What separated them was Chinese-language promotion, LINUX DO, and the "no bans" pitch, not the technology.

Across the whole DSH ecosystem, 311 stars is only mid-table: among DSH-related repos created after mid-October, it ranks 7 for stars gained over 9 days, while the top ones gain thousands in a single week.

Copycats have already arrived: ACP-Ant (39 stars) states "Inspired by dsh-llm-antigravity-acp" and turned the same approach into a generic OpenAI/Anthropic-compatible interface; someone made a Windows WSL version; and an account copied the whole repo wholesale.

"No bans" lasted a few days

In November, Google began detecting third-party tools by prompt signatures and returning 10 429. The author pushed an update 11-12 that scrambled the system prompt, inserted zero-width spaces inside words, and impersonated the official client's identifier during the handshake.

On Nov 11, someone on the Google developer forum asked whether another plugin of the same kind was against the rules. The official reply was blunt: don't use personal accounts with these plugins. Wrapping "agy" in a third-party tool and auto-switching accounts are both prohibited. To use Gemini in a third-party framework, get an API key from AI Studio. The multi-account pool this plugin sells on is exactly the second case.

The README's first paragraph now reads: "Google uses prompt-based detection... bans have already happened." Paid plans haven't been banned for now; bans have concentrated on promotional and giveaway plans, and those are exactly the users with unused quota. Meanwhile, a new LINUX DO thread appeared 11-13: after using dsh-plugin-bundle, "my account was temporarily banned, which plugin won't get banned?" Both promotional threads now fail to load without logging in.

If it were you

The verdict: Don't chase this project. The niche is crowded (a dozen-plus clones), it breaks the platform's terms (Google has already named it), and its lifespan depends on when Google tightens up. Followers will get fewer and fewer stars and risk a reputation for getting people banned. The part worth learning is the author's distribution rhythm: publish a research post to build readers in the community, post the open-source promo three days later, then post a "big update" three days after that, responding to replies, to ride two waves of traffic in one cycle.

Who this fits: Developers with a long posting history on Chinese developer communities like LINUX DO or V2EX, whose IDs people recognize; those who have a tool that solves a currently hot pain point and just need the first batch of stars.

Who this doesn't fit: Anyone planning yet another "plug a subscription into framework X" plugin. ACP-Ant says it was inspired by this one and got 39 stars a week, while the original author is already absorbing the backlash from bans. Also anyone with no presence in the Chinese community, hoping one post will catapult them to the top (this author has been posting tutorials on the forum since at least the end of 2025). And anyone building an English project targeting Hacker News or Reddit: this rhythm would need new channels to test.

How to do it: Find a newly open-sourced, hot host (this time DSH), look at what users have already paid for but can't use smoothly, and wire it in as a native feature of the host. Choose an integration the platform permits, though: an official API key, the platform's public extension interface, or filling gaps the host itself left (dsh-context added context visualization and got 4,000 more stars). Ship the things users care about most in one go, and ship whatever gets requested in the replies within three days.

How to get users: Post 1 is a technical research write-up that explains the pain point and what you found, with a small tool attached. Post 2 is the formal promotion, with a title that states the user's biggest fear and benefit outright, and an explicit star request at the end. Post 3 is "a big update based on your feedback", responding point by point and naming people. The README states which community it was promoted in (LINUX DO's rules require it), and if someone reposts it on X, let it spread.

When to do it: Within the first few months after the host goes open source, while discussion is still hot. DSH has been open source for three months and the open slots in its ecosystem are shrinking; when the next hot agent framework appears, start in its first week.

What would show you're wrong: ① After Google tightened up, this repo and its clones kept gaining stars and ban threads didn't multiply, meaning the platform tolerates more than expected and this lane has months left. ② You run this three-post rhythm on LINUX DO for a compliant project and it gets not even 100 stars in two weeks, meaning this time it ran on the "no bans" fear nerve, and the rhythm itself isn't that effective. ③ DSH officially integrates Gemini subscriptions, or Google opens third-party access, and this whole class of plugin has no reason to exist.

Data and sources

GitHub repo, README, commit history and daily stars (as of 11-14); stars for clones and copycat repos from GitHub (11-14). LINUX DO threads: 3117832 (11-03 research post), 3133812 (11-06 launch post), 3145154 (11-09 update post), 3150975 (11-10 Google block), 3138065, 3125733, 3135766, 3171970 (11-13 ban help request). The launch and update posts don't load without logging in now, so the body text comes from an archive and view counts are unavailable. Google developer forum "ToS clarification - dsh-antigravity-acp" (11-11 official reply). X: @leo114119 (11-12). Trendshift repositories/342222. From the outside, there's no way to tell how many stars reflect real installs or whether any were bought.

GitHub repo ↗

Research notes: competitor table, acquisition evidence, full research report
Competitors
NameWhereLaunchedScaleHow it differs from this one
NoeFabris/opencode-antigravity-authOpen source2025-12-0911,041 starHost is OpenCode, connecting directly to Cloud Code via OAuth, a reverse-proxy approach; this project's whole pitch is "no reverse proxy".
amlyczz/dsh-agy-linkOpen source2026-08-19173 stars, +7 in the last 21 daysAlso plugs the agy CLI into DSH, English-language, no community promotion, no multi-account pool, 1M unlock, or dumbing-down retry
chaos-03x/dsh-agy / LiZhenNet/dsh-antigravity / suntianc/dsh-antigravity-auth, etc.Open source2026-0828–69 starDirect OAuth credentials or reverse proxying; the ban risk is exactly the thing this project's marketing positions itself against
AITabby/dockyard-dsh / GooDAnDReaDY/dsh-subscriptionsOpen source2026-0879 / 25 starMulti-provider account pool, general-purpose, not focused on the Antigravity experience
KouzakiUmi/dsh-antigravity-acp / dannndouglas/dsh-antigravity-acpOpen source2026-1010 / 6 starSame official ACP route with similar features, but English and unpromoted; the KouzakiUmi version was named by the Google forum as not recommended
DylanLIiii/opencode-antigravity-bridgeOpen source2026-10-2348 starSame idea, host is Magpie/OpenCode
Antigravity's official desktop client and the agy CLIBig-company features2026Official GoogleThe official client hard-caps at 256K, has no context display, and weak sub-agents; the plugin exists to fix these pain points
Where users come from
  • Verified LINUX DO technical pre-launch post: 11-03 "Don't waste the Turkish-region Gemini 20x you just bought: research on Antigravity's context problem & a method to unlock one million context", 1.6k views, 15 replies, with the unlock script attached
  • Verified LINUX DO open-source promotion post: 11-06 13:59 UTC "No reverse proxy, no bans: embedding Antigravity into the DeepSeek harness via the ACP protocol" (topic 3133812), at least 7 pages of replies, closing with a star request; the 11-08 snapshot shows +122 that day
  • Verified LINUX DO update follow-up post: 11-09 08:40 UTC "dsh-llm-antigravity-acp big update" (topic 3145154), added multi-account, proxy and dumbing-down retry based on reply requests, and asked for stars again; the 11-10 snapshot shows +63
  • Verified LINUX DO reposts and word of mouth: recommended in reposts in posts 3141628, 3136801, 3104824, etc.
  • Verified X alt account repost: @leo114119 posted 11-12, 3,499 views, copying the LINUX DO title
  • Verified Author's long-term credibility on LINUX DO: @23375 has long posted Codex and Claude Code tips, with single posts pulling 1k–4.7k views; another repo, aicoding-cookbook (685 stars), was also driven by a LINUX DO tutorial post

lili-luo/dsh-plugin-bundle: why it got off the ground

Data card: GitHub, repo created 2026-11-06, by 11-14 had 311 stars and 31 forks; gained 7 over the last 288 days, with a single-day peak of +122 (11-08 snapshot). Research date 2026-11-14.

One line

This is a DeepSeek Harness (DSH) plugin bundle. The core plugin dsh-llm-antigravity-acp launches the locally installed official Antigravity CLI's agy acp, turning the Gemini 4 Argon/Carbon and Claude Opus 5.5 models in a Google AI Pro/Ultra subscription into first-tier models in DSH's model picker. A companion script patches the agy binary to unlock context from 256K to about 1M. It took off because its author (a longtime LINUX DO user, @23375) caught a timing window: the Chinese community had a stash of cheap Google subscriptions (Ultra at 20x via a Turkish-region account, Pro for 24 months via Google One promos), the official client was hard to use, and reverse proxies were getting mass-banned. The author posted "No reverse proxy, no bans" on LINUX DO, which lit the demand directly. A string of major updates followed over 3 days, then an update post drove a second wave. Nearly all the stars came from LINUX DO.

1. What it is

  • Repo: github.com/lili-luo/dsh-plugin-bundle (MIT, JavaScript/TypeScript, 16 commits, single contributor)
  • dsh-llm-antigravity-acp: talks to the official agy acp process over ACP (Agent Client Protocol). Login state stays in the official process and the system keychain; the plugin "never stores keys or forwards to another gateway." Specifically:
    • DSH's tools are handed to the model through a per-session local MCP bridge, with subagents, compaction and permissions all managed by DSH;
    • A quota "pill" next to the input box shows the weekly quota and the 5-hour quota (read from agy -p /usage);
    • Real per-step usage is read from agy's local SQLite session store and lights up DSH's context gauge;
    • Multi-account pool: each account gets its own $HOME and keychain, auto-switches when a quota runs out, and can be configured per account with proxy, weight and available models;
    • "Dumbed-down" detection: a five-dimension routing fingerprint built from gen_metadata billing data, with automatic re-answer when output is cut at 128K;
    • Anti-detection: before sending, it rewrites English sentences likely to trigger upstream feature matching, inserts zero-width spaces into words in the system prompt, and during the ACP handshake impersonates the official client identifier antigravity, with a matching User-Agent.
  • agy-context-unlock: binary patches for agy and the desktop language_server on macOS, Linux and Windows, skipping the 256K clamp and the single-message 64K input cap.
  • The README opens by admitting that Google detects via prompt fingerprinting and bans have already happened; paid plans have not been banned for now, while promo and giveaway plans are getting hit hardest (README, 11-12 commits).

2. Competitors: who else does this

"Plugging an Antigravity subscription into a third-party harness" is a crowded lane. DSH is DeepSeek's open-source agent harness released in 2026-08-13 (deepseek-ai/deepseek-harness has 280k stars, and the ecosystem list awesome-dsh-plugin has 24.6k), and someone shipped an Antigravity plugin the day after launch.

ProjectPositionLaunchedScale (GitHub API, 11-14)How it differs from this project
NoeFabris/opencode-antigravity-authOpen source (OpenCode/Magpie)2025-12-0911,041 stars, +7 in the last 35 daysHost is OpenCode, uses OAuth direct to Cloud Code, a reverse-proxy type; the ban risk is the very thing this project's pitch positions itself against
amlyczz/dsh-agy-linkOpen source (DSH)2026-08-19173 stars, +7 in the last 21 daysAlso calls the agy CLI, with Google login inside the GUI; English-only, released three months earlier, but has no multi-account pool, 1M unlock, or dumbed-down re-answer; LINUX DO users compared it to this project in threads ("pretty much the same as this one")
chaos-03x/dsh-agyOpen source2026-08-1469 starUses OAuth auth, a reverse-proxy approach
AITabby/dockyard-dshOpen source2026-08-1579 starAccount pool across several subscriptions (Codex, Antigravity, Grok), general-purpose
LiZhenNet/dsh-antigravityOpen source2026-08-1833 stars (no updates since August)Stores OAuth credentials in DSH and hits Cloud Code directly, a reverse-proxy approach
suntianc/dsh-antigravity-auth, GooDAnDReaDY/dsh-subscriptions, Jaylor-Wang/dsh-tool-antigravity, OpenSaozi/dsh-antigravityOpen source2026-08 to 094 to 28 starsAll are OAuth/reverse-proxy or multi-subscription aggregators
KouzakiUmi/dsh-antigravity-acpOpen source2026-10-1410 starAlso uses the official ACP, but reads agy's login files and runs multiple workers; a Google developer forum 11-11 reply specifically called it out, saying using a personal account with it is "not recommended"
dannndouglas/dsh-antigravity-acpOpen source2026-10-056 starAlso official ACP plus DSH tools over MCP, English-only, with no community promotion
DylanLIiii/opencode-antigravity-bridgeOpen source (Magpie)2026-10-2348 starSame idea, different host
anglee0323/agy-bridgeOpen source2026-11-060 starWraps agy acp as a local OpenAI-compatible endpoint; the README itself admits it violates the ToS
Antigravity's official desktop client and the agy CLIBig-company features2026Official GoogleUsers complain it's hard to use: hard cutoff at 256K, frequent retries, no context display, weak subagents; these are the exact pain points this plugin targets

Bottom line: this project is not first in functionality (an agy subprocess approach existed as early as August, and an ACP approach was built as early as October), but it is first in its category on stars. It gained 311 in 8 days; the closest competitor, dsh-agy-link, took three months to reach 173, and gained only 21 in the same week (our github data). Across the whole DSH ecosystem it ranks mid-tier: among DSH-related repos created after 10-15, it ranks #9 on stars gained over the last 7 days, behind ones like dsh-Go (+7 in 8,880 days) and dsh-purge (+3,130).

3. Where users come from: growth tactics

The main channel is two "open-source promotion" posts on LINUX DO, confirmed.

  • 11-03: the author first posted a technical write-up, "Don't waste the Turkish-region gemini20x you just bought: research on Antigravity's context limits & a method to unlock one million context" (linux.do/t/topic/3117832), with 1.6k views and 15 replies, and attached agy-context-unlock.zip. This post built an early audience of people frustrated that "Antigravity is terrible and context gets cut."
  • 11-06 13:59 UTC: release post, "No reverse proxy, no bans: embedding Antigravity into the DeepSeek harness via the ACP protocol" (linux.do/t/topic/3133812), tagged #open-source-promotion, ending with "if you're interested, give it a star." The Exa snapshot shows at least 7 pages of replies (20 per page, so at least 120 replies). Most replies were "urgently needed, my Haiku quota goes unused anyway," "bookmarked, will try tomorrow," with some bug reports and questions about why Pro accounts don't show Gemini 4. The repo was created the same hour; the README ends with a note saying "this project is promoted in the LINUX DO community," which LINUX DO's promotion rules require.
  • 11-09 08:40 UTC: update post, "No reverse proxy! No bans! Perfectly plugging Antigravity into the DeepSeek harness: big dsh-llm-antigravity-acp update (bug fixes, agy prompt trimming, dumbed-down mitigation, multi-account import, UI polish, per-IP proxy config, etc.)" (linux.do/t/topic/3145154). The post responds point by point to requests from the earlier thread: multi-account support for jio and student accounts, per-account proxies to avoid risk controls, and re-answering when output is dumbed down. It closes with another star request: "this took a few billion tokens too, if you're interested, give it a star."
  • Secondary spread within the site: "Is the acp call to Antigravity's gemini 3.8flash back to normal speed?" (3141628, 11-08), "How good is dsh, compared with pi" (3136801), and "[Open-source self-recommendation] DSH plugin: plain-language version" (3104824) all had users sharing or recommending this post.

The star curve lines up with the posting times (our github data, snapshot day):

Snapshot day11-0711-0811-0911-1011-1111-1211-1311-14
star23145180243277283302311

The release post brought 11-08 +122; the update post brought 11-10 +63; after the 11-12 X post, 11-13 added another +19. Trendshift counts differently and only shows +178 over 9 days, but its peak falls in the same 11-08 to 11-10 window, and it never broke into its top 25 (trendshift.io/repositories/342222).

X: small, confirmed. On 11-12 there was one Chinese X post from @leo114119, "DSH plugin share dsh-llm-antigravity-acp: no reverse proxy, no bans!...", with 3,499 views and 7 replies. The copy was lifted from the LINUX DO title, and a commenter said "it's still agy cli, no real difference, just a new front end." x-radar's local corpus turned up nothing more.

Channels not found: no media coverage, Hacker News, Reddit, Bilibili, or dedicated Zhihu write-ups turned up; the author also isn't a big X account (their GitHub profile reads "22-year-old AI product manager, job hunting, targeting Guangdong").

The author's own playbook is reusable. The author's other repo, aicoding-cookbook (685 stars), grew the same way: 2025-12-28 posted "Augment lazy-setup tutorial" on LINUX DO with the repo linked. The account has long posted Codex and Claude Code tips on LINUX DO, with individual posts often reaching 1k to 4.7k views, building up credibility. In short, the author follows a fixed pattern: publish a technical research post to build credibility and readership, then publish an open-source promotion post asking for stars.

4. Why now

  1. More people suddenly had spare subscriptions. In November the top LINUX DO topics were "Turkish-region 410-yuan Ultra 20x," with tutorials on both X and Bilibili; there were also posts like "Google One gives 24 months of Gemini Pro free (how-to), registration bot now open source." Lots of people had quota they couldn't use ("my Haiku quota goes unused anyway").
  2. The official client was widely disliked. Several complaint posts ran around the same time: agy hard-capped at 256K, dumbed-down output after compaction (3125733, 3135766), and antigravity-cli issues #1245 and #878 on GitHub.
  3. Reverse proxies were being banned. The release post opened with a screenshot of a ban: "bans have increased sharply recently." Another thread had a user saying Antigravity Tool and Sub2api "free Pro accounts die the moment you plug them in" (3138065). "No reverse proxy, no bans" spoke directly to that fear.
  4. DSH had just launched in August and the ecosystem was hot. Chinese developers were looking for ways to run stronger models inside DSH; questions like "How do I use Gemini Ultra in DSH?" (3117898) show the demand was already there.
  5. Google 11-10 started using prompt-feature detection to block third-party harnesses, directly returning 429 (3150975, the same day Gemini 4 Carbon launched). The author 11-12 added "scrambling the system prompt and inserting zero-width spaces," and fixed it right after. This kept it working when some peers broke, and it also made users more dependent on how fast it updates.

5. What the differentiation is, and whether it's why it took off

  • The positioning pitch is the main reason. Most rivals use OAuth direct or reverse proxies. This one packaged "goes through the official agy acp process, credentials stay with the official client, no token handling" as "no reverse proxy, no bans," which hit the biggest fear at the time. Technically the claim doesn't hold up: Google's forum has explicitly said wrapping agy for third-party use violates the ToS, and the README admits bans have happened. But at launch, that positioning was the selling point.
  • "Everything included" product strength is the secondary reason. The 1M context unlock, quota pill, real usage gauge, multi-account pool and dumbed-down detection are all "squeeze the subscription dry" features that LINUX DO users care most about. Few rival plugins had all of them, and the author shipped the requested additions within 3 days (v0.4.0 on 11-09).
  • Chinese-language, posted in the right community, with prior groundwork. English-language rivals (dannndouglas, KouzakiUmi, dsh-agy-link) had similar features but no community promotion, and only reached 6 to 173 stars.

So differentiation is partly the product itself, but what really decides whether it hits 8 stars in 311 days is distribution: posting in the right community, at the right moment, with the right pitch.

6. Visibility and copycats

  • Visibility: it's circulating in small circles. Two promo posts on LINUX DO plus several reposts on the forum, and one X post with 3.5k views. No media coverage, not in Trendshift's top 25, not on GitHub trending (the repo was under 60 days old, so it couldn't have made it anyway). It's open source and free, so no revenue. Also, both promo posts now return 404 to anonymous visitors (possibly changed to login-only), and they don't show up in the author's public profile topic list either.
  • Copycats: czg86389-hub/ACP-Ant (created 11-07, 39 stars) and xpeb/ACP-Ant (0 stars) both state "Inspired by dsh-llm-antigravity-acp" and generalize the same idea to OpenAI/Anthropic-compatible APIs. lgd970/dsh-llm-antigravity-acp-wsl (2 stars) is a version modified for Windows WSL. Accounts like z21100644 have cloned the whole repo. One LINUX DO user wrote: "Connected it to opencode following this guy's approach."
  • Risks: Google has identified this kind of integration, and it has banned many activity accounts. If the ACP allowlist tightens, the model list shrinks to just Gemini. Binary patches have to be redone every time agy updates. 11-13 has already posted a new thread, "...using dsh-plugin-bundle from GitHub, account briefly banned, any plugins that won't get banned?" (3171970).

7. Takeaways

  • On a hot new host (here, DSH), wire subscriptions that users have already paid for but can't use smoothly into native capability. The demand is ready-made, and users are willing to try.
  • Post a research thread first to build credibility and readers, then after three days post the open-source promo, then three days later post a follow-up about a major update based on user feedback. One cycle, two waves of traffic.
  • Titles name the biggest current fear and benefit outright ("no reverse proxy, no bans", "1M context"), and each post explicitly asks for stars at the end.
  • Risk: a project like this lives or dies on the platform's tolerance. What you can learn is the distribution rhythm, not the product itself.

8. Uncertain

  • The exact view and like counts for the two LINUX DO posts are unavailable (the posts currently return 404 to anonymous access, and the Exa snapshot has no view counts).
  • How many stars come from real installs, and whether any were bought: the GitHub stargazers API returns 404 for this repo, so there's no breakdown. Our repo's suspect field is empty.
  • No evidence found of reposting in private channels such as QQ groups, WeChat groups, or Telegram.
  • The actual scale of the bans, and whether it will be asked to take the project down.

Sources

  • Repo, commits, README: GitHub API (gh api repos/lili-luo/dsh-plugin-bundle, /commits, /readme, 11-14)
  • Daily star series: our github tables repo_day/repo_profile; data card gh_lili-luo__dsh-plugin-bundle.json
  • LINUX DO: 3133812 (launch post, 11-06), 3145154 (update post, 11-09), 3117832 (context research post, 11-03), 3141628, 3136801, 3150975, 3138065, 3125733, 3135766, 3171970, 1371911; author profile linux.do/u/23375/activity/topics (post bodies from Exa snapshots)
  • Trendshift: trendshift.io/repositories/342222
  • X: x.com/leo114119/status/2120671010215301588
  • Google developer forum ToS clarification: discuss.ai.google.dev/t/tos-clarification-dsh-antigravity-ac…
  • Scale of competitors and copycat repos: GitHub API (11-14); DSH release date: Zhihu zhuanlan.zhihu.com/p/2072331028375548274, github.com/deepseek-ai/deepseek-harness

This article was written by AI from public data and the data we collect daily. Numbers are sourced, and inferences are labeled.