Google released a "self-improving agent harness" that gained 10k stars in two days: Harness² runs on the brand and the trend, not the method

Harness² is an open-source framework Google's research team released with a paper, letting agents revise peripheral settings like the system prompt, memory and tool descriptions on each new task. It reached 22,804 stars in 31 days, but many projects share the same idea, most stalling at a few hundred to a thousand-plus stars. What set it apart was Google's name, "harness," the hottest term of the month, and a cluster of X big-account reposts on Oct 18. You can't borrow those three things; what you can borrow is how it packaged the paper's code.

The Oct 18 morning post

Oct 2026 18 09:39 (UTC): Akshay Pachaar, who does AI explainers on X, posted: "Google just open-sourced Harness². (turn any harness into a self-improving system)" He then explained it plainly: the harness is the layer around the model (system prompts, tools, memory, skills, subagents). Until now a person designed it once and every task used that same setup. Harness² lets the agent modify it for each new task on its own, without touching the model weights.

The post later reached about 759k views, 7.5K likes and 1K reposts. An hour-plus earlier, 08:15, MarkTechPost had published an intro article. The next day, Chubby (@kimmonismus) shared a 47-second video (121k views). JosephZhou (@openmys) said he had already plugged it into his product JEV and his visual test scores went up (183k views). Phil Schmid, developer relations at Google DeepMind, also posted a breakdown of the workflow. X generated a trending topic page for it titled "Google Open-Sources Harness² for Self-Improving AI Agents".

Here's how the repo's star count moved (GitHub daily stars):

The paper went up on arXiv and Hugging Face Papers on Oct 14, but by 17 it had only 320 stars. The real growth came in the three days after the big accounts reposted.

What it actually is

In one sentence: you already have a coding agent (it defaults to OpenCode and also supports Codex), and Harness² wraps around it and adjusts that outer layer of settings to suit the task in front of it.

It exposes 8 editable components: system prompts, guardrails, memory, tool descriptions, subagents, skills, scripts and plugins, all as files you can edit directly. For each task it runs a loop of "propose a change, try several variants on the same task, compare how those runs differ, then compose a better version" (called Propose–Probe–Compose in the README). No ground-truth answer is required. After finishing a task, it saves the chosen settings and the lessons that held up across several runs, and the next task picks up from those notes.

The paper's numbers: with a single round of changes on GLM-5 and Gemini 3.5 Flash, WorkBuddy-Bench rose by up to 11.5 points, JobBench by 4.5 points, and the LAB pass rate by 11.8 percentage points. The repo also ships a demo that needs no model key (one command: harness2-demo) and a GIF of the install process.

Why this one

The name rode a trend. In Oct 2026, "harness engineering" was one of the hottest terms in AI circles on X. Two related trending topics also ran at the time: "AI Builders Embrace Harness Engineering for Reliable Agents" with about 1.5K posts, and "AI Engineering Shifts to Harnesses and Loops Beyond Prompts" with about 1K posts. The HN thread "Harness Engineering 101" reached 132 points. Everyone was talking about how to tune harnesses, and a project where "the harness improves itself" fit the next step. Calling it simply Harness, with a "²" added, made it instantly clear which topic it belonged to.

Google's brand. Media headlines almost all used the same line: "Google open-sources self-improving agents". But the brand alone wasn't enough: under the same google-research account, the similar projects rrsi had only 1,725 stars, envharness 676 stars and veriharness 82 stars. They launched without catching the trend, and no big accounts reposted them.

A quotable line and easy-to-share visuals. "turn any harness into a self-improving system" and "get stronger without changing weights", plus a flow diagram and a set of score-gain numbers, were all ready for big accounts to pick up. It connects directly to OpenCode and Codex, so it reads as "something I could use to improve my own agent" rather than yet another paper. That's also why JEV could announce "already integrated" the next day.

Media relay. After MarkTechPost, datastudios, flowtivity, wavect, Medium and several YouTube explainer videos followed. In the Chinese-language sphere, 36氪 published two pieces in Oct 19 36 (one was a hands-on test of Jev for domestic developers), and Tencent News, Sohu and Zhihu also covered it, and Baidu Baike created an entry. There were also posts on Reddit's r/LocalLLaMA. Hacker News didn't really help: someone submitted the link in Oct 19, and it got 81 points and 19 comments.

It never appeared on GitHub trending on any day. Nearly all of those 20k+ stars came from traffic off the platform.

Lots of people looking, few using it

Stars rose fast, but the repo itself barely changed. Between Oct 17 and Nov 2 the main branch had no new commits, and community PRs piled up until Nov 2, when a batch was merged at once. Much of the issue tracker consists of external bug-fix PRs (#145 through #193), and I infer many were AI-generated. Some people reported that the k≥2 demo doesn't run on Windows (#151, #185).

The most telling is issue #149 from Oct 28, titled "How should Harness² be deployed in production without running Propose–Probe–Compose for every task?" The person asking did the math: a production agent receives 1,000 tasks a day, and running several candidate variants per task is too much for latency and inference cost. They also noted that neither the paper nor the code has a mechanism for merging what was improved on a single task back into the base setup. Running it also requires Vertex AI and substantial API spend. So the number of people actually using it is probably small.

Stars are already slowing: over the last 7 days +1,526, over the first 7 days +3,445, and on Nov 6 alone +165.

Who else is doing the same thing

On method, Harness² emphasizes "at deployment time, on unseen tasks, without a ground-truth answer, it can still improve, plus a cross-task experience layer." That's a distinction in the paper, but almost no one mentions it in the repost copy, and ordinary readers can't tell them apart. Meta-Harness did nearly the same thing half a year earlier, with a tenth or less of the attention.

Some things grew out of it: JEV integrated it into its own product to ride the wave; a community member built a Rust port, harnessmith, with a web interface and support for local models (issue #194, Nov 5); Ken Huang wrapped it as an agent skill and wrote up what it costs to run; someone proposed in issue #178 making it a skill; and the community is adding Claude Code support (#177). No repo named after Harness² has grown on its own.

If it were you

Verdict: Don't expect to copy the 20k stars. That came from Google's name, the trend, and big accounts all at once, and you won't get any of those. What you can do is build the pieces it left unfinished, and borrow its method of packaging paper code. Realistic expectations: a few hundred to a thousand or two stars.

Who it's for: developers already tuning the harnesses of Claude Code, Codex and similar agents, who know which step is the most painful; researchers with their own papers or research code who want more people to see it.

Who it's not for: anyone building yet another "general self-improving agent framework" to go head-to-head with Meta-Harness, AutoHarness or Harness²; anyone without big-account reach who's counting on method novelty to drive stars.

How to do it:

• Fill its production gap. Issue #149 spells out the ready-made need: build a lightweight tool that keeps running online, picks failed tasks offline to improve, and merges back into the base setup only after validation, reading directly from Claude Code or Codex run logs, without depending on Vertex. The repo's first sentence already states it addresses the difficulty of shipping Harness² to production.
• Switch the ecosystem. Build a slimmed-down version that only supports Claude Code and only touches skills and CLAUDE.md; or a version that runs on local models and Windows and installs in ten minutes. harnessmith is already doing Rust plus a web UI, so you'd need to move fast.
• Borrow the packaging for your own project. Anchor the name to the hottest term of the moment; prepare a demo that needs no key and runs with one command; put a flow diagram, a set of before-and-after numbers and one line people can repost right at the top of the README.

How to get users: reach out directly to accounts that cover agent architecture, like Akshay Pachaar, Chubby and Phil Schmid, with one diagram and a set of numbers; in Harness²'s issue tracker, r/LocalLLaMA, and Chinese platforms like Zhihu and WeChat Official Accounts, use "production-ready Harness²" or "Claude Code edition" as the second half of your headline. HN has already shown it doesn't do much.

When the window was: while the word "harness" was still hot, meaning before the end of November. Daily additions have already dropped from 6,000 to 165, and the topic is fading (inferred).

What would show you read it wrong: ① Google quickly ships an official production deployment path or Claude Code support, which closes the gap-filling route; ② a port like harnessmith is still at a few dozen stars a month later, showing people are just watching, not actually wanting to use it; ③ conversely, if a similar project without big-lab backing gains 5,000 stars on its own before December, that means real demand exists in this space and it's worth investing in more seriously.

Data and sources: GitHub repo page, README and issues #149, #151, #177, #178, #185, #194 (11-06); daily star counts (10-17 to 11-06); X posts from @akshay_pachaar (10-18), @kimmonismus, @openmys, @_philschmid (10-19) and the X trending topic page; MarkTechPost (10-18); 36氪 and Tencent News (36, 10-19); Hacker News submission (10-19,81 points); arXiv 2610.14224; competitors' GitHub pages (11-06). Whether Google's official account and the authors posted is unverified; I did not obtain the specific heat levels on Reddit and YouTube.