# 1,431 stars, 230 downloads: Meldwork has six AIs argue in a group chat until they agree, but its heat was bought · GitHub open-source project

> Source: https://stringers.io/en/github/gh_Ryder-Sun__Meldwork.html (Stringers / 什么值得做, generated 2026-11-08)
> Stringers answers one question every day: what small product can one or two people build in a few months and actually make money from. Numbers come from 15 databases we collect daily, each with source and date.
> For agents: these verdicts and the underlying databases (verified revenue, App Store / Google Play charts, ad libraries, GitHub, Product Hunt…) are queryable live over MCP — tools today / hot / products / directions / direction / data. Setup: https://github.com/komako-workshop/stringers (the user logs in at stringers.io → "配置 agent" to get a personal URL). Site index: https://stringers.io/llms.txt

> It's not actually a hit: stars climbed fast, but the fork accounts are mass-registered fakes, downloads total about 230, and X and HN have zero discussion. The heat is most likely manufactured, and only auto-tracking growth aggregators picked it up.

[GitHub open-source project](https://stringers.io/en/github/index.md) · written 11-6

Ryder-Sun/Meldwork · Ryder-Sun

# 1,431 stars, 230 downloads: Meldwork has six AIs argue in a group chat until they agree, but its heat was bought

**What it is** A free Mac desktop app that puts the AI coding tools installed on your computer, such as Claude Code, Codex, Kimi, and Qwen, into one group chat, where they divide up the work and check each other's mistakes. You just set the goal and make the final calls.

**Why it blew up** It didn't really: stars climbed fast, but the fork accounts are batch-registered fakes, combined downloads are around 230, there's zero discussion on X or HN, and the heat is most likely manufactured. Only auto-tracking growth aggregator sites picked it up.

**D** **How you could follow it** Don't copy the full desktop shell; turn its only fresh idea, "cross-vendor AI peer review and sign-off," into a small plugin you can install in Claude Code or Codex, and post it with a short video showing "one model writes, another catches the real bug."

Grade D: the stars didn't come from real demand, so they don't prove the direction can earn stars. The top of the unified AI-tool-shell category already sits at 20,000 to 50,000 stars, and big vendors are folding multi-AI into their own tools. Only the small angle of "cross-vendor peer review" is left to borrow. Few people know about it yet

Data (updated daily) · Repo created 2026-07-29 · 1,468 stars · 7 days +195

GitHub · stars

Data 2026-10-09 → 2026-11-08 (31 days, 30 observations). Points before 10-28 come from deeply / archive backfill, not every day has one

A solo developer in Beijing built a Mac app that puts Claude Code, Codex, Kimi, Qwen and other AI coding tools from different vendors into one group chat, where they discuss, check each other's mistakes, and only call a job finished once everyone signs off on the same version. The repo collected 100 stars in 1,431 days and was still accelerating last week. But scroll down and the forks are almost all batch-registered fake accounts, and only about two hundred real people actually downloaded the installer. Below: what it is, where the stars came from, what's left in this space, and whether you should follow it.

### Nine rounds, six signatures

The V1.0.9 preview notes for Meldwork boast: "A real six-Agent unlimited-round discussion, converged in nine rounds, delivered with an identical hash." In other words: six AIs from different vendors each read the requirements, wrote proposals, pointed out each other's flaws, went back and forth nine rounds, and produced a file that's identical in the end, with everyone clicking "agree."

That's what it's selling. The author, Ryder Sun, works at an AI research institute in Beijing's Zhongguancun. The repo was created 2026-07-29, licensed Apache-2.0, free, with no paid tier at all.

### What it actually is

A desktop app (built with Electron) that only supports Apple silicon Macs. It pulls in whichever AI command-line tools you have installed locally. The directory lists 13: Claude Code, Codex, Gemini CLI, Kimi Code, Qwen Code, OpenCode, OpenClaw, Hermes, plus domestic tools like WorkBuddy, Zcode, and MiMo Code. You set goals inside it, grant permissions (which directories it can read, whether it can go online), make decisions at key points, and let them divide up the work among themselves in the group.

Beyond that, it can plug the local Obsidian notes, Feishu and DingTalk command-line tools in as knowledge sources, and every step's process and output is logged locally. Looking at the tool list and knowledge sources, it's clearly built for Chinese users.

The engineering effort is real: 294 commits, V1.0.9 says 1,700 desktop-side and 379 frontend tests; the README is extremely detailed, even listing which tool's auth will fail and which gateway turns "stop" into "tool call".

The weak spots are also in the README: it only supports M-series Macs; the installer isn't notarized by Apple, so on first launch you have to go to System Settings and click "Open Anyway"; having a command-line tool installed doesn't mean it can connect to a model, and OpenClaw, Zcode, Gemini, Qwen and several others have auth failures.

### Where the stars come from: a crowd of faceless accounts

Look at the numbers first (GitHub daily star and fork counts):

| Date | star | fork |
|---|---|---|
| 10-16 | 852 | 2 |
| 10-19 | 1,056 | 2 |
| 10-22 | 1,100 | 11 |
| 10-24 | 1,084 | 23 |
| 10-31 | 1,213 | 70 |
| 11-06 | 1,431 | 95 |

Two things are off. First, at 10-16, the repo had 852 stars but only 2 forks. In a normally popular open-source project, stars and forks run at roughly ten to one. After that, forks suddenly climbed steadily by 3 to 9 a day. Second, from 10-22 to 10-24, stars dropped from 1,100 back to 1,084. When GitHub bans junk accounts, the stars those accounts gave disappear with them, and the curve falls back like this.

Next, who's doing the forking. Pulling the earliest 100 forks by time (GitHub, 11-06), the usernames look like this: BettyOgdencoreytobyt31, Zaracarmenforster1998, GeorgiaJeanninajeremyj16, argots64today, seaward95twins, mayday-teals-1v; the most recent ones include gears-sparky2s, kitties-firs6o, baffle-ageless-0f. They show up in batches (08-13 on one day with 8 of them, and 3 to 9 per day in late October), and never touch anything again after forking. Spot-checking a few: some have already been banned; the rest were all registered within the last two or three months, with 0 following and 0 followers, and bios that are template sentences like "Electrician. baking, cycling, and too much coffee." These same accounts also star and fork a batch of unrelated small Chinese repos, and the lists overlap heavily. This is the typical signature of a star-farming service in China.

Finally, checking whether anyone is actually using it:

- 10 prerelease installers, with DMG and ZIP downloads **totaling roughly 230** , and the most downloaded V1.0.9 DMG got just 37 (GitHub Releases, 11-06). That's an order of magnitude below the 1,431 stars.

- Of 63 issues and PRs, 62 were opened by the author; the only outsider was a search API company pitching its own plugin. Only 8 people watch the repo.

- The author posted it on Product Hunt themselves. It didn't make the homepage, got 2 votes, and ranked #150 that day.

- In the nearly 90 days, not a single post about it turns up on X, and nothing on Hacker News. The biggest single day was 10-11 with +95 stars, and no post, article or repost can be matched to that day.

The only places that mention it are one Reddit post (titled "1.3k stars", poster unverified) and a set of aggregator sites that automatically scrape GitHub growth rates. They see stars rising fast and list it automatically; one shows "+399.7% in 30 days".

To be clear: GitHub no longer lets outsiders pull the list of users who starred a repo, so I did not verify the stars one by one. Calling them bought is an inference drawn from three things together: the fake fork accounts, the download numbers, and zero external discussion. All three point the same way. Also, the repo has been up for 60 days and has never appeared on GitHub trending. The inflated numbers come in small, steady daily amounts, enough to make aggregators show "fast growth", but not enough to reach the trending threshold.

### Who it's competing with: this lane was already full a year ago

"Putting every AI coding tool into one desktop shell" is not a new idea. The projects below came earlier and are bigger (GitHub stars, 11-06):

| Project | Launched | Scale | How it differs from Meldwork |
|---|---|---|---|
| AionUi | 2025-08 | 34.1k star | Also puts 20+ AI command-line tools in one interface, available on Win/Mac/Linux, a year earlier |
| Multica | 2026-01 | 55.1k star | A human and AI team, dispatching work on a kanban board |
| Vibe Kanban | 2025-06 | 28.6k star | A kanban that manages each coding AI's own branches, but doesn't handle discussion between AIs |
| Paseo | 2025-10 | 23.3k star | Orchestrates multiple coding AIs, remote-controllable from a phone |
| Microsoft Magentic-UI | 2025-05 | 10.1k star | Multi-AI with a human in the loop, but uses its own AIs and doesn't connect third-party tools |
| Claude Squad | 2025-03 | 8.7k star | Multiple AIs side by side in a terminal, no collaboration |
| Emdash | 2025-08 | 6.2k star | A dev environment for parallel coding AIs, backed by YC |

Also, Claude Code has its own subagents and multi-agent teams, and Codex can run several tasks at once. The big companies have built "multi-AI" into their own tools.

Where Meldwork is truly different is **cross-vendor** : it lets AIs from different companies review each other and co-sign the same version. The top players mainly push "run in parallel" and "dispatch work", not "catch each other's mistakes". But there is currently no user evidence that anyone is paying for this difference. The stars didn't come from it.

### If it were you

**Verdict** : D. Worth knowing about, but I wouldn't advise copying it. Its stars were not pulled in by real demand, so they prove nothing about whether this direction can earn stars. And the "unified AI tool shell" lane it sits in is already led by projects with 20,000 to 50,000 stars, while the big companies are folding these features into their own products.

**Two things worth remembering from it** :

1. An idea: "AIs from different vendors review and co-sign each other's work". The leading products haven't made this their main pitch.

2. A way to spot fakes: when judging whether a repo is really hot, don't look only at stars. Check the download counts on Releases, check whether the people forking have avatars and a history, and check whether the issues are all opened by the author. It takes three minutes to tell real from fake.

**If you still want stars in this space** : don't build another full desktop shell. Make "cross-vendor review" a small thing instead, such as a plugin or skill that installs into Claude Code or Codex: once code is written, it automatically asks an AI from the other vendor to review it, and it only commits if both agree. Keep it small, installable with one command, and record a 30-second demo video of "Claude writes it, Codex catches the bug". That is far more realistic than trying to match AionUi feature for feature. Note that the Claude Code and Codex ecosystems already have people building similar "have another model double-check it" plugins, so search that space before you start.

**Who it suits** : developers who use two or more AI coding tools every day and have actually been burned by "one AI writes its own code and reviews it"; people who can post a solid demo on X, Juejin or Jike.

**Who it doesn't suit** : anyone who wants to build a full-featured desktop app to go head-to-head with projects with tens of thousands of stars; anyone who has no posting channels and is counting on organic GitHub traffic; anyone who wants to start by buying stars. This project is the example: it bought 1,400 stars and got two hundred downloads and zero discussion in return.

**How to get users** : a short screen recording that shows just one thing: code written by one AI, and another AI catching a real bug on the spot. Post on X and Hacker News first (in English), then post the Chinese version on Juejin, V2EX and Jike. Put the video and a one-line install command on the first screen of the README.

**When to move** : the sooner the better, ideally before early 2027. Tools like Claude Code and Codex update very fast. The day the vendors ship a built-in "have another model review it" feature, this gap closes.

**Signs you've misread this** : ① Meldwork's downloads climb to several thousand within a month or two and outsiders start opening issues. That would mean real users exist, and the cross-vendor group-chat format has more demand than I estimated here. ② Top projects like AionUi or Multica make "multi-AI cross-review and co-sign" a headline feature and their stars visibly rise. That would mean the demand is real, but the window for small teams closes with it. ③ Someone reaches a thousand genuine stars within two weeks with a small plugin-style "cross-model review" tool. That would mean the path above works, and you should move faster.

### Data and sources

GitHub: the Ryder-Sun/Meldwork repo page, README, V1.0.9 release notes, Releases download counts, fork list (earliest 100 and latest 15), issue list, and some fork account profiles (11-06 retrieved); daily stars/forks (10-16 to 11-06). Competitor stars: each project's GitHub page (11-06). Product Hunt: hunted.space/product/meldwork. llmrepos.com (+399.7% in 30 days). Searches on X for the last 90 days and on Hacker News returned no results. Reddit r/BestGitHubRepos post body and poster not verified. Where it says "inference" or "unverified", that is what it is.

[GitHub repo ↗](https://github.com/Ryder-Sun/Meldwork)

**Research notes: competitor table, acquisition evidence, full research report**

Competitors

| Name | Where | Launched | Scale | How it differs from this one |
|---|---|---|---|---|
| AionUi | Open source | 2025-08 | 34.1k star | Cowork, a desktop that similarly unifies 20+ CLI agents, cross-platform, a year earlier and two orders of magnitude bigger. Meldwork adds automatic discussion between agents and cross-review with co-signing. |
| Multica | Open source | 2026-01 | 55.1k star | Human-and-agent teams with kanban dispatch. Meldwork is group-chat-style discussion. |
| Paseo | Open source | 2025-10 | 23.3k star | Multi-coding-agent orchestration with phone remote control, leaning toward coding. |
| Vibe Kanban | Open source | 2025-06 | 28.6k star | A kanban managing multiple coding-agent worktrees, with no discussion between agents. |
| Claude Squad | Open source | 2025-03 | 8.7k star | Parallel multi-agents in a terminal, no collaboration. |
| Emdash | Open source | 2025-08 | 6.2k star,YC W26 | A dev environment for parallel coding agents, funded. |
| Microsoft Magentic-UI | Open source | 2025-05 | 10.1k star | Multi-agent with a human in the loop, but uses built-in agents and doesn't connect third-party CLIs. |
| Claude Code subagents/agent teams, Codex multi-task. | Big-company features | 2025-2026 | Built in | Multi-agent within a single vendor; Meldwork's pitch is cross-vendor. |

Where users come from

- **Confirmed** **Starred/forked in bulk** : the earliest 100 forks have generated usernames (BettyOgdencoreytobyt31, argots64today, etc.), 0 followers, appear in batches by day, some accounts already banned, and the same batch also forked/starred a string of unrelated small Chinese repos. Stars went 10-22→10-24, then fell back by 16.

- **Confirmed** **Product Hunt** : the author hunted it themselves, got 2 votes, wasn't featured, ranked #150 that day.

- Inference **Reddit r/BestGitHubRepos** : one post title cites 1.3k stars, poster unverified.

- **Confirmed** **Automatic listing by GitHub aggregators** : listed by llmrepos, skillsllm, agentfilter, airanks, reputagent and others.

## Ryder-Sun/Meldwork research report (2026-11-06)

### One line

Meldwork is an Electron desktop app for macOS (Apple silicon) that pulls the agent CLIs installed on your machine (Claude Code, Codex, Gemini CLI, Kimi Code, Qwen Code, OpenCode, Hermes, OpenClaw and 13 others) into one "group chat", where they discuss, divide up work and review each other automatically. The user only sets goals, grants permissions and makes key decisions. The author is Ryder Sun, an individual developer affiliated with the Beijing Zhongguancun Academy of AI. Apache-2.0, free, no paid tier.

### Verdict: it didn't take off; most of the 1.4k stars look bought

- The reason it was surfaced: "+7 stars in the last 241 days, 7 times the previous 2.7 days; forks went from single digits to 95." On checking, **the forks are actually the clearest sign of inflation** , and the stars very likely came from the same source.

- Real usage signals are weak: 10 prerelease DMG/ZIP downloads **totaling roughly 230** (V1.0.9's DMG 37, V1.0.8's 28, and each other version in single digits to a dozen or so; GitHub Releases API, 2026-11-06), an order of magnitude below the 1,443 stars.

- Of the 63 issues/PRs, 62 were opened by the author. The only outsider was Parallel (a search API vendor) pitching its own MCP (#2026-10-20 "Proposal: keyless web knowledge search with Parallel Search MCP"). Only 8 watchers.

- Product Hunt: the author hunted it themselves, it wasn't featured, got 2 votes and 1 comments, and ranked #150 that day (hunted.space/product/meldwork).

- X local corpus (x-radar, last 90 days) returned 0 results for "Meldwork"; HN Algolia has no relevant posts. The only hits are one r/BestGitHubRepos post (title includes "1.3k stars", looks auto-scraped or self-posted; reddit body not retrievable, unverified) and a batch of GitHub aggregator sites (llmrepos, skillsllm, agentfilter, airanks, reputagent), all auto-indexed.

### Evidence of inflated numbers (why we say the stars/forks were bought)

1. **The fork accounts are an account farm.** Pulled the earliest 100 forks (GitHub API /forks?sort=oldest):
    - The usernames are typically generated: BettyOgdencoreytobyt31, Zaracarmenforster1998, Maltzhobsonjordanj63, GeorgiaJeanninajeremyj16, HobartKittyStoweelmerme, crullerrampage4v, argots64today, seaward95twins, mayday-teals-1v, reviserheir2v...
    - They show up in batches: 2026-08-13 in one day, 8 of them seven, 08-15/16 three, 09-17 ... 10-19 to 10-31 per day, 3–9 per day; every fork has 0 stars and no pushes after forking.
    - Spot check: BettyOgden…, justishaanagarwal, jqzheng2 are already deleted or suspended (API returns empty); crullerrampage4v (registered 2026-09), argots64today (registered 2026-08), seaward95twins (registered 2026-10-13) each have 0 following, 0 followers, and templated bios: "Electrician. baking, cycling, and too much coffee." / "Just a software engineer who enjoys kayaking and gardening."
    - These accounts fork/star the same batch of small Chinese repos: Trace, remoteai, BlueFatFish, MasterAgent, dsh-image-gen, Deepscient, axuse, spec-harness, TokenBar, flybrainlabs/miner, a run of "mcd-*" (McDonald's deals) repos... The star lists of three of the accounts overlap heavily. That's the typical "client list" of Chinese GitHub star-farming services.

2. **The star curve and fork curve decouple, then move in sync.** At 10-16, 852 stars against only 2 forks (real popular repos usually sit within 10:1 of each other on star:fork ratio); after that forks climb steadily at +3~9 per day, which lines up with the farm accounts above. Stars fell from 1,100 to 1,084 between 10-22 and 10-24 (this repo's card daily). GitHub purges junk accounts and stars drop when it does, which matches the forks being deleted.

3. **The single-day peak matches no external event.** The highest day, +95 on 2026-10-11 (card max_day), has no posts, press, or X discussion from that day. llmrepos logged +399.7% over 30 days (about 285 → 1,420).

4. **The author's other 18 repos sit at single digits up to 28 stars** (Realm 28, EvoLabeler 19, the rest 2–11), with no follower base that would bring traffic (followers 20).

5. Even after 60 days of tracking it has never made trending (card trending_days_any=0). Star inflation here is small amounts added steadily each day, just enough to show as "fast-growing" on aggregator sites, but never enough to clear the trending threshold.

Note: we can't get the stargazer list (GitHub now requires login to list stargazers, and our token lacks the scope), so we did not check star-by-star whether the stars were bought. The judgment rests on the fork farm + download counts + zero external discussion, three signals pointing the same way.

### The product itself (this part is real)

- The engineering effort is real: 294 commits, V1.0.9 claims 1,700 desktop and 379 frontend tests; the README is very detailed (Run Ledger, Human Gate, auth pitfalls for each vendor's CLI, and the Magpie gateway bug that rewrote stop into tool_calls are all documented).

- The core pitch isn't "run multiple coding agents in parallel" but **letting agents from different vendors join the same group chat, review each other, and sign off on the same delivered version** ("six agents discussed in unlimited rounds, converged after 9 rounds, delivered hash matches"). It also supports local Obsidian and Feishu/DingTalk CLI as knowledge sources, and the directory includes domestic CLIs like WorkBuddy, Zcode, MiMo Code, and Kimi Code. It's clearly built for Chinese users.

- Weak points: Apple silicon Mac only; not notarized, so on first launch you have to click "Open Anyway"; installing a CLI doesn't mean it can connect to a model, and the README itself lists auth failures for several vendors including OpenClaw, Zcode, Gemini, and Qwen.

### Competitors

| Name | Form | Launched | Scale (GitHub API, 2026-11-06) | How it differs from Meldwork |
|---|---|---|---|---|
| AionUi(iOfficeAI) | Open-source desktop, Win/Mac/Linux | 2025-08 | 34.1k star / 3.6k fork | Also packs OpenClaw, Hermes, Claude Code, Codex and 20+ other CLIs into one "Cowork" interface. It's earlier, cross-platform, and two orders of magnitude bigger. Meldwork's differentiator is the layer above: multi-agent auto-discussion and peer review. |
| Multica | Open-source, self-hostable | 2026-01 | 55.1k star | "People and agents as one team", task-board style assignment; Meldwork is group-chat style discussion |
| Paseo | Open-source, desktop + mobile | 2025-10 | 23.3k star | Multi-coding-agent orchestration, phone remote control; focused on coding |
| Vibe Kanban(Bloop) | Open source | 2025-06 | 28.6k star | Kanban that manages worktrees for multiple coding agents; no agent-to-agent discussion |
| Claude Squad | Open-source TUI | 2025-03 | 8.7k star | Opens multiple agents in parallel in the terminal; no collaboration |
| Emdash(YC W26) | Open-source ADE | 2025-08 | 6.2k star | A dev environment for parallel coding agents, funded. |
| Crystal → Nimbalyst | Open-source desktop | 2025-06 | 3.1k star | Parallel Claude/Codex sessions + git worktree |
| Microsoft Magentic-UI | Open source | 2025-05 | 10.1k star | Human-in-the-loop multi-agent browser/filesystem agent; brings its own agent, doesn't plug into third-party CLIs |
| Claude Code subagents / agent teams, Codex multitasking | Big-company features | 2025–2026 | Built in | Multi-agent within a single vendor; Meldwork's pitch is cross-vendor |

Verdict: this niche (a unified shell/orchestrator for local CLI agents) has been crowded for 2025 years, with AionUi, Multica, Paseo, and Vibe Kanban leading at tens of thousands of stars. Meldwork entered a year late. Its differentiator ("cross-vendor agent group chat, peer review, and done only when the delivered version is consistent") is interesting, but there is no user evidence yet that anyone is buying it.

### Growth channels

| Channel | Evidence | Confirmed? |
|---|---|---|
| Star/fork boosting (Chinese star-farming service) | The earliest 100 forks are almost all generated usernames, 0 followers, appearing in batches, some already banned; the same accounts also fork/star a run of unrelated small Chinese repos | Yes (fork part confirmed; star part inferred) |
| Product Hunt self-launch | Author self-hunted, 2 upvotes, not featured | Yes, but ineffective |
| Reddit r/BestGitHubRepos | One post, title includes 1.3k stars, body could not be retrieved | Poster not verified |
| GitHub aggregators/directories auto-indexed | llmrepos, skillsllm, agentfilter, airanks, reputagent, opensiro/vsm-harness-index review PR | Yes (passive: the inflated stars got it indexed) |
| X / HN / media | x-radar 0 posts, none on HN | None |

### Visibility

Hardly anyone knows about it yet. No revenue (free and open-source), no press, no X discussion, about two hundred real downloads. The star count is cited by aggregators, but no one is talking about it.

### Has anyone copied it

None. If anything, it's a latecomer in an already crowded niche.

### Takeaways

- A differentiation angle worth borrowing: stop building "yet another shell that runs coding agents in parallel" and build "cross-vendor agent peer review/sign-off" (a task is complete only when models from different vendors agree on the same delivered version). The top products don't lead with this yet.

- Adapting to domestic CLIs (Kimi Code, Qwen Code, MiMo, WorkBuddy, Zcode) and Feishu/DingTalk knowledge sources is an open gap beyond AionUi.

- Cautionary tale: star farming can get a repo into aggregators, but it won't reach trending or bring downloads. Download counts (Releases download_count) are the fastest way to spot inflated stars.

### Uncertain

- We did not get the stargazer list, so whether a large share of stars was bought was not checked star by star. It is inferred from the fork farm and download counts.

- The author and engagement numbers for the r/BestGitHubRepos post are unverified.

- No evidence found of promotion through WeChat groups, Xiaohongshu, Jike, or other domestic channels (the README has no group QR code).

- Download counts only cover GitHub Releases; the number of people running it from source is unknown.

### Sources

- Data card /home/ljr/fanout/why/cards/gh_Ryder-Sun__Meldwork.json (daily star/fork, max_day 10-11 +95, trending 0 days)

- GitHub API: repos/Ryder-Sun/Meldwork, /releases, /forks?sort=oldest, /issues?state=all, users/Ryder-Sun, users/{fork account}, /starred (2026-11-06 fetched)

- README:[github.com/Ryder-Sun/Meldwork](https://github.com/Ryder-Sun/Meldwork)

- [llmrepos.com/repos/Ryder-Sun/Meldwork](https://llmrepos.com/repos/Ryder-Sun/Meldwork) (30 days +399.7%)

- [hunted.space/product/meldwork](https://hunted.space/product/meldwork) (PH 2 votes, ranked #150)

- x-radar search for "Meldwork" over the last 90 days returned 0 posts; HN Algolia has none relevant

- Competitor stars: GitHub API (iOfficeAI/AionUi, multica-ai/multica, getpaseo/paseo, BloopAI/vibe-kanban, smtg-ai/claude-squad, generalaction/emdash, stravu/crystal, microsoft/magentic-ui)

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