Holaboss
Skip to content

Overview

At Holaboss, our vision is that long-horizon AI work should be defined by the environment around the agent, not by the harness alone. A clearly defined environment gives the agent a stable workspace, memory, continuity model, and capability surface, creating the conditions for controlled, sample-efficient learning and self-improvement over time. That vision led us to build holaOS, the open-source environment layer that now powers Holaboss Desktop. Holaboss Desktop is the operator-facing desktop application built on top of holaOS, giving you the local product surface for installing, inspecting, and running workspaces.

From harness engineering to environment engineering

Traditional agent systems over-focus on the harness:

  • provider and model routing
  • prompt assembly and context packing
  • tool schemas and tool execution
  • streaming
  • retries, fallback, and transport behavior
  • executor and sandbox wiring

Those things still matter, but they are not the primary artifact in holaOS.

In holaOS, the primary artifact is the environment around the agent. The shift matters because long-horizon work needs more than a strong executor. It needs a stable operating context that persists across runs and gives learning, continuity, and capability control a consistent place to live.

That is the difference between harness engineering and environment engineering: the harness remains one subsystem, but the environment becomes the durable contract.

The environment contract

holaOS makes that environment explicit by turning it into concrete, inspectable surfaces:

  • workspace structure
  • memory and recall surfaces
  • continuity artifacts and runtime state
  • controlled self-improvement behavior
  • capability projection
  • harness boundary
  • packaging and portability

Concretely, that contract includes:

  • workspace.yaml, AGENTS.md, skills/, and apps/ as the authored workspace surface
  • durable memory under memory/
  • runtime continuity and metadata under state/runtime.db
  • request snapshots, compaction boundaries, and session-memory projections
  • capability manifests and prompt assembly for each run
  • the evolve loop that promotes durable memory and candidate skills over time

This is why holaOS is better described as environment engineering than harness engineering.

Relationship to Holaboss Desktop

Holaboss Desktop is the first product surface built on top of holaOS.

The desktop app provides:

  • the operator UI
  • local setup and packaging flows
  • model configuration and provider management
  • workspace creation and inspection
  • a polished shell for the underlying environment

The desktop is important, but it is not the whole story. The deeper technical story lives in the environment system underneath it.

Start with the page that matches your goal: