Stringers
undefined-ui/second-brain-os · undefined-ui

One tweet with 500k views brought in 260 stars: how Second Brain OS turned a viral post into an "AI agent learning map" repo

What it is A free learning pack for AI engineers: agent courses, topic handbooks, curated resources, and Claude Code tools, plus a second-brain template where Claude helps you organize your Obsidian notes, and a website that draws everything as a clickable map.

Why it took off June, the author, wrote a long X post on building an AI second brain that got 9.16M views. September turned it into a repo and caught the first wave of stars. Then 11-03 posted a tweet saying "spend 15 minutes browsing this site," which got 500k views and brought in 11-05 and 11-06 stars over two days, with 260 stars total.

CHow you could follow it Stop making second-brain templates. Pick a topic nobody has mapped yet, such as a Chinese-language agent engineering learning path, and build it on the same structure: courses, handbooks, curated resources, and a clickable knowledge-graph site. Publish long tutorials first to collect bookmarks, then create the repo, and put the repo link prominently in your tweets.

Grade C: the playbook of turning a viral post into a repo, and the clickable learning-map format, are worth studying. But its stars came from an article with 9.16M views and an account with 20k followers, which followers can't reproduce. Even with that reach, 500k views only converted to about 260 stars, and the second-brain category is already crowded. What people in the niche are saying
Data (updated daily) · Repo created 2026-09-07 · 1,515 stars · 7 days +346
GitHub · stars
5001k1.5k09-2610-1610-2410-3111-081.5k
Data 2026-09-26 → 2026-11-08 (44 days, 32 observations). Points before 10-28 come from deeply / archive backfill, not every day has one

Second Brain OS is a free markdown repo: an agent course with 7 modules, 5 handbooks, a glossary, 114 curated resources, a set of Claude Code tools, and a hands-on project to build a "second brain" that AI maintains for you, plus a clickable, rotatable knowledge-graph site. It was created in Sep 7 and has reached 6 stars and 1,449 forks by Nov 250, gaining 260 in the last two days. Almost all of those stars came from the audience the author built on X. Below: what it is, where the stars came from, why the same traffic produced so few stars, and how to think about building a similar project that can earn stars.

A tweet from Nov 3: "Lock yourself away for 15 minutes"

On Nov 3, 2026, X user Yarchi (@undefinedKi, 20K followers, self-described as "AI and tech researcher, data engineer") posted a tweet of just two sentences:

"Lock yourself away for just 15 minutes and go through this site. I promise your understanding of AI agents will exceed 95% of people."

Below it was a link, secondbrainos.dev. By 11-06, the tweet had 502k views, 11k likes, and 19k bookmarks (on X, 11-06).

The next day, AI news account @DataChaz, with 180k followers, wrote a long post saying the site "turns the whole field into a map you can browse, honestly impressive" (15k views). Two other accounts, @KanikaBK and @saidul_dev, also posted introductions. The repo's stars then jumped: 11-04 on one day, 1,189,11-05 +109,11-06 +151, the highest single-day total since the repo was created (per GitHub's daily star count).

Note that the tweet linked to the site, not the repo. 19k people bookmarked it, and roughly 260 people clicked through to GitHub and starred it over two days.

What it actually is

Open secondbrainos.dev and the homepage is a spinning sphere graph: 130 pages, 60k words, 57 terms, 107 tools, and 1,236 connecting lines. Each page, term, and tool is a bubble. Click one and the map rotates to it, lighting up everything it depends on.

The repo itself is plain markdown under the MIT license. You can read it without signing up or installing anything. The README opens by listing what's inside:

  • Agent course: 7 modules, from "one prompt" to "a shipped agent," covering context, loops, when to skip expensive models, harnesses, evaluation, and deployment; 3 lessons per module, 21 pages in total;
  • 5 handbooks: knowledge graphs, model routing, harnesses, loops, and evaluation, each going one level deeper, with a hands-on project at the end of each;
  • Second-brain project: a beginner Obsidian vault with a built-in CLAUDE.md, so Claude Code can organize your notes, link them together, and answer questions about them;
  • Toolkit: a Claude Code plugin with 18 skills, 72 slash commands, and 6 sub-agents;
  • 114 curated resources: papers, repos, tools, and Obsidian plugins, with a monthly "new this month" section that says "verified at the source."

Its self-description has also changed. The repo's original tagline was "an AI second brain that maintains itself." The GitHub page now says "a guide and resource hub for AI engineers." The second brain has moved from the main attraction to one hands-on exercise inside the course.

How the stars built up: first, a long post with 9.16M views

The story starts with Jun 20, when Yarchi posted a long X article, "How to Build an AI Second Brain With Claude and Obsidian That Gets Smarter Every Day (Full Guide)." It walks you step by step through installing Claude Desktop and Obsidian, enabling plugins, and letting Claude read and write your notes vault. The opener says you can follow along even if you've never touched Claude Code or Obsidian. By 11-06 it had 9.16M views, 5,462 likes, and 20k+ bookmarks (X, 11-06). It builds on the "LLM Wiki" idea Karpathy floated in April, where an LLM maintains a markdown knowledge base for you. That was one of the hottest topics in the Claude Code crowd on X in 2026.

The timeline after that:

DateWhat happenedViews / stars
06-20Long post "Complete AI Second Brain Guide"9.16M views
09-07Repo created, turning the post into a starter vault + skills—
09-26—663 stars (first 19 days)
10-07First "Second Brain OS" launch tweet, with a site demo video8,163 views
10-11"9M people read my second-brain article, now here's a version you can click through"9,275 views
OctoberPlateau, single digits per day10-17 1,094 → 11-04 1,189
11-02"Every AI engineer needs this," linking to the repo4,209 views
11-03"Lock yourself away for 15 minutes," linking to the site502k views
11-04@DataChaz, @KanikaBK, @saidul_dev follow up with introductions15k / 1,339 / 89 views
11-05—1,298(+109)
11-06—1,449(+151)

(View counts come from the X page as read on 11-06. Star counts come from GitHub, with one daily figure starting 10-17.)

Two conversion rates are worth noting:

  • A long post with 9.16M views brought in 19 stars in the first 663 days after the repo was created, then slowly climbed to 1,100+ over the following month.
  • A tweet with 500k views and 19k bookmarks brought in about 260 stars over two days.

People on X are willing to bookmark, but less willing to take the extra step to GitHub. The tweet led people to the site, and only a small "Repo" link in the top right corner of the site pointed to the repository.

It hasn't been on Hacker News or GitHub Trending (the repo is only two months old, and the daily 151 isn't enough to get there). The fork rate is high, though: 250 forks to 1,449 stars, about 17%, which is above what a typical bookmark-style repo gets. Looks like plenty of people are pulling the vault and running it themselves.

Who it's competing with

"Obsidian + Claude Code second brain" is one of the most crowded categories on GitHub this year, nearly all of it emerging after Karpathy's LLM Wiki:

Projectstars (approx., 11-06)How it differs
khoj-ai/khoj38kA finished software product that has existed since 2021, a self-hostable AI second-brain app rather than a template
AgriciDaniel/claude-obsidian16.2kThe top player in this category, built by April on the same LLM Wiki base. It only does a self-organizing vault, with no course, and its homepage links to a paid community
breferrari/obsidian-mind5,500Long-term memory for coding agents, supporting Claude, Codex, and Gemini CLI
eugeniughelbur/obsidian-second-brain5,200Long-term memory for 8 kinds of agents, more focused on "memory"
ballred/obsidian-claude-pkm1,900Pure beginner templates, with no course and no site
A pile of LLM Wiki implementations (swarmvault, llm-wikid, memoriki, and a dozen more)100–700 eachSingle-feature tools

Second Brain OS is a later entry in this wave. Its way of avoiding direct competition was to stop calling itself "yet another second-brain template" and present itself as an agent learning path with a map, something like an awesome-list that updates plus a tutorial series. That packaging shaped whether people were willing to bookmark it, but what got people to click in the first place was the article with 9.16M views and an account with 20k followers.

If it were you

One-line verdict: the "viral post → repo" path is real, and the "draw a field as a clickable map" format is fresh. But Second Brain OS's 1,449 stars came from an article with 9.16M views and a tweet with 500k views. Converted, that's not a high rate, and the second-brain category is already saturated. It's worth learning from, but not worth copying as-is.

Who it suits: people who already have a few thousand to tens of thousands of followers on X, Jike, Xiaohongshu, or Bilibili around a technical topic and can write long tutorials that get bookmarked widely; or people with real, systematic knowledge of a field (agents, RAG, evaluation, a specific framework) who can fill dozens of pages.

Who it doesn't suit: anyone planning yet another "Obsidian + Claude second-brain template." The top one has 16k stars, and the dozen behind it are stuck in the hundreds. It also doesn't suit people with no audience who expect the repo to be found through search. This repo never relied on search or Trending for much of its traffic.

How to do it:

  • Change the topic, keep the format: don't build another second brain. Pick a field that doesn't have a "map" yet, such as a Chinese-language agent engineering path, the MCP ecosystem, or a panorama of a specific framework, and use the same structure: tiered courses, a few topic handbooks, a glossary, curated resources with a reason for each entry, and a clickable knowledge-graph site. (Inference: I didn't find a Chinese-language version of comparable completeness; not verified item by item.)
  • Write the article first, then build the repo: June, Yarchi published the long post first and September created the repo later. Use a "follow along from zero" tutorial to test whether anyone bookmarks it, and turn it into a repo only once the bookmarks pile up.
  • Copy its packaging details: the first screen of the README is a list of "what's inside" with numbers (how many modules, handbooks, and resources). A monthly "new this month" section gives people a reason to come back and share again. The spinning graph on the homepage is naturally suited to screen recordings for tweets.
  • Fill the gap it left: its biggest tweet only linked to the site. Put a prominent "Star on GitHub" button on your site's first screen and at the bottom of every page, and give both the site and repo links in the tweet.

How to get users: on X, rely on your own long posts and short tweets, then have AI news accounts like @DataChaz (with hundreds of thousands of followers) repost once. For the Chinese version, post on Jike, Juejin, V2EX, and Xiaohongshu, and on Bilibili make a video titled "Tour this map in 15 minutes." The hook should be as short as theirs: "Spend 15 minutes and understand X better than 95% of people."

Window closes: the AI agent / Claude Code learning wave is still hot, and resource-roundup repos still get bookmarked now. It closes once the main platforms ship official learning paths, or once a dozen of these "full-map" repos show up at once and attention gets split. My estimate: a few months.

What would prove this wrong: ① a similar "learning map" repo without a big account pushing it hits a thousand stars on its own. That means the format itself earns stars and distribution matters less, which makes it more worth building. ② Second Brain OS keeps gaining dozens of stars a day from GitHub search and Trending instead of the author's posts. That means it has become the default entry point for the topic, and a same-topic repo adds little. You'd have to pick a different angle. ③ The author ships a Chinese or other-language version. Then the "build it in another language" path is gone.

Data and sources

GitHub repo page, README, and daily star/fork counts (10-17 through 11-06; the September numbers come from earlier points in the same record). secondbrainos.dev homepage (11-06). The author's long post on X (06-20) and tweets (10-07, 10-11, 11-02, 11-03), plus tweets from @DataChaz, @KanikaBK, and @saidul_dev (11-04). View, like, and bookmark counts were all read at 11-06. Competitor star counts are as of 11-06; the ones marked "~" are rounded.

GitHub repo ↗

Research notes: competitor table, acquisition evidence, full research report
Competitors
NameWhereLaunchedScaleHow it differs from this one
khoj-ai/khojOpen source~2021 (1908 days)38.0k starA self-hostable, finished AI second-brain app (searches web and docs, can build agents). Not a vault template plus a course. Real software.
AgriciDaniel/claude-obsidianOpen source2026-04-0716.2k star/1.6k forkThe real leader in this category, also built on Karpathy's LLM Wiki. Its homepage links a paid skool community as the monetization path. Pure self-organizing vault, with no course or handbook layer.
breferrari/obsidian-mindOpen sourceAbout 2026-035.5k starPitches persistent memory for coding agents, across multiple agents (Claude / Codex / Gemini CLI).
eugeniughelbur/obsidian-second-brainOpen sourceAbout 2026-045.2k starPersistent memory for 8 agents. Focused on memory, not courses.
LLM Wiki group (swarmvault, llm-wikid, memoriki, and about ten others)Open sourceFrom 2026-04100-700 stars eachEach is a single-point implementation of Karpathy's LLM Wiki. None has the course + resource hub + website packaging.
Where users come from
  • 查实 X创作者爆文(作者Yarchi @undefinedKi 2026-06的second brain长文,自称900万阅读):作者10-11推'9 million people read my second brain article'(tweet 2109296112968384824);homepage字段直接指向该X文章
  • Verified X launch thread (by the author): 10-11 9M views on the launch tweet + 'I put everything... called it Second Brain OS' (tweet 2107917869363380534)
  • Verified Peer/influencer X thread amplification: @saidul_dev 2026-11-04 recommended it in a thread (tweet 2118031441862996295), posted right before the +109/+151 spike at 11-05/06
  • Verified Shareable web asset secondbrainos.dev (knowledge graph): the author spread it in multiple posts using website screenshots and links. The README's first line directs readers to "Read it on the web."

second-brain-os (undefined-ui): why it took off

What it is, in one sentence

An "AI engineer learning and resource hub" repo: a 7-module agent course, a 5-chapter handbook, a glossary, 114 curated resources, and a Claude Code toolkit (18 skills / 72 commands / 6 subagents / plugins). It also includes a "self-maintaining second brain" as a hands-on project (a starter Obsidian + Claude Code vault). Everything is pure markdown, MIT-licensed, and free. There's also an interactive site, secondbrainos.dev, that links every page, term, and tool into a graph.

Conclusion: why it took off

This is a classic "X content creator → GitHub repo" funnel. The author Yarchi (@undefinedKi, self-described as "AI & tech researcher | Data engineer") 2026-06 published a viral X long-form post, "How to Build an AI Second Brain With Claude and Obsidian" (self-reported 9M reads), which built an audience interested in "Claude Code + Obsidian second brain." In September the article was packaged into a repo. In October it expanded into an "AI agents landscape map + course," paired with secondbrainos.dev, and was pushed repeatedly through the author's and peers' X threads. Stars came from X traffic, not search or trending (trending_days are all 0, since the repo is only 60 days old, short of the 60-day threshold for trending).

Growth data

  • Created 2026-09-07; by 09-26 it had 663 stars. It hit 600+ in about the first ~19 days, riding the existing audience from June's viral post. Source: GitHub repo, repo_day.
  • October was essentially flat: 1,020 (10-12) → 1,189 (11-04), with single-digit daily gains. Source: GitHub repo, repo_day.
  • 11-05 +109, 11-06 +151 (single-day peak). Over the last 7 days, +289, about 5.8 times the +50 of the first 7 days. Status: accelerating. Source: GitHub repo, repo_profile / repo_day.
  • The surge lines up with the posts on X: @saidul_dev 2026-11-04 put out a recommendation thread ("I found a free resource... Second Brain OS, made by @undefinedKi... bookmark this one"), along with the author's own 10-11 launch post "9M reads" (tweet 2109296112968384824). Source: Jina read of the original x.com posts.
  • 250 forks, a fork/star ratio of about 17% (new repos with ≥5000 stars have a median of about 11%, so this is higher). That suggests people are actually cloning the vault to use it, not just starring it. Source: GitHub repo.

Visibility: circulating in small circles

  • No public revenue. It's a free MIT project with no in-app purchases or paywall, and the author hasn't disclosed any income. (They probably shouldn't. It's a lead-gen and personal-brand asset.)
  • HN has a lot of "second brain / LLM wiki" posts (Karpathy's LLM Wiki gist 2026-04 scored 296 points, plus several Show HN), but none of them is this repo, and it never made the HN front page. Source: hackernews library, story table.
  • Reach is concentrated in the Claude Code / AI-agent circles on X (the author's posts plus peer threads). No mainstream media or big-account features. Compared with the larger category player claude-obsidian (16.2k stars), it's still an order of magnitude behind.
  • Conclusion: it's circulating in a small circle, not yet "widely discussed."

Followers and copycats

Strictly speaking, no one is copying this specific repo. But the whole category is a crowd of repos copying each other. Since Karpathy's "LLM Wiki" pattern (2026-04), a stream of "Obsidian + Claude Code second brain" templates has appeared. second-brain-os is one of the later entries in this wave, wrapped in a "course" packaging. 250 forks are mostly people using it for themselves, not competitors.

Competitors (doing the same thing)

This is an extremely crowded space. Searching GitHub for "second brain / obsidian / claude / pkm" returns 30+ repos. The main ones:

NamePlatformLaunchedScaleHow it differs
khoj-ai/khojOpen source (web/desktop)~2021 (1908 days)38.0k starA self-hostable, finished AI second-brain app (searches web and docs, can build agents). Not a "vault template plus course"; it's real software.
AgriciDaniel/claude-obsidianOpen source (Claude + Obsidian)2026-04-0716.2k stars, 1.6k forksThe real leader of the category, also built on Karpathy's LLM Wiki. Its homepage uses a paid skool.com community as the monetization funnel. Pure "self-organizing vault" with no course or handbook layer.
breferrari/obsidian-mindOpen source~2026-035.5k starPitches persistent memory for coding agents, across multiple agents (Claude / Codex / Gemini CLI).
eugeniughelbur/obsidian-second-brainOpen source~2026-045.2k starPersistent memory for 8 agents such as Claude Code and Codex. Focused on "memory" rather than "courses."
ballred/obsidian-claude-pkmOpen source~2025-081.9k starPure starter kit. No course, no website.
LLM Wiki group (swarmvault, llm-wikid, memoriki, praneybehl, and about ten others)Open sourceFrom ¥2026-04100–700 starAll are implementations of Karpathy's LLM Wiki with single-point features. None has second-brain-os's course + resource hub + website packaging.

Differentiation, and whether it explains the breakout

  • Differentiation (real): competitors mostly offer only a self-organizing vault template. second-brain-os positions itself as a learning and reference hub: an agent-engineering course, a 5-chapter handbook, a glossary, 114 resources "curated this month and checked at the source," and an interactive site (secondbrainos.dev) that links everything into a knowledge graph. The second brain is just one hands-on project within it. That moves it from "another vault template" to an "AI agent learning path," closer to a living awesome-list plus tutorial.
  • Why it broke out: the differentiation explains why people keep it (high information density, weekly updates, a clickable site, all of which make people want to star it). But distribution is what lit the fuse: the audience built by the author's 9M-read viral post, the ongoing X launch threads, and peer reposts. In other words, the distribution strategy brings people in, and the product (the course packaging) makes them stay and star.

What others can borrow

  1. The viral post → repo funnel: first use a standalone, shareable long post (a how-to tutorial) to generate reach on X and build an audience. Then turn the content into a free MIT repo to collect stars and personal-brand value. Content first, repo second.
  2. Upgrade a "template" into a "course/hub": in a saturated template market, differentiate with a course + handbook + curated resources + a browsable site. High information density and a weekly-update promise turn one-time likes into long-term bookmarks.
  3. Ship a shareable web asset (the secondbrainos.dev knowledge graph). It's easier to screenshot and spread on X than a plain README.
  4. Use peer threads for a second spark: after launch, find a vertical "thread account" (such as @saidul_dev) and push another round to create a second peak.

Still unclear

  • "9M reads" is the author's own claim, not independently verified.
  • Attributing the 11-05/06 peak to saidul_dev's thread plus the author's own posts is an inference from timing. I couldn't get per-tweet impression or click data (X radar's local corpus doesn't contain these accounts; total=0).
  • Monetization is unclear. It's currently fully free. The author may monetize through personal brand, a future paid course, or a community. (The leading competitor claude-obsidian already uses a paid skool community, a common path in this category.) second-brain-os has no paid offering yet.
  • Retention and actual usage are unknown. Stars and forks don't equal long-term use.

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