← Back to archive

Repo of the Day

GitHub - holaboss-ai/holaboss-ai: OSS core runtime and desktop workspace stack for Holaboss

Published: Oct 6, 2026

Open repository ↗

OSS core runtime and desktop workspace stack for Holaboss - holaboss-ai/holaboss-ai

Summary

holaOS is an open-source Electron desktop workspace written in TypeScript that lets engineers run AI agents (Claude Code, Codex, or its own) against existing tools, chat platforms, and local files through the Model Context Protocol (MCP) and an in-workspace app marketplace. It is described as local-first, with workspace files, memory, embeddings, and session history kept on the developer's own disk, and ships with 100+ integrations plus bring-your-own-key support for OpenAI, Anthropic, and OpenAI/Anthropic-compatible endpoints.

What it is useful for

holaOS is useful when engineers want one desktop surface where an agent acts on real systems instead of producing chat transcripts. According to the README, it can connect to chat tools like Slack, Feishu, DingTalk, and WeChat; link services such as Gmail, Notion, GitHub, and Linear via one-click OAuth; add any MCP server for additional tools; and drive a signed-in browser for click-and-extract flows. Outputs land as real files (.xlsx, .pptx, .docx) rather than text-only replies. Engineers who need to keep workspace data on their own machines get per-tool, per-scope approvals and a memory layer stored as plain files they can open and edit. Teams standardized on Claude Code or Codex can keep that agent while sharing the same memory, integrations, and apps, so switching agents doesn't mean rebuilding setup. Scheduled or triggered automations (digests, monitors, reports) are also documented.

How engineers can use it

The README documents a one-line bootstrap for macOS, Linux, or WSL:

curl -fsSL https://raw.githubusercontent.com/holaboss-ai/holaOS/refs/heads/main/scripts/install.sh | bash -s -- --launch

For a manual path it requires git, node, and npm (Node pinned via .nvmrc), then:

  1. npm run desktop:install
  2. cp apps/desktop/.env.example apps/desktop/.env
  3. npm run desktop:prepare-runtime:local
  4. npm run desktop:typecheck (optional validation)
  5. npm run desktop:dev

A predev hook validates the environment and rebuilds native modules before Electron opens. If launch fails, stopping after step 4 surfaces the next manual step as documented in INSTALL.md. The license is a modified Apache 2.0 with extra commercial-distribution and branding conditions, so teams planning to redistribute should read LICENSE first.