Stringers
lemonadesaltbagel/airlock · lemonadesaltbagel

189 stars, 2 commits, 0 issues: a local coding agent that "doesn't let the cloud see your code", how did the stars come in

What it is A local coding agent: your code only goes to the model on your machine. When stuck, it rewrites the problem as a small example unrelated to your project, checks it, and only asks a cloud frontier model after you approve.

Why it blew up It didn't blow up on its own. Four unrelated AI libraries the author published the same week each gained a steady +12 to 15 stars and +3 forks per day. 38 of the forks come from fork-only accounts that look like paid-work accounts, with zero off-platform discussion. It's safe to conclude the stars were bought.

CHow you could follow it Don't copy a big all-in-one local agent. Build the "rewrite as an unrelated example + strict rule checks" piece on its own as an MCP plugin that plugs into Claude Code and Cursor, then use a real-case comparison table and CLAIMS.md-style per-claim promises to post on Show HN and r/LocalLLaMA for genuine stars.

C grade: the "ask the cloud in different words" idea and the CLAIMS.md format are worth learning, and similar redaction proxies can get real hundreds to thousands of stars. But this repo's stars were bought, there's no real demand evidence for the specific approach, and local agents and sandboxes already have mature open-source options. Few people know about it yet
Data (updated daily) · Repo created 2026-10-24 · 287 stars · 7 days +84
GitHub · stars
010020030010-3111-0511-1011-1511-20287
Data 2026-10-31 → 2026-11-20 (21 days, 21 observations). Points before 10-28 come from deeply / archive backfill, not every day has one

Airlock is a local coding agent: your code only goes to the model on your machine. When stuck, it rewrites the problem as a small example unrelated to your project, then asks a cloud frontier model. The idea is rare and the README is professionally written. But it climbed to 189 stars in 19 days, tracking the same straight line as three other libraries the author published that same week, and all its forks came from the same pool of "work-for-hire" accounts. If you want to build a similar project and collect stars, first separate "the idea is good" from "the stars are real."

After Oct 28, the code stopped; the stars didn't

The repo was created in 2026 Oct 24 by a developer in Sydney with the GitHub name lemonadesaltbagel, whose bio reads "Exploring agentic post-training." At midnight on Oct 28 he pushed a second commit adding a sandbox, a gateway, and encrypted logs, and has never pushed code since.

From that day on, stars and forks began arriving daily:

DatestarsforkStars that day
10-31284
11-036313+13
11-0610221+15
11-0914430+13
11-1218938+18

GitHub daily numbers. Over 12 days, stars came in daily at +9 to +18, with no sudden spikes and no zero days; forks came in at 2 to 4 per day, every single day.

At first glance the curve looks healthy: no sign of a leaderboard push, more like word of mouth spreading slowly. The problem is that the four AI tool libraries the author published from Oct 21 to 24 trace out the same line:

LibraryRepo createdWhat it doesAs of 11-12
veil10-21A local privacy proxy for coding agents29 → 174 stars
crab10-22Reverse-engineering behavior to rewrite software51 → 296 stars
sill10-23Native Windows bash for coding agents40 → 241 stars
airlock10-24This one28 → 189 stars

The four topics are unrelated, yet the daily gains each swing between +12 and +15 stars and +3 forks, with forks making up 14% to 20% of stars. As a control, his GR IV camera firmware patch GR4-LUTSmith, built in early October, has 40 stars, gained +1 over the last ~7 days, and stopped long ago.

Who forked the 38 forks

Checking airlock's 38 fork accounts one by one (from public GitHub profiles), they look nearly identical: each has 17 to 100 repos, 85% to 100% of which are forks of others' work. Of the 17 accounts whose followers were checked, none has more than 8 followers. 8 accounts have a single star and no commits at all. Their names look randomly assembled: Jizzspionage, Dorcelub, Prosecol, Valencool.

Looking at what else these accounts starred: all 31 starred EverOS and DataFlow, 30 starred MemoryBear, followed by a string of freshly released AI libraries like SenseNova-U1 and OmniAgent. The forked repos overlap heavily too. A shared pool of accounts taking turns starring and forking a batch of client repos, with a few large repos mixed in as cover, is the typical look of a bought-stars account pool.

Sampling 12 forkers each from the author's other three libraries, 11, 12, and 9 of them respectively match the same profile. Of the 7 forkers of the early camera library, only 2 look like that. In other words, the AI libraries from late October were pushed through in batches.

Outside GitHub, there's no buzz: nothing on Hacker News, X, Reddit, or in the media. The only results are auto-aggregators that scrape GitHub, like slopbucket and GitHot. 189 stars and 38 forks, yet only 0 issues from real people and 0 external PRs, the only PR being from dependabot. All 38 forks stopped at the Oct 28 commit, and nobody changed a single line on top of it.

Conclusion: stars and forks were bought and delivered at a steady daily pace (an inference, with high confidence: GitHub doesn't publicly list who starred a repo, so stars can't be checked one by one; this is deduced from the fork roster and the synced curves). Judging from the author's bio and cadence of publishing repos, the goal seems to be a GitHub track record and reputation.

The idea itself is good

Bought stars don't mean the product is empty. The README's first line: "A local coding agent that keeps your project private and asks frontier models for help without showing them your code": a local coding agent that keeps your code secret while still asking frontier models for help, without showing them your code.

How it works:

  • The work stays local. Reading code, editing code, running tests: all of it talks only to llama.cpp on your own machine.
  • It asks the cloud only when stuck, and it rephrases the question. When tests keep failing, it rewrites the problem as the kind of minimal reproducible example a senior engineer would post on Stack Overflow: no filenames, variable names, business details, or your code. You can read the original and approve each item before it's sent.
  • A hard-rule outbound check. If a message contains project identifiers, string literals, copied code, secrets, or any term you listed in jewels.json as off-limits, it is not sent.
  • A fictional backstory. airlock init randomly assigns each project a fictional scenario, and every question is framed inside it, so someone reading the query log can't reconstruct what you're building.
  • Sandbox and gateway. The agent runs inside macOS Seatbelt / Linux bubblewrap. The sandbox layer uses Anthropic's open-source sandbox-runtime directly. Only the gateway outside the sandbox holds the API key, and every outbound message is logged to an encrypted, tamper-evident log.

The most instructive part is CLAIMS.md. It opens with "This is a privacy tool, so this file is part of the product," then lists exactly what is and isn't guaranteed, including a line few people dare to write: "Airlock makes no privacy guarantees yet." The rewriting is done by a model, and the check only catches literal leaks. Describe your idea in different words and it can still leak out.

But it's still a preview: 2 commits in total, and the author writes "only use it on test projects for now."

Who's doing something similar

ProjectStarsHow it differs
HazyResearch/minions1,388Stanford's local-small-model-plus-cloud-large-model collaboration. The closest idea, but it sends excerpts of the original text to the cloud.
sgasser/pasteguard828A local privacy proxy that redacts PII and secrets. No agent included.
openai/privacy-filter2,779OpenAI's PII detection and masking model.
rizzo-pii, DontFeedTheAI, kiji-proxy, and others.339–1,265Assorted LLM outbound redaction proxies. They don't sandbox anything and don't rewrite questions.
stacklok/codegate791, archivedThe predecessor of a local coding-agent privacy gateway. It has been discontinued.
OpenCode, or Aider with a local model.226k / 50kRunning fully local means nothing leaks, but there's no "rephrase, then ask the cloud" step.
Five or six projects called Airlock.Single digits to 22Name collisions. They do agent sandboxing and credential isolation, not code privacy rewriting.

Star counts are GitHub public numbers, 11-12. Big companies solve "can code go to the cloud?" with zero-retention contracts, Copilot content exclusion, and Tabnine on-prem deployment, not by rewriting questions.

The combination of "work locally + rewrite into unrelated examples before asking + hard-rule check + fictional backstory" hasn't turned up a second instance. Redaction proxies do genuinely reach a few hundred to over a thousand stars, which shows people care about "don't let AI see my stuff." But whether anyone actually uses this specific "rephrase before asking the cloud" approach, airlock offers no evidence at all.

If it were you

The verdict: The idea is worth borrowing, but this repo's stars can't be taken as demand evidence. Building another airlock like it will most likely not earn real stars. Isolating and doing its best step well has a shot.

Who it fits: Developers who have built coding agents, MCP tools, or security tools and can state a privacy promise clearly and test it, or people in healthcare, law, finance, or corporate intranets for whom "code can't leave the building" is a real pain.

Who it doesn't fit: Anyone aiming for a big all-in-one "local agent + sandbox + gateway." OpenCode and Aider already own the local agent space, and Anthropic's sandbox already exists, so your effort goes into parts others have already done well. It's also not for anyone hoping to start by buying stars. Bought stars don't bring users, and getting caught hurts your reputation.

How to do it:

  1. Build only the "rewrite + check" layer, as an MCP tool or a plugin for Claude Code / Cursor. Plug into the agents people already use instead of asking them to switch agents.
  2. Prove it works with real cases. Collect genuine problems from open-source projects, and show before-and-after rewrites, the cloud's answers, and whether anything leaked in a table at the top of the README. This is what airlock most lacks.
  3. Learn from CLAIMS.md: write out, line by line, what is and isn't guaranteed, and pair it with a detection command anyone can run. For a privacy tool, that honesty is the most valuable part.

How to get users: Post a Show HN with a title that says it plainly, like "Let Claude fix your bugs without showing it your code." Post in r/LocalLLaMA and r/privacy. Leave comparison tables under enterprise security and compliance accounts and newsletters on X. Real users will file issues, and those issues become your next version's requirements.

When to build it: Not in a rush. Big vendors solve enterprise demand with contracts, and no individual developer has claimed this layer in the short term (an inference). But local models get stronger every quarter, and once they're strong enough that you never need the cloud, this layer's value shrinks. Shipping within a year is a reasonable bet.

What would show I got it wrong: If your version has been out for a month or two and nobody on Show HN or Reddit asks how to use it or files an issue, and people only click the star, then "rephrase before asking the cloud" is a need that sounds good but nobody actually uses. Conversely, if real people keep filing issues and PRs after airlock stops inflating its numbers, the gap is bigger than it looks and a better version is worth building seriously.

GitHub repo ↗

Research notes: competitor table, acquisition evidence, full research report
Competitors
NameWhereLaunchedScaleHow it differs from this one
HazyResearch/minionsOpen source2025-021,388 starA protocol for local small models and cloud large models to collaborate. The idea is recent. Minions sends excerpts to the cloud; airlock rewrites into project-unrelated examples before asking, and adds a sandbox.
sgasser/pasteguardOpen source2026-01828 starAn outbound privacy proxy that redacts PII and secrets. It doesn't bundle an agent and doesn't rewrite questions.
lemonadesaltbagel/veil (same author)Open source2026-10-21174 stars (also inflated)A deterministic pseudonymization proxy. airlock is a version of it that adds a bundled local agent.
openai/privacy-filterBig-company features2026-042,779 starA model that only does PII detection and masking.
rizzo-pii / DontFeedTheAI / kiji-proxy / packyme privacy-filterOpen source2025–2026339–1,265 starAn LLM outbound redaction proxy. It doesn't handle agent sandboxing or question rewriting.
stacklok/codegateOpen source2024-11791 stars, archivedThe predecessor of a local coding-agent privacy gateway. It has been discontinued.
anthropics/sandbox-runtimeOpen source2025-107,086 starClaude Code's OS sandbox. airlock's sandbox layer uses it directly.
OpenCode / Aider with a local model.Open source2023–2025226k / 50k starFully local means no leaks, but there's no step of de-identifying and then asking the cloud.
Code Airlock, calebfaruki/airlock, airlock.sorrel.systems, and other projects with the same name.Other2026-03 to 11Each has single-digit to 22 stars, with HN scores of 1–4.They do agent sandboxing, credential isolation, or policy control. None do code-privacy question rewriting.
Anthropic and OpenAI zero-retention, Copilot content exclusion, Tabnine offline deployment.Big-company featuresAlready thereEnterprise standard.They prevent code leaks through contracts and private deployment, not by rewriting questions.
Where users come from
  • Verified paid star and fork farming (a pool of accounts deployed at a steady daily rate): 38 forkers, starting from 10-28, arrive at 2 to 4 per day. Each has 17 to 100 repos, 85% to 100% of which are forks, and the followers of the 17 accounts checked are all under 8. 8 accounts' stars and contributions are all 0. This pool is mass-starring and forking the same chain of repos, including EverOS, DataFlow, MemoryBear, and OmniAgent. Of 12 forkers sampled from the same author's crab, sill, and veil, 11, 12, and 9 respectively are the same kind of account. Of the 7 forkers on a camera firmware repo, only 2 are.
  • Verified automatic aggregator indexing: slopbucket.app (36 stars at time of indexing), hahachat.icu, GitHot, and githubrepo.cloud all scrape automatically.
  • Inference HN / X / Reddit / media: No HN story links to lemonadesaltbagel. x-radar returns 0 results. Jina, Exa, and Brave turn up no discussion.

lemonadesaltbagel/airlock: how it got this far

Verdict

It didn't catch fire on its own. The curve looks healthy, "19 days, 189 stars, rising by 13 a day at a steady pace," but it follows the same pattern as three other AI tool repos the author built in the same week (crab, sill, veil). All four were created between 10-21 and 10-24, and afterward each shows a straight line of +12 to +15 stars and +3 forks per day. All of airlock's 38 forks come from one type of account: ten to a hundred repos each, 85% to 100% forks, 0 to 8 followers. These same accounts are also mass-forking and starring a batch of new Chinese AI repos (DataFlow, MemoryBear, OmniAgent, Tourmind-Booking-Skills, and others). HN, X, Reddit, and the media show nothing, and the only traces are auto-scraped aggregator sites. The most reasonable explanation is paid starring and forking, deployed at a steady daily rate. The recall scoring treats "steady, no spikes" and "fork/star ratio at 20%" as signs of real spread. Here they're the reverse. Steady pacing and a fixed fork ratio are exactly the signature of a botting service.

The product idea itself is solid: a local model does the work, and when stuck it rewrites the problem as a de-identified "Stack Overflow-style minimal example" before asking a frontier cloud model. It also has a deterministic outbound check, a "fictional backstory" cover, an OS sandbox, and a gateway that holds the key. But it's still a preview, with 2 commits in total. It states plainly, "no privacy guarantees for now, don't use it on private code," and no real user has filed an issue.

What it is

  • Description: A privacy-first local coding agent that consults frontier AI models without exposing your source code. (Apache-2.0, TypeScript, monorepo: packages/{agent,broker,consult,gateway,ledger,policy-data,sandbox})
  • Mechanism (README, CLAIMS.md): A local llama.cpp model reads and writes code and runs tests. After repeated failures it calls consult_expert, which first rewrites the problem into generic, project-unrelated examples, wraps it in the fictional backstory chosen randomly at airlock init, and passes it through a deterministic outbound check (blocking project identifiers, string literals, copied code, secrets, and self-declared crown jewels). By default the user must approve each item before it goes to the cloud model (which uses the user's own key). The agent runs in a Seatbelt / bubblewrap sandbox, and the sandbox layer uses Anthropic's open-source @anthropic-ai/sandbox-runtime 0.0.81 (packages/sandbox/package.json). Outbound records are written to a tamper-evident log using AES-256-GCM with an HMAC chain.
  • Status: 2 commits (10-24 initial release, 10-28 added sandbox, gateway, and logging). No code has been pushed since. The only PR was opened by dependabot. 0 issues (GitHub API, 2026-11-12).
  • Author: lemonadesaltbagel (Austin / Xintian Huang, Sydney; the repos include a UNSW COMP1531 course repo). The bio reads "Exploring agentic post-training." 187 followers, no X account. Starting in 2026-10, they shipped more than a dozen repos in a burst: Ricoh GR IV camera firmware patches (GR4-LUTSmith and others, 10-07 to 10-16), sill (native Windows bash for coding agents), veil (a local privacy proxy for coding agents), crab (black-box behavior cloning), airlock, pane (macOS window management), OpenWiSH, cnode, and others.

Growth data

  • Data card (github repo_day): 10-31 has 28 stars, 11-12 has 189 stars. Over the last 7 days: +102, with a single-day peak of +18. Daily gains: +13, +9, +13, +13, +11, +15, +13, +16, +13, +15, +12, +18, with no spikes at all.
  • Same author's repos over the same period (github repos, as of 11-12):
    • sill (created 10-23): 40 → 241, daily +9 to 18
    • veil (10-21 built): 29 → 174, +5 per day through 14
    • crab (10-22 built): 51 → 296, +7 per day through 21
    • Forks and stars on all four repos sit between 14% and 20%. The control is the author's earlier camera-firmware repo from early October: GR4-LUTSmith has only 40 stars, +7 in the last 1 days, and it has stopped growing.
  • None of them made trending. That means little, since a repo under 60 days old can't make it anyway.

Growth tactic: evidence of fake traffic

  1. Forks arrive at a steady pace. Airlock's 38 forks started at 10-28, adding 2 to 4 a day, through 11-11 (GitHub forks API). Crab's 53 forks, from 10-25 to 11-11, also add 1 to 5 a day, every single day.
  2. The fork accounts all look alike. I checked 38 forkers one by one (GitHub API): each has 17 to 100 repos, and 85% to 100% of them are forks (KhaLift has 37 repos, 35 of them forks; Jizzspionage has 18, 17 of them forks; f2Wong has 100, all forks). I checked the followers of 17 of these accounts, and all of them have 8 or fewer. 8 accounts have stars at 0 and contributions at 0 (DTT-108, Jizzspionage, MusePose, Valencool, etc.). Quite a few names look randomly generated (Jizzspionage, Dorcelub, Prosecol, Valencool, puredict).
  3. These accounts are boosting the same set of repos. Among the repos that 38 of these accounts recently starred, the most repeated are EverMind-AI/EverOS (31 accounts starred it), OpenDCAI/DataFlow (31), MemoryBear (30), SenseNova-U1 (29), iPolloWork (27), mycontext (26), testsprite-cli (24), OmniAgent (24), and more. The forked repos overlap just as heavily (LightRAG has 12 accounts, bisheng 10, DataFlow 10, Tourmind-Booking-Skills 7). KhaLift starred both the author's crab and veil. This is a classic for-hire account pool: the same accounts take turns forking and starring client repos, with some big repos mixed in as camouflage.
  4. Each of the author's four repos uses a different set of accounts, with almost no overlap. The forkers of airlock, veil, sill, and crab overlap by only 1 accounts each. But from each of the other three repos, I pulled 12 forkers, and 11, 12, and 9 of them respectively match the same profile (more than 85% of their repos are forks, fewer than 10 followers, more than 15 repos). Tks2k4 forked 703 repos from a single account, appearing on crab, sill, and veil. Of the 7 forkers of the camera-firmware repo GR4-LUTSmith, only 2 fit this profile. In other words, the AI tool repos the author posted in late October were pushed in batches, while the early camera repo was not.
  5. No outside chatter at all. No HN story points to lemonadesaltbagel (the Show HN posts with Airlock in the title are other projects). A search for lemonadesaltbagel on x-radar returns 0 results. Jina, Exa, and Brave only surface GitHub's own pages, aggregator sites like slopbucket.app (auto-indexed, reads "posted by lemonadesaltbagel", 36 stars when indexed), hahachat.icu, and githubrepo.cloud. The GitHot listing the recall card mentions (158 stars) is also just an aggregator.
  6. The numbers don't match real usage. 189 stars and 38 forks, but only 2 commits, 0 real issues, and 0 external PRs. Every fork is stuck at the 10-28 commit, and nobody has changed anything on top of it.

Conclusion: the growth tactic is a steady drip of bought stars and forks (confidence: strong indirect evidence; GitHub no longer exposes the stargazer list, the API returns 404, and the graphql totalCount is 0, so the stars themselves can't be checked one by one). Judging by the author's bio and behavior, the goal seems to be GitHub clout or a résumé line, not revenue.

Competitors

NameWhereLaunchedScaleHow it differs
HazyResearch/minionsOpen source2025-021,388 starStanford's protocol for a local small model working with a cloud large model is the closest idea, but minions sends snippets to the cloud. Airlock rewrites the question into an unrelated example before asking, plus adds a sandbox.
sgasser/pasteguardOpen source2026-01828 starA local privacy proxy that sits in front of browser chat, APIs, and coding agents and redacts PII and secrets. It doesn't ship its own agent.
lemonadesaltbagel/veil (the author's own)Open source2026-10-21174 stars (also inflated)A deterministic pseudonymization proxy for tools like Claude Code. Airlock is the version that "upgrades" it by bundling a local agent.
openai/privacy-filterOpen source / big tech2026-042,779 starOpenAI's PII filter model. It only detects and masks.
Rizzo-AI-Academy/rizzo-pii, zeroc00I/DontFeedTheAI, dataiku/kiji-proxy, packyme/privacy-filterOpen source2025–2026339–1,265 starAssorted LLM egress redaction proxies. None of them handle the agent sandbox.
stacklok/codegateOpen source2024-11791 stars, archivedA predecessor in local coding-agent gateways (hiding keys, handling privacy). It has stopped.
anthropics/sandbox-runtimeOpen source / big tech2025-107,086 starClaude Code's OS sandbox. Airlock's sandbox layer uses it directly.
OpenCode, Aider + Ollama / llama.cppOpen source2023–2025226k / 50k starRunning fully local means nothing leaks, but there's no "de-identify, then ask the cloud" step.
Code Airlock, calebfaruki/airlock, airlock.sorrel.systems (Mac App Store), airlock.lunareng.com, airlockrun/airlockOpen source / store2026-03 to 11Each has single-digit to 22 stars, with HN scores of 1–4.Name collisions: these do agent sandboxing, credential isolation, or policy control. None rewrite code for privacy.
Big-vendor features: Anthropic / OpenAI zero data retention (ZDR), Copilot content exclusion, Tabnine offline deploymentBig-company featuresAlready thereEnterprise standard.Enterprises handle "can code go to the cloud" with contracts and private deployments, not by rewriting the question.

No one combines "local model does the work + rewrite into an unrelated example before consulting + deterministic egress checks + fictional backstory." The combination is genuinely rare. It just hasn't produced any traceable real-world spread.

Differentiation

  • Where it really differs: (1) it doesn't send code snippets, it rewrites the question into a minimal reproducible example, which is a different approach from redaction proxies; (2) each project gets a fixed fictional backstory, so a prompt history can't be used to reconstruct what you're building; (3) CLAIMS.md spells out item by item what is and isn't guaranteed, a strong move for a privacy tool.
  • But that isn't why it's climbing. The real traffic signal is zero, and the star curve is identical to the author's three unrelated repos. The differentiation only makes the README look worth starring. The accounts doing the boosting don't read READMEs.

How many people can see it

Almost nobody knows about it yet. Revenue isn't public (it's free open source). HN, X, Reddit, and the press haven't mentioned it. It only appears on auto-aggregator sites like slopbucket, hahachat, GitHot, and githubrepo.cloud. Copycats: none. Several projects share the name, but they were built independently, not copied from this one.

What others can borrow

  • "Rewrite the question into a minimal reproducible example before asking a large model" plus "fictional backstory" is a viable direction for using frontier models in privacy-sensitive settings (enterprise code, healthcare, legal). The CLAIMS.md approach of stating guarantees item by item is also worth copying for privacy and security tools.
  • Lesson for us: steady, daily drip-fed boosting looks more "real" than a single-day spike, and it can fool recall rules that score on curve shape and fork ratio. Our recall should add a few checks: multiple repos from the same author growing at the same time, forkers with an unusually high fork share, and forkers overlapping with each other.

Still unclear

  • GitHub doesn't expose the star list, so whether the stars are bought can only be inferred from the forks (the two track each other steadily at a fixed ratio, so the likelihood is high, but I haven't verified individual accounts).
  • Did the author buy it and have others push it, or is an account pool using it as a "camouflage target"? It has only a couple dozen stars and isn't on any chart, so it's an unlikely pick for camouflage. Four repos from the same author boosted at the same time and pace suggests the author ordered it. No direct evidence.
  • The first 10-24 to 10-28 days' roughly 28 stars (36 when slopbucket indexed it) may include some real interest.

Sources

  • GitHub API (checked 2026-11-12): repos/lemonadesaltbagel/{airlock,veil,sill,crab,GR4-LUTSmith}, each repo's forks, the users/*/repos, starred, and graphql profiles of 38 forkers
  • Our github database: repo_profile, repo_day (owner = lemonadesaltbagel)
  • Our hackernews database: search for lemonadesaltbagel / airlock
  • x-radar: search for lemonadesaltbagel (0 results)
  • github.com/lemonadesaltbagel/Airlock (README.md, CLAIMS.md, packages/sandbox/package.json)
  • slopbucket.app/tools/airlock
  • Competitor star counts: GitHub API (2026-11-12)

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