holaOS

holaOS turns recurring, context-heavy work into running AI work-streams.

Create a workspace for the work you keep restarting in chat — weekly research, content production, customer feedback, launch planning, or client delivery. Kickoff turns that work into goals, context, rules, sources, a first artifact, and the next run. When you review the output and correct it, those corrections become visible rules so the next run starts smarter than the last.

Under the hood, holaOS is an open agent computer: a shared environment where agents can use the same browser, files, apps, tools, and runtime state you do. The difference in Beta 0.1 is the product loop. Instead of giving an agent one disposable session, you give each recurring work-stream a living workspace with its own memory, history, outputs, and control surface.

Use it for work that unfolds over time: research that changes every week, content that needs your voice, feedback that should become product decisions, launches with many moving parts, and client work that needs isolated context. The first win is not configuring a blank agent. The first win is seeing a workspace created from a real recurring job, with a reviewable output and a next run already set up.

What changed in Beta 0.1

• Multi Workspaces keep each long-running work-stream in its own context, rules, tools, files, history, and next run.
• Sub Agents help complex work move forward in parallel — research, drafting, verification, synthesis — without manually juggling chats.
• Dashboards for active visualization that you and your agent maintain

Examples

Try holaOS with one recurring job you keep restarting:

• Research Radar — track competitors, market shifts, funding news, and customer signals; ship a weekly brief with sources and deltas.
• Content Engine — turn founder notes into X posts, newsletter drafts, and video hooks while saving edits as style rules.
• Customer Voice — group feedback from calls, support, Discord, and X into a product action board.
• Launch / Campaign Workstream — generate a campaign calendar, channel briefs, asset gaps, daily metrics, and retrospective.
• Client Delivery Loop — create an isolated workspace for each client while reusing your delivery playbook.

Table of Contents

• Quick Start
  • What you need
  • One-Line Install
• Documentation
• Manual Install
  • One-Line Agent Setup
• Contributing
• OSS Release Notes

Quick Start

One-Line Install

For a fresh-machine bootstrap on macOS, Linux, or WSL, use the repository installer:

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

You can also follow the manual path if you want to control each setup step.

Star the Repository

Documentation

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 |

Manual Install

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 --version

One-Line Agent Setup

If 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/refs/heads/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 apps/desktop/.env from apps/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.

1. Install the desktop dependencies from the repository root:

npm run desktop:install

2. Create your local environment file:

cp apps/desktop/.env.example apps/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. The canonical path is apps/desktop/.env. Existing legacy desktop/.env files are still accepted for now, but new setups should use apps/desktop/.env.

3. Prepare the local runtime bundle:

npm run desktop:prepare-runtime:local

4. If you want a quick validation pass before launching Electron, run:

npm run desktop:typecheck

5. Start the desktop app in development mode:

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 r