Our take
Activeregular commits and releases- Activity
- 66
- Community
- 33
- Issues
- 54
- Pull requests
- 81
+0 stars in the last 8 days
- Merges more pull requests than 89% of the projects we track
holaOS is an actively developed, ambitious desktop agent workspace, but its concentrated contributor base and modified license make careful evaluation important for organizational adoption.
Good fit if
- You want a customizable desktop environment where agents, apps, and integrations work side by side.
- Keeping workspace files and memory local is a priority, and you are comfortable running a Node.js 24-or-newer development setup or using the desktop app.
- You can review the modified Apache 2.0 terms and accept their additional conditions.
Look elsewhere if
- You need a conventional hosted chat product rather than a configurable local-first workspace.
- Your team requires a permissive, unmodified Apache 2.0 license or a broad, distributed maintainer base.
- You require documented automated tests before evaluating a project; the repository's supplied project facts report none.
All health signals
| Last commit | 2026-08-21 (2 months ago) |
|---|---|
| Commits, last 90 days | 100+ |
| Releases, last 12 months | 1 (latest latest, 2026-08-06) |
| Contributors | 7 (top contributor: 80% of commits) |
| Issues closed, last 90 days | 3+ (typically closed in 4 days) |
| Pull requests merged, last 90 days | 83 (typically merged in 0 days) |
| Project age | 7 months |
Checked on 2026-10-10 with the GitHub API.
Overview
holaOS is a TypeScript and Electron desktop workspace for configuring AI agents around the apps, chat tools, files, and systems a team already uses. Rather than making chat the whole interface, it lets agents work alongside interactive apps and share tools and memory across agent choices such as Claude Code, Codex, or its built-in agent.
Its local-first design stores workspace files and memory on the user's machine. The project is aimed at teams that want to connect and customize agent workflows without moving their work context into a hosted workspace. It also supports model-provider keys supplied by users.
Key Features
- Run agents alongside interactive apps in a desktop workspace, with the ability to observe and take over their work.
- Connect integrations, chat tools, and MCP servers so agents can work with existing systems.
- Share tools, skills, apps, and memory across supported agents.
- Store memory as local files that users can inspect and edit.
- Use built-in model access or supply keys for supported providers and compatible endpoints.
- Use an agent-driven browser, scheduled or triggered automation, and generated office documents.
Use Cases
- Teams that need agents to work with context in Slack or other supported chat tools, rather than relying on someone to summarize conversations.
- Developers who want to use Claude Code, Codex, or the built-in agent in a shared workspace with common tools and memory.
- Users who want an agent to interact with an app or browser while they can see and take over the work.
- Organizations exploring local-first agent workflows across existing systems, with user approval controlling access to tools and data.
What you need
Detected in the repository
- Node.js >=24 (from package.json)
- Automated checks on GitHub Actions
Getting Started
For a fresh-machine bootstrap on macOS, Linux, or WSL, the README provides this installer:
curl -fsSL https://raw.githubusercontent.com/holaboss-ai/holaOS/refs/heads/main/scripts/install.sh | bash -s -- --launch
See the README for manual installation and setup details.
License in Plain Words
No standard license was detected. Without a license, the default copyright rules apply: you may read the code, but not reuse it. Check the repository or ask the authors.
Alternatives
- lobehub: LobeHub is a web app for creating and scheduling agents, while holaOS centers on a customizable desktop workspace alongside existing apps and tools.
- maka: Maka emphasizes agent execution, evaluation, and an auditable event log; holaOS emphasizes integrating agents with apps, files, and chat tools.
- Kun: Kun focuses on shared tasks and approvals across a desktop GUI and terminal TUI, while holaOS brings agents alongside apps and integrations.
- synara: Synara is focused on coding-agent sessions with project files, terminals, previews, and Git review, while holaOS targets a broader app-integrated workspace.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| holaOS | TypeScript | – | 11.4k | Active |
| lobehub | TypeScript | – | 83.1k | Active |
| maka | TypeScript | Apache-2.0 | 5.7k | New |
| Kun | TypeScript | Other | 6.3k | New |
| synara | TypeScript | MIT | 2k | Active |
Considerations
The repository is active, with regular commits and a recent release, but most contributions come from one contributor. That concentration may matter to teams assessing continuity and support; issue handling and merged changes are also worth reviewing against your needs.
The README describes local storage for workspace data and memory, but using model services may still involve sending prompts to the chosen provider. Review provider settings and the project's security documentation before connecting sensitive systems. The project requires Node.js 24 or newer for the documented development setup, and the supplied project facts do not report automated tests. The license is modified Apache 2.0 with additional commercial-distribution and branding conditions, so check the license before redistributing or adopting it commercially.
Found this useful?
Share it with someone who would like holaOS.