An Open Agent Computer for ANY digital work.
⭐ Help us reach more developers and grow the holaOS community. Star this repo!
Website · Docs · Sign in · Quick Start
holaOS is an open agent computer for any digital work. It reimagines the computer as a shared environment where humans and AI agents operate side by side—with full access to the same browser, files, and apps, like collaborating with a powerful teammate that continuously learns how to work better with you. Instead of working across disconnected tools and contexts, everything lives in one place where memory, execution, and goals remain coherent, so work doesn’t reset or lose state. Agents operate continuously within this environment, evolving over time while remaining fully inspectable, and can be shaped by you through roles and templates to support consistent, repeatable ways of working.
For a fresh-machine bootstrap on macOS, Linux, or WSL, use the repository installer:
curl -fsSL https://raw.githubusercontent.com/holaboss-ai/holaOS/main/scripts/install.sh | bash -s -- --launchYou can also follow the manual path if you want to control each setup step.
If holaOS is useful or interesting, a GitHub Star would be greatly appreciated.
All deeper technical and product documentation lives at holaos.ai/docs:
| Section | What's Covered |
|---|---|
| Overview | The merged entry page for the environment-engineering thesis and system model |
| Quick Start | The fastest path to a working local desktop environment |
| Workspaces | How workspaces are created, switched, managed, and represented on disk |
| Environment Engineering | The core thesis behind holaOS and why the environment defines the system |
| Concepts | Core system vocabulary for workspaces, runtime, memory, and outputs |
| Workspace Model | Workspace contract, authored surfaces, and runtime-owned state |
| Memory and Continuity | Durable memory, continuity artifacts, and long-horizon resume behavior |
| Agent Harness | The stable harness boundary inside the runtime and how executors fit into it |
| Independent Deploy | Running the portable runtime without the desktop app |
| Build on holaOS | The code-true developer map for desktop, runtime, apps, templates, and validation paths |
| Start Developing | The local developer path for desktop and runtime validation |
| Runtime APIs | The runtime operational surface for workspaces, runs, streaming, and app lifecycle |
| Build Your First App | Building workspace apps on top of holaOS |
| Reference | Environment variables and supporting reference material |
You likely will not need this section because One-Line Install runs the same setup. Use Manual Install when you want to inspect or control each step. If you use the manual path, verify the usual prerequisites first:
git --version
node --version
npm --versionIf you use Codex, Claude Code, Cursor, Windsurf, or another coding agent, you can hand it the setup instructions in one sentence:
Run the holaOS install script from https://raw.githubusercontent.com/holaboss-ai/holaOS/main/scripts/install.sh. It should install git and Node.js 24.14.1/npm if they are missing, clone or update the repo into ~/holaboss-ai unless I specify another --dir, run desktop:install, create desktop/.env from desktop/.env.example if needed, run desktop:prepare-runtime:local and desktop:typecheck, and only run desktop:dev if I ask for --launch. If Electron cannot open, stop after verification and tell me the next manual step.
That handoff keeps the installation flow self-contained while leaving the detailed bootstrap steps in the repo-local INSTALL.md runbook.
This is the baseline installation flow for local desktop development.
- Install the desktop dependencies from the repository root:
npm run desktop:install- Create your local environment file:
cp desktop/.env.example desktop/.envIf you are following the repo exactly, keep the file close to the template and only change the values that your provider or machine needs.
- Prepare the local runtime bundle:
npm run desktop:prepare-runtime:local- If you want a quick validation pass before launching Electron, run:
npm run desktop:typecheck- Start the desktop app in development mode:
npm run desktop:devThe predev hook will validate the environment, rebuild native modules, and make sure a staged runtime bundle exists.
If you want to stage the runtime before opening the desktop app, there are two common paths:
Build from local runtime:
npm run desktop:prepare-runtime:localFetch the latest published runtime:
npm run desktop:prepare-runtimeUse the local path when you are actively changing runtime code. Use the published bundle when you want to verify the desktop against a known release artifact.
Use One-Line Install when you want the fastest path to a working local desktop environment. Use Manual Install when you need to inspect or control each setup step yourself.
If you want to contribute, start with Start Developing to get the local desktop and runtime loop working, then use Contributing for validation, commit, and review expectations.
- License: MIT. See LICENSE.
- Security issues: report privately to
admin@holaboss.ai. See SECURITY.md.