EN
Back to the archive

The archive · AI & Models · Product decision · 2026

Holaboss's holaOS: local-first agent workspace tops GitHub Trending, 11.1k stars

holaOS runs Claude Code, Codex and BYOK models in one shared-memory workspace; GitHub TypeScript Trending #1 on Aug 13, 2026, 11.1k stars by Sep 4.

Holaboss

The betDevelopers juggling agents with separate contexts will standardize on one local-first workspace where Claude Code, Codex and BYOK models share memory, tools and apps.Live

What the business is

holaOS is an open-source (modified Apache 2.0) Electron desktop workspace that runs Claude Code, Codex and Holaboss's own agent side by side over a shared runtime: memory stored as plain local files, shared tools, browser access, HolaApps and 100+ integrations via MCP and OAuth, with built-in models (Claude Opus 5, GPT 5.6, Kimi K3, GLM 5.2) or bring-your-own keys.

How it started

Holaboss (holaboss-ai), led by Jeffrey Li, created the repository on 2026-03-22 after watching developers keep three or four agent CLIs open with none knowing what another had done. The fix was a single desktop workspace where every agent reads and writes the same memory, tools and integrations: close the app and return a week later and the context is still there, stored as ordinary local files the user can open and edit.

What happened

holaOS Desktop Beta 0.1 landed on 2026-05-12 with a dashboard, sub-agents and multi-workspace isolation. The project then went viral in mid-August 2026: it held the #1 spot on GitHub's TypeScript Trending chart on 2026-08-13 and stayed in the TypeScript top slot through Aug 15, adding over 1,200 stars in 72 hours with a single-day peak of 769. Totals climbed from 7,045 stars on 2026-08-14 (7.3k with 637 forks per TrendForge) to roughly 10.6k by 2026-08-22 and 11.1k by 2026-09-04. The launch also drew scrutiny: the license is modified Apache 2.0, free inside one organization but requiring a separate commercial license to host holaOS as a service or embed it in a product; a Korean technical review on 2026-08-16 found the '100+ integrations' claim unverifiable in the code, noted OAuth flows route through third-party Composio rather than fully self-hosted connectors, and flagged an open issue about whether memory leaks between workspaces.

How it ended up

Still live in beta as of September 2026 at roughly 11.1k GitHub stars; Holaboss has disclosed no funding, revenue or pricing, and the bet is unproven - the surge is GitHub adoption, not yet a business, and the review noted zero Hacker News threads about holaOS as of 2026-08-16.

Background

holaOS is the bet that the pain of the 2026 agent boom is fragmentation, not model quality. Developers run Claude Code, Codex and other agent CLIs in separate terminals, and none of them knows what the others did; Holaboss, led by Jeffrey Li, answered with an open-source desktop workspace in which every agent shares the same local-file memory, tools, browser and integrations. Its slogan is 'agents swappable, context persists': start a task in Codex, finish it in Claude Code, and the markdown-based memory travels with the project.

The technical wedge is a shared kernel rather than another agent framework: harness adapters let Claude Code, Codex and a built-in holaOS agent run on one runtime, with HolaApps rendering live UIs alongside the agents and models built in or supplied by the user's own API keys. The repository appeared on 2026-03-22, shipped Desktop Beta 0.1 on 2026-05-12, and went viral in August 2026 - #1 on GitHub's TypeScript Trending chart on 2026-08-13, 1,200+ stars in 72 hours, a 769-star single day, and totals climbing from 7,045 stars on Aug 14 to about 11.1k by Sep 4.

The scrutiny it attracted is as instructive as the growth. The 'modified Apache 2.0' license permits internal use but requires a separate commercial license to host or embed holaOS, the marketing claim of 100+ integrations could not be confirmed in the code, and OAuth integration flows route through the third-party Composio platform rather than being fully self-hosted, which sits uneasily with the local-first pitch. A Korean technical review of 2026-08-16 also found no Hacker News discussion yet and an open issue about whether memory and preferences leak across workspaces.

As of early September 2026 the project is live beta software with real developer adoption but no disclosed company funding, revenue or pricing - a reminder that GitHub Trending measures attention, and converting attention into a business is a separate, unproven bet.

What has to be true

  • The problem was felt by every multi-agent developer in 2026: context, tools and credentials lived in silos, so a shared workspace addressed a real and growing pain rather than a hypothetical one.
  • Local-first memory stored as editable files was a differentiated answer to the trust problem - users could see and control exactly what the agents remembered.
  • BYOK and multi-model support tapped developer fatigue with vendor lock-in just as Anthropic and OpenAI were pushing their own agent ecosystems.
  • The open-source, self-hosted form lowered the barrier to trying it, letting a small unfunded team ride GitHub's distribution instead of buying ads.
  • The unsolved parts were equally real: no revenue model, an unverifiable integrations count, a license boundary complicating the open-source story, and zero Hacker News traction as of mid-August 2026.

What can be applied

A category can go viral on GitHub before it has a business: what converts a trending repo into a company is verified integrations, a clear license boundary and proof of paid usage, not star velocity.

Aftermath

As of 2026-09-05 holaOS remains live in beta at roughly 11.1k GitHub stars (Star History, 2026-09-04), having trended for four consecutive days in mid-August with a best all-languages rank of #7 and a #1 TypeScript rank on 2026-08-13 through 08-15. Holaboss has not disclosed funding, revenue or pricing; the license requires a commercial agreement for hosting or embedding the product, and open issues remain about memory isolation between workspaces. The company's next test is whether it can convert a GitHub-star surge into verified paid usage before the attention fades.

Sources

spotted an error? The archive wants to know.

Your turn

You just read one. Describe what you are building, and see who is betting on the same thing.

Free account · 3 free questions · no card

Related cases