One person, 245k lines of AI-written Rust: how LayerFS got 2,700 stars in two weeks off DeepSeek Harness
What it is A filesystem for AI agents: every time an agent runs a command, it mounts a full copy of the project. No copying needed, it auto-saves on finish, and supports branching, rollback, and merging.
Why it took off The freshly hyped DeepSeek Harness was missing a storage layer, and this filled the gap. The author ran a ten-day countdown in Chinese telling a personal story, then posted an English launch thread with 10 hard numbers (160k views) and a test table that also listed the losses. Rust accounts, a French tech account, and Hacker News amplified it, and a 999-yuan airdrop from DeepSeek's operations team brought a second wave.
BHow you could play it Don't build another agent filesystem. Copy the playbook: find another missing layer for the hot agent framework (secrets, network isolation, metering, locking, observability), or build a crash-resistant, framework-agnostic version.
- Data (updated daily) · Repo created 2026-08-10 · 2,701 stars · 7 days +106
GitHub · stars Data 2026-10-09 → 2026-11-08 (31 days, 31 observations). Points before 10-28 come from deeply / archive backfill, not every day has one
LayerFS is a filesystem for AI agents: every time an agent runs a command, it mounts a complete, writable copy of the project, auto-saves on finish, and supports branching, rollback, and merging. The author is an indie developer based in China. The repo hit 2,697 stars in 88 days (GitHub, 11-06), and more than half of those came in the five days from October 19 to 23. The playbook is clear: build the layer a freshly hyped platform lacks, back it with a table of hard numbers, and add a ten-day countdown and a broke-developer story. Below: what it is, where the stars came from, who's competing for the same attention, and whether you can copy the approach.
The post from October 21 at 8 p.m.
On October 21 of 2026, at 8 p.m. Beijing time, the X account @yifanxu_ephai posted an English thread:
LayerFS v1.0.0 is out 🎉 Open-source (MIT) Recursive filesystem for AI agents.
It listed 10 "core ideas," one per line, almost each with a number: "10 copies take up the space of 0.31," "installing deps takes about 5 minutes, mounting takes 0.05 seconds." The last line was "Watch the video below, and have Fun!!!", attached to a purpose-made launch video.
The thread got 1,297 likes and 162k views. The repo gained 484 stars the next day and 452 the day after (GitHub daily star counts).
The poster, Yifan Xu, lists a CS background from the University of Toronto, a dropped-out AI master's at NTU Singapore, and currently lives in China. He has 7,139 followers on X (11-06). In his Chinese posts he's described his situation: a year and a half with no income, living with his parents, and getting chewed out by an investor half a year ago. In October 28 he posted again:
I opened my account and found an airdrop of 999 yuan from a DeepSeek operations girl (because the dsh-layerfs plugin I built got noticed). Thinking back to earlier this year, after leaving my startup I self-funded a multi-agent harness. Running it on the cheapest MiniMax API I still burned over a hundred dollars a day……
That post got 122k views, and the repo gained 288 stars that day.
What problem it actually solves
You run five Claude Code or DeepSeek Harness agents on the same project, and each needs its own copy or they step on each other. The usual fix is git worktree, but a worktree only covers source code: node_modules and build outputs have to be reinstalled for every copy. And if something breaks three steps back, there's no ready-made save point to return to.
LayerFS works like this:
- Each time an agent calls Bash, it mounts a complete workspace, including .git, dependencies, and build outputs, without copying files. When the run ends, it auto-commits a save point and unmounts.
- All saves are split into content chunks, deduplicated, and stored in one SQLite file. Multiple agents committing to the same store are rejected if they touch the same file. Lock files, caches, and similar files can be marked "last writer wins."
- Any save point can be forked again, and forking doesn't copy files.
Its only current use is dsh-layerfs, a plugin for DeepSeek Harness (dsh). dsh is an agent runtime framework DeepSeek open-sourced in Aug 13, now at 275k stars (GitHub, 11-06).
The README is candid: it only has a "use and throw away" mode, with no protection against crashes or power loss, and warns "don't treat it as the only copy of data you can't rebuild." Version 1.1 already broke compatibility with 1.0,2.0, and it's being redone on another branch.
Where the stars came from
| Date | Stars | What happened that day |
|---|---|---|
| 08-10 | 0 | Repo created, with several previews in September |
| 10-09 | 350 | The first number in the daily log |
| 10-17 | 443 | The author's Chinese warm-up post "DSH-LayerFS + Shark Girl View," 54k views |
| 10-19 | 585 | Reposted by the English Rust account @rustaceans_rs (Rust Bytes): 984 likes, 47k views |
| 10-20 | 898 | +313 in one day; the author announced "official launch on October 21" |
| 10-22 | 1,447 | +484. The v1.0 launch post reached 162k views. The same day, someone (not the author) posted it to Hacker News: 76 points, 48 comments |
| 10-23 | 1,899 | +452, aftershocks |
| 10-27 | 2,136 | Reposted by the French tech account @CamilleRoux: 1,093 likes, 61k views |
| 10-28 | 2,424 | +288, the "999-yuan airdrop" post |
| 11-06 | 2,697 | A few dozen stars a day |
(Star counts come from GitHub daily records. Attributing the 10-20 day mainly to Rust Bytes is an inference, since GitHub doesn't provide per-star timestamps for this repo.)
The last 7 days added only 177, versus 7 in the first 613 days. Momentum is already cooling.
The traffic comes down to four sources:
- The author's own X posts, in both Chinese and English. The Chinese posts tell the human story (no income, 24 hours without sleep rescuing an interface, "stay tuned, family"), with nearly a post a day from October 14 on, counting down to launch. The English posts only cover tech and numbers. The biggest wave was the English launch thread.
- Riding the DeepSeek Harness wave. dsh is built on "everything is a plugin," and plugin authors are all competing for visibility, but most build application-level features. LayerFS is one of the few that builds a storage layer, and its README's first screen is a co-branded "LayerFS × DSH" logo. The author turned DeepSeek operations' 999-yuan airdrop into material for a second wave.
- English tech accounts reposting on their own. The tags "written in Rust, FUSE, has a test table" alone are enough to get picked up by Rust-community accounts.
- Cross-promotion in Chinese AI circles, and the launch video. The video was made with help from @lemomo_ai, and the author says "people asking how the video was made outnumber people asking about LayerFS."
No ads, no Product Hunt launch, and it never appeared on GitHub Trending, as far as I can find.
What Hacker News thought
The HN thread's 76 points brought exposure but not goodwill. Top comments:
- "How is this different from btrfs?" Someone replied: "The difference is this one is vibe coded, and that one has been running in the Linux kernel for years."
- A user named compsciphd: "Did this 16 years ago, published it 15 years ago, patented it 13 years ago, same name and everything." They linked the 2010 USENIX paper Apiary. LayerFS's README later added a "Prior work" section.
- Several people complained the site hijacks scrolling and has too many animations: "I tried for 20 minutes and couldn't get through it."
- Others said: "About 245k lines of Rust written by an LLM. Even the people calling it AI slop have to admit it's technically impressive."
In other words, what gets people to share is the test table and the sheer fact that one person built a filesystem with AI. That same fact is what makes people who know the field frown.
A test table that also lists the losses
The most instructive part of the README is its test table. 8 tests, each linked to its method and raw records:
- Run unmodified against Cloudflare's own 12-test filesystem suite: 5.20 seconds vs. 8.88 seconds, 1.71x faster;
- 157 historical snapshots of a real project stored in 100 MB, 19.9x smaller than Btrfs + zstd;
- 8,798 POSIX conformance assertions, 0 unexpected failures;
- Sequential writes are only 0.31x the control, sequential reads 0.81x, random writes 0.40x. These rows are slower, and the table reports them honestly.
Take big-company baselines, compare against mature alternatives, and list the places you lose. These three moves make a 88-day project look more serious than its peers.
Who it's competing with
"Give an agent a workspace that can fork and roll back" is not something LayerFS invented first, and it doesn't have the most stars.
| Project | Launched | Stars | How it differs |
|---|---|---|---|
| tursodatabase/agentfs | 2025-10 | 3,511 | The closest rival is also a filesystem for agents stored in a single SQLite file; it focuses on one agent's state and audit trail, not on branching and merging. |
| dagger/container-use | 2025-05 | 4,086 | One container per agent plus one git branch. |
| binpash/try | 2023-05 | 5,505 | Single-machine "try first, then apply"; LayerFS's README itself lists it as prior work. |
| vibe-kanban / claude-squad / crystal | 2025 | 28,609 / 8,740 / 3,127 | Uses git worktree to give each agent its own copy of the source code, without dependencies. |
| E2B / Daytona | From ¥2023 | 14,747 / 71,367 | Isolation and snapshots at the sandbox and VM level. |
| shepherd-agents/shepherd | 2026-06 | 2,504 | Makes the agent's execution trace rollbackable, at the runtime layer. |
| Btrfs / ZFS snapshots, overlayfs. | Years | Built into the kernel. | Mature, crash-resistant; the first thing people on HN compare it to. |
(Star counts from GitHub, 10-31 to 11-06.)
I didn't find a repo that directly copies LayerFS, but there is already a site with a "LayerFS alternatives" search page. Several leaders in this category sit between three thousand and tens of thousands of stars. LayerFS's position doesn't rest on unique technology; it rests on being tied to dsh and on its launch playbook.
Another number worth noting: dsh-layerfs, the plugin that is the actual entry point, has only 52 stars (GitHub, 11-06). Lots of people look; how many actually install it is hard to tell from outside. The author has also said that many issues and PRs "feel like agents digging them out of obscure corners."
If it were you
B: Copy the playbook, but don't build another agent filesystem. LayerFS shows that "build the missing infrastructure on a freshly hyped platform + a hard benchmark table + a bilingual launch" can earn over two thousand stars in two weeks, and that anyone can replicate it without big-company backing. The weakness is that its specific niche already has several projects with three to five thousand stars, such as AgentFS, container-use, and try, and HN has already grown wary of "AI-written systems software."
Who it suits: developers who can write systems-layer or infrastructure code (Rust, Go, storage, networking, sandboxing) and who are willing to post progress on X every day. Being able to write in both Chinese and English helps.
Who it doesn't suit: people who only want to build small application-layer plugins; people unwilling to show up and tell their own story; people who want to build something users can trust with their data. That last one requires years of reliability, not a two-week launch.
How to do it: three paths, ranked by how worthwhile they are.
- Pick a different foundation layer: find what dsh (or the next freshly hyped agent framework) still lacks in infrastructure, such as secrets management, network isolation, cost accounting, messaging and locks between agents, or observability, and build it as a plugin. LayerFS captured the gap of "few low-level plugins"; storage is taken, but other areas are still open (my inference, not verified one by one).
- Do the parts it did poorly: no crash resistance, runs only on Linux and inside dsh, and 1.1 is incompatible. A small, stable version that survives power loss, isn't tied to a framework, and works directly with Claude Code and Codex would target the crowd on HN that says "I'd rather use btrfs."
- Change ecosystems: LayerFS only works with dsh. Doing the same thing for the multi-agent workflows of Claude Code, Codex, and Cursor would reach a bigger audience, but you'd be up against container-use and the worktree crowd directly.
How to get users: follow its rhythm. In the ten days before launch, post progress daily in the Chinese-speaking community and put yourself front and center. On launch day, publish an English post focused only on the technology, attach a number to each idea, and include a solid video. Put the benchmark table at the top of the README, using a platform's or big company's own benchmark, and include the losses too. Add a "prior work" section so HN can't dig it up on you first. Keep the website restrained and don't hijack scrolling. Any endorsement from the platform (reposts, airdrops, recommendations) becomes a second wave.
When to get in: dsh's plugin ecosystem is still growing, but it gets more crowded every month, and the open foundation slots keep shrinking. To ride this wave, you'd ideally have something out before Q1 of 2027 1.0.
Signs you've misread it: (1) LayerFS ships nothing new and its weekly star gains stay above 200 a month later. That means the category can pull people on its own, and building a direct competitor is worth considering. (2) dsh's star growth clearly stalls and plugin posts stop getting attention. The platform free-ride path is closed. (3) Another AI-written foundation project gets torn apart on HN until it's pulled, or a serious data-loss incident happens. Then "AI-written systems software" shifts from a selling point to a liability, and the same playbook has to be reframed more conservatively.
Research notes: competitor table, acquisition evidence, full research report
- Competitors
Name Where Launched Scale How it differs from this one tursodatabase/agentfs (Turso AgentFS) Open source 2025-10-24 3,511 stars; derived repo run-llama/agentfs-claude 323 stars Also a SQLite single-file filesystem for agents, but focused on single-agent state and audit. LayerFS focuses on multi-agent branching, merging, conflicts, and content-based deduplication. dagger/container-use Open source 2025-05-23 4,086 star One container per agent plus a git branch. LayerFS works at the filesystem layer and makes one Commit per tool call. binpash/try Open source 2023-05-17 5,505 star Single machine, one overlay at a time: try first, then apply. LayerFS lets multiple agents share one Store, with full history. The git worktree family (vibe-kanban / claude-squad / crystal). Open source 2025 28,609 / 8,740 / 3,127 star Worktrees only cover source code. LayerFS mounts the whole tree zero-copy, including .git, dependencies, and build artifacts, so nothing needs reinstalling. E2B / Daytona / zeroboot / arcbox Open source 2023–2026 14,747 / 71,367 / 2,467 / 4,251 star Sandboxing, VM-level isolation, and snapshots. LayerFS only handles the storage history layer and leaves sandboxing to Docker. shepherd-agents/shepherd Open source 2026-06 2,504 star Rollbackable execution traces at the runtime layer. LayerFS is at the filesystem layer. TigerFS / JuiceFS / cloudflare artifact-fs / smfs / airstore Open source 2021–2026 722 / 14,694 / 1,211 / 492 / 187 star Databases and object storage mounted as filesystems, instant mounting of large repos, memory-style filesystems. None of these focus on multi-agent branch merging. Btrfs/ZFS snapshots, overlayfs. Other Years Kernel-level and mature. Mature and crash-resistant. LayerFS claims it saves 19.9x the space on small-file history, but it only has a Disposable mode and no crash-persistence. Cloudflare Computer Big-company features 2026 Not verified LayerFS benchmarked on Cloudflare's own fs-bench and claims to be 1.71x faster, borrowing credibility from a big company's benchmark. - Where users come from
- Verified The author's own X posts (bilingual, ten-day countdown + personal story): @yifanxu_ephai 10-21 v1.0 launch post got 1,297 likes and 162k views; +484 stars the next day and +452 the day after; a Chinese teaser post 10-17 got 54k views.
- Verified Attached to the DeepSeek Harness platform + small official endorsement: shipped as the dsh-layerfs plugin (dsh 274,792 stars); 10-28 the author shared a DeepSeek operations airdrop of ¥999, 122k views, +288 stars that day.
- Verified Reposts from English and French technical accounts: @rustaceans_rs post 10-19 got 984 likes and 47k views, +313 the next day; @CamilleRoux post 10-26 got 1,093 likes and 61k views; @DanKornas 11-04.
- Verified Hacker News: 10-21 someone else submitted "LayerFS: A filesystem for AI coding agents"; it got 76 points and 48 comments, many questioning whether it was vibe-coded and the website's scroll hijacking.
- Verified Cross-promotion in the Chinese AI community + a launch video made for it: reposts from @barryxv6, @Lonely__MH, and @ZengwuY; the launch video made by @lemomo_ai drew many questions.
- Verified Aggregator sites / Reddit weekly roundups / LinkedIn and Instagram reposts: hermes-ai.net, InferRealm, agentswitchboard 10-31, ai.dosa.dev, the r/OpenSourceAI weekly roundup, and automatic r/hackernews reposts.
- Verified Feishu livestream + Discord/WeChat groups: 10-26 a Feishu livestream about LayerFS 2.0.
- Inferred Ads / Product Hunt / GitHub trending: nothing found; a repo under 60 days old can't appear on trending (trending_days_any=0).
Why LayerFS (Ephemeral-AI-Lab/layerfs) took off
Channel: GitHub · Research day 2026-11-06 · Data card: gh_Ephemeral-AI-Lab__layerfs.json
One line
LayerFS is a FUSE filesystem written in Rust. Each time an AI agent calls Bash, it mounts a complete, writable Workspace (without copying the base). When the run finishes, it automatically commits a deduplicated Commit that can be branched, rolled back, and merged. Everything lives in a single SQLite file. The initial release shipped as dsh-layerfs, a plugin for DeepSeek Harness (dsh).
Takeaway: Chinese indie developer Yifan Xu (@yifanxu_ephai) packaged "filesystem isolation and history for parallel multi-agent work" as a Rust infrastructure project with hard numbers, and launched it on DeepSeek Harness, a new platform with 270k stars. The v1.0 launch post from 10-21 (160k views), plus an HN submission that got 76 points on the same day, and reposts from English Rust and French technical accounts brought in about 940 stars over two days. A story post about a DeepSeek operations airdrop of ¥999 (10-28) brought another wave. Afterward, the buzz faded to a dozen or two dozen stars a day.
1. Growth data
Source: our GitHub repo_day dataset (daily from 10-09 onward; early days sourced from deeply).
| Date | star | Daily gain | what happened |
|---|---|---|---|
| 08-10 | 0 | — | Repo created |
| 09-01 ~ 09-16 | — | — | v0.1.0 to v0.1.6 developer preview releases (GitHub releases) |
| 10-09 | 350 | — | First observation in the dataset |
| 10-15 | 403 | +1 | The author posted a demo video (15k views). |
| 10-18 | 489 | +46 | 10-17 The author's Chinese post "DSH-LayerFS + shark-girl view" 54k views; reposted by @Lonely__MH. |
| 10-19 | 585 | +96 | 10-19 01:34 (Beijing) @rustaceans_rs (Rust Bytes) posted, 984 likes and 47k views. |
| 10-20 | 898 | +313 | The Rust Bytes post kept gaining traction, and the author previewed an "Oct 21 Official Release" 10-20. |
| 10-21 | 963 | +65 | v1.0.0 released (10-21 11:21 UTC). |
| 10-22 | 1,447 | +484 | The author's English launch post (10-21 20:00 Beijing time) got 1,297 likes and 162k views; HN "LayerFS: A filesystem for AI coding agents" got 76 points and 48 comments (10-21 12:34 UTC, submitted by l2dy, not the author). |
| 10-23 | 1,899 | +452 | Launch post and HN aftermath; automatic reposts on r/hackernews and r/hypeurls; Windows support added. |
| 10-24 | 1,992 | +93 | v1.1.0 |
| 10-27 | 2,136 | +68 | 10-26 Recommendation from French technical account @CamilleRoux (1,093 likes, 61k views). |
| 10-28 | 2,424 | +288 | 10-28 06:59 Author's post: "Got an airdrop from a DeepSeek ops girl 999 yuan (because dsh-layerfs got noticed)" 772 likes, 122k views |
| 10-29 ~ 11-06 | 2,689 | +13 to +58 per day | Long tail: aggregator sites, weekly roundups, LinkedIn/Instagram reposts |
- +177 in the last 7 days, +613 in the first 7 days; the repo is marked "cooling". Single-day peak +484 (10-22).
- forks 149, fork/star ratio 5.5%, open issues 40, open PRs 17 (github repo, captured 10-31).
- The author himself says many PRs/issues "feel more like an agent digging them out of obscure corners" (X 10-27), so some contributors may be AI-generated contribution spam, not real users.
- Star timeline breakdown unavailable: the GitHub stargazers API returns 404 for this repo.
2. Competitors: who else does the same thing
"A forkable, rollbackable filesystem / workspace for agents" is already a crowded lane. LayerFS is not the first, nor the one with the most stars.
| Product | Type | Launched | Scale | How LayerFS differs |
|---|---|---|---|---|
| tursodatabase/agentfs(Turso AgentFS) | Open source | 2025-10-24 | 3,511 stars; derived repo run-llama/agentfs-claude 323 stars | The most direct rival, also "a single SQLite file holding an agent filesystem + audit." AgentFS focuses on state and auditing for a single agent; LayerFS focuses on multi-agent branching, merging, conflict handling, and content-based dedup. |
| dagger/container-use | Open source | 2025-05-23 | 4,086 star | One container plus a git branch per agent. LayerFS works at the filesystem layer, with one Commit per tool call, and doesn't rely on git. |
| binpash/try | Open source | 2023-05-17 | 5,505 star | Single-machine, one overlay at a time, "try first, then apply." LayerFS's README lists it as prior art. |
| Git worktree family: BloopAI/vibe-kanban, smtg-ai/claude-squad, stravu/crystal | Open source | 2025 | 28,609 / 8,740 / 3,127 star | Each agent gets its own copy of the code via git worktree. LayerFS's pitch is mounting the whole tree at once, including .git, dependencies, and build artifacts, so a new Workspace needs no reinstall. |
| E2B / Daytona / zerobootdev/zeroboot / arcbox | Open source + cloud | 2023–2026 | 14,747 / 71,367 / 2,467 / 4,251 star | Sandboxing, VM-level isolation, and snapshots. LayerFS covers only the storage layer and leaves sandboxing to Docker. |
| shepherd-agents/shepherd | Open source | 2026-06 | 2,504 star | Turns agent execution into git-like, reversible trajectories. Runtime-focused, whereas LayerFS is filesystem-focused. |
| timescale/tigerfs, juicedata/juicefs, cloudflare/artifact-fs, supermemoryai/smfs, beam-cloud/airstore | Open source | 2021–2026 | 722 / 14,694 / 1,211 / 492 / 187 star | Databases or object storage mounted as filesystems, instant mounts for large repos, memory-style FS. None of them focus on multi-agent branch merging. |
| Btrfs/ZFS snapshots, overlayfs. | Engine | Years | System level | Mature and crash-tolerant. LayerFS's benchmarks claim 19.9x less space on small-file history, but it only has a Disposable mode and no crash persistence. |
| Cloudflare Computer (source of fs-bench) | Big-company features | 2026 | — | LayerFS runs Cloudflare's own 12-item fs-bench and claims a 1.71x speedup, borrowing a big company's benchmark to lend credibility. |
| Apiary(Potter & Nieh,USENIX ATC 2010) | Academic | 2010 | — | On HN, original author compsciphd commented that the idea was "built and patented 16 years ago"; LayerFS's README later added a Prior art section. |
3. Growth: where users come from
- The author's own X account (bilingual, Chinese and English) is the main engine (confirmed). @yifanxu_ephai has posted progress almost daily since 10-14. Chinese posts tell personal stories ("no income for a year and a half, dropped out, living at my parents' place", "24 hours without sleep rescuing the UI", "a VC called me an idiot six months ago"), while English posts focus on technology. The v1.0 English launch post got 1,297 likes, 172 reposts, and 162k views, and it was the source of the biggest wave.
- Tied to the DeepSeek Harness platform (confirmed). dsh is an agent harness open-sourced by DeepSeek 2026-08-13 ("Everything is a Plugin"; deepseek-ai/deepseek-harness now has 274,792 stars; the HN launch post scored 747 points). LayerFS ships as a
dsh-layerfsplugin, its topics includedeepseek, and the README's first screen reads "LayerFS × DSH." Many projects in the plugin ecosystem compete for exposure, and LayerFS is one of the few working at the storage layer. The team also built dsh-plugins (54 stars, "Make Deepseek Harness Great") and mayfly (a dsh terminal UI, 23 stars). - A small DeepSeek official endorsement became material for a second wave of spread (confirmed). 10-28 The author posted "DeepSeek ops airdropped 999 yuan," along with the struggle of burning his own money on the MiniMax API and not finding a token sponsor. It got 122k views, and the star count rose +288 that day.
- Self-posted reposts from English tech accounts (verified). @rustaceans_rs (Rust Bytes) posted it 10-19 with 984 likes and 47K views, and it later made their weekly newsletter; @CamilleRoux (French) posted 10-26 with 1,093 likes and 61K views; @DanKornas posted 11-04. Stars rose +313 the day after the Rust Bytes post, and the timing matches.
- Hacker News (confirmed). Submitted by 10-21 others, scored 76 points with 48 comments; the front-page ranking is not recorded. The comments were mostly negative: "vibe coded," "website hijacks scrolling, AI slop," "what's the difference from btrfs," "existed 16 years ago." Some said, "245k lines of Rust written by an LLM, technically impressive." HN brought exposure, not reputation.
- Cross-promotion within Chinese AI circles (confirmed). @barryxv 6 10-11 (10k views), @Lonely__MH 10-18, @ZengwuY 10-21, and @lemomo_ai (Lemon Teacher helped produce the launch video). The author specifically thanked the video creator, saying "as many people asked how the video was made as asked about LayerFS." The launch video itself became a point of spread.
- Aggregator sites and SEO long tail (confirmed). Long posts on hermes-ai.net, InferRealm, agentswitchboard (10-31 drop), ai.dosa.dev, vibecoding.app, and thesatyajit.com; Reddit r/OpenSourceAI ("14 new AI dev tools") and r/EveryDevAI; Instagram ("three tools trending on GitHub right now"); LinkedIn reposts.
- Livestreams and communities (confirmed). 10-26 A Feishu livestream about LayerFS 2.0, plus a Discord and WeChat groups ("group members").
- Ads / Product Hunt / trending: none found. The repo is 88 days old; it can't reach trending before 60 days, and our github repo shows trending_days_any=0.
4. Why it made the list
- Hit a real problem: when multiple agents run in parallel, each needs a full copy of the project, which is slow, takes up space, and is hard to roll back. On HN, fnordpiglet said he runs 100 worktrees at once, which is exactly the use case LayerFS describes.
- Packaging "AI-written systems software" with hard numbers: the README opens with a 8-row benchmark table (19.9× smaller than Btrfs+zstd, 1.71× faster than Cloudflare fs-bench, 0 unexpected pjdfstest failures), and it even admits where it loses to fio. There's also a "Use something else if…" section, which makes it look more serious than the usual competitors. Before 10-21, it also pushed claims like "2.5TB snapshots, 30 branches squeezed into 4.66GB."
- Riding the platform: DeepSeek Harness was hot, plugin authors were all competing for exposure, and "DSH is missing a storage layer" made for an easy story. DeepSeek ops' 999-yuan airdrop became material for the second wave.
- Founder story + launch pacing: a ten-day countdown in the Chinese community ("Stay tuned, everyone" and "24 hours without sleep"), the persona of a broke but determined indie dev, plus a commissioned launch video and an anime "shark girl" visual gave a low-level storage library emotion and imagery on X.
- Launching in Chinese and English at the same time: Chinese community cross-promotion laid the groundwork, and the English Rust account, French account, and HN amplified it. The Rust tag alone gets picked up by Rust community accounts.
5. What the differentiation is, and whether it explains the breakout
- Technical differentiation: "each tool call = one mount + one Commit," content-based chunk dedup (CAS + CDC + COW), zero-copy forking of the whole tree (including .git, node_modules, and build artifacts), multiple agents committing to a single SQLite Store, same-file conflicts rejected, and the
.lwwrule lets new writes overwrite. Turso's AgentFS is also a single SQLite file, but it doesn't focus on branching, merging, or dedup; the git worktree family doesn't include dependencies or build artifacts; sandbox tools handle isolation but not history. - Why it spread: the differentiation is a "hook" that can be explained clearly and backed by benchmarks, which makes Rust accounts and tech bloggers willing to repost. But most of the stars came from the launch strategy + the platform wave + the author's personal story. Practical usability is still weak: it only has a Disposable mode and offers no crash protection, 1.1 already broke compatibility, 2.0 was redone on another branch, and HN generally distrusts a "vibe-coded filesystem." Differentiation is necessary, but distribution is what decided the outcome.
VI. Visibility and copycats
- Visibility: it's spreading within a small circle. It's known in the Chinese indie AI developer community and in the Rust/agent infrastructure community. The largest single post got 160k views; HN reached 76 points (not a big hit). Coverage comes from small sites like hermes-ai and InferRealm plus aggregators, with no mainstream tech media. It's open source and free, with no revenue.
- Copycats: no repo directly copying LayerFS has been seen. Parallel AgentFS derivatives in the same space (coplane/localsandbox, CelestoAI/AgentFS), YoloFS, and others predate it or are independent of it. ai.dosa.dev has already built a "LayerFS alternatives" SEO page.
VII. What others can borrow
- On a newly hot platform (here, dsh), building the missing "infrastructure" plugin gets singled out by the official side and media more easily than building an app-layer plugin.
- Infrastructure projects build credibility with benchmark tables that compare against the big company's own benchmarks and mature solutions (Btrfs), and that also list the categories where they lose.
- A ten-day countdown before launch + a personal story + a commissioned launch video; official small endorsements (airdrops, reposts) get amplified again as second-wave material.
- A bilingual launch: the Chinese community lays the foundation, and English tech accounts amplify.
- Lesson learned: HN dislikes AI-generated systems software and flashy scroll-hijacking websites, so the site of an infrastructure project should stay restrained.
8. What's still uncertain
- The exact source of each peak is unknown, because stargazer timestamps are unavailable. Attributing the +313 on 10-20 mainly to Rust Bytes is an inference.
- Whether DeepSeek officially recommended LayerFS through dsh's official channels (README, plugin marketplace featured slots, official X): the author only says "got noticed, received a 999-yuan airdrop." Searching the deepseek-ai/deepseek-harness issues finds no mention of layerfs.
- Real installs and usage: dsh-layerfs has only 52 stars; npm/SDK downloads were not checked.
- The data card says "@ScarletKc / Yifan Xu" are the same person, which is incorrect: the author is @yifanxu_ephai (4,132 commits); ScarletKc is a contributor (10 commits) and a friend who gave the author Devin. The HN submitter l2dy is not the author either.
- 2.0 (LayerFS Connect, storage-compute decoupling, shared Postgres): whether these can turn stars into real users.
Sources
- GitHub repo and API: github.com/Ephemeral-AI-Lab/layerfs (README, releases, contributors); stars for repos under the organization; deepseek-ai/deepseek-harness has 274,792 stars
- Our github repo: repo_profile, repo_day (Ephemeral-AI-Lab/layerfs, 2026-10-09 ~ 11-06)
- Our hackernews repo + HN API: item 50179857 (76 points, 48 comments), 49285244 (dsh launch, 747 points)
- X (x live / x post, checked 2026-11-06): 2112876555907064008 (v1.0 launch), 2115216765512995263 (999 airdrop), 2111873467180015848 (Rust Bytes), 2114733867739295888 (Camille Roux), 2111398582289076594, 2112253765139271695, 2112602428126458125, 2113293725044756551, 2114884296536404218, 2108942646962184357, 2108955023698989109, 2112901988690374833, 2117745126915379598
- Web: hermes-ai.net/news/ephemeral-ai-lab-s-layerfs-gives-parallel-ai-agents-forkable-isolated/; inferrealm.com/news/layerfs/; agentswitchboard.dev/drops/2026-10-31; ai.dosa.dev/tools/layerfs/alternatives; reddit r/hackernews 1xbpkp9, r/OpenSourceAI 1xkdlue; juicefs.com blog (AgentFS/TigerFS/JuiceFS comparison)