by holaboss-ai
The agent environment for long-horizon work, continuity, and self-evolution.
# Add to your Claude Code skills
git clone https://github.com/holaboss-ai/holaOSholaOS is the agent environment for long-horizon work. It gives agents a structured operating system made of runtime, memory, tools, apps, and durable state so they can work continuously, evolve over time, and stay inspectable across runs instead of resetting back to one-off task execution.
Quick Start is the shortest path to a working local Holaboss Desktop environment powered by holaOS. Use the one-line repository installer on a fresh machine, or follow the manual path if you want to control each setup step yourself.
curlbashThe installer bootstraps git, Node.js 22, and npm if they are missing. On Linux it may use sudo to install git.
For a fresh-machine bootstrap on macOS, Linux, or WSL, use the repository installer:
curl -fsSL https://raw.githubusercontent.com/holaboss-ai/holaboss-ai/main/scripts/install.sh | bash -s -- --launch
That installer:
git if it is missing22 plus npm if they are missing~/holaboss-ai by defaultdesktop/.env from desktop/.env.example if needednpm run desktop:installnpm run desktop:prepare-runtime:localnpm run desktop:typechecknpm run desktop:dev when you pass --launchAll deeper technical and product documentation lives at holaboss.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 | | Learning Path | The technical path through the docs after setup | | 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 | | Start Developing | The local developer path for desktop and runtime validation | | Contributing | The contributor workflow, validation expectations, and review guidance | | Runtime APIs | The runtime operational surface for workspaces, runs, and app lifecycle | | Independent Deploy | Running the portable runtime without the desktop app | | Agent Harness | The stable harness boundary inside the runtime and how executors fit into it | | Build Your First App | Building workspace apps on top of holaOS | | Troubleshooting | The common local runtime and desktop failure modes | | Workspace Experience | The desktop workspace surface built on top of holaOS | | Model Configuration | Providers, defaults, config precedence, and runtime model selection | | Reference | Environment variables and supporting reference material |
You really shouldn't need this as the one line install is doing the exact same thing. But oh well it's here in case you need it. If you are using the manual path instead, you can verify the usual prerequisites with:
git --version
node --version
npm --version
If you use Codex, Claude Code, Cursor, Windsurf, or another coding agent, you can hand it the setup instructions in one sentence:
Run the Holaboss install script from https://raw.githubusercontent.com/holaboss-ai/holaboss-ai/main/scripts/install.sh. It should install git and Node.js 22/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.
npm run desktop:install
cp desktop/.env.example desktop/.env
If you are following the repo exactly, keep the file close to the template and only change the values that your provider or machine needs.
npm run desktop:prepare-runtime:local
npm run desktop:typecheck
npm run desktop:dev
The 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:local
Fetch the latest published runtime:
npm run desktop:prepare-runtime
Use 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.
To learn more about how to contribute and how the system is structured, review Contributing. It is the canonical page for the contributor workflow and the build-on-holaOS development path.
admin@holaboss.ai. See SECURITY.md.No comments yet. Be the first to share your thoughts!