---
title: "holaOS Ships Beta 0.1 Giving AI Agents Persistent Memory Across Workstreams"
subtitle: "holaOS Beta 0.1 ships persistent multi-workspace agents with shared memory, sub-agents, and 100+ integrations — open-source and free to start"
url: "https://alphasignal.ai/news/holaos-ships-beta-0-1-giving-ai-agents-persistent-memory-across-workstreams"
author: "AlphaSignal Newsroom"
author_url: "https://alphasignal.ai/editorial-team"
company: "AlphaSignal"
company_url: "https://alphasignal.ai/company/alphasignal"
published: "2026-08-10T01:44:53.000Z"
updated: "2026-08-10T07:10:25.424Z"
type: "Repo"
topics:
  - "Agents"
  - "Open Source"
subtopics:
  - "Computer Use"
  - "Agent Frameworks"
  - "Multi Agent"
upvotes: 102
source_url: "https://github.com/holaboss-ai/holaOS"
comments: 0
truncated: true
---

# holaOS Ships Beta 0.1 Giving AI Agents Persistent Memory Across Workstreams

> holaOS Beta 0.1 ships persistent multi-workspace agents with shared memory, sub-agents, and 100+ integrations — open-source and free to start

Most AI agents are built for a single conversation. You ask, they answer, and the next session starts from scratch. [holaOS](https://github.com/holaboss-ai/holaOS) is betting that agent value only compounds when they can pick up where they left off across days, weeks, and multiple parallel workstreams. Beta 0.1 is the first release that makes that concrete.

## The persistence problem

Every Claude Code session starts clean. That works for a 15-minute task. It breaks down when you're running a multi-step research agent, an automated refactor across a large codebase, or any workflow where the agent needs to accumulate knowledge between runs.

The root issue is that most agent setups have no persistent operating environment. The agent executes, terminates, and the next invocation knows nothing about the previous one. You can work around this with custom scripts, checkpointing logic, and memory stores bolted on manually, or you can use a tool designed for exactly this.

holaOS gives agents a structured operating system built from runtime, memory, tools, apps, and durable state so they can work continuously, evolve over time, and stay inspectable across runs.

## What shipped in Beta 0.1

Beta 0.1 adds a workstream management layer on top of the Agent Computer foundation. Three capabilities define this version:

* **Multi Workspaces:** Create isolated workspaces for distinct tasks such as competitive tracking or content creation. Each workspace preserves its own context, files, and previous outputs. A content pipeline shares no state with an inbox assistant.

_Preview only. Full text requires an AlphaSignal Pro account._

## Sources

- [holaboss-ai/holaOS — GitHub](https://github.com/holaboss-ai/holaOS)
- [holaOS 0.1 launches as AI Workstream Management Layer — TestingCatalog](https://www.testingcatalog.com/holaos-0-1-released-as-ai-workstream-management-layer/)
- [holaOS Desktop Beta 0.1 Released for Long-Term AI Work — KuCoin](https://www.kucoin.com/news/flash/holaos-desktop-beta-0-1-launched-for-long-term-ai-work)
- [holaOS: Agent Environment for Long-Horizon Work with MCP — dudarik.com](https://dudarik.com/en/blog/holaos-mcp/)
- [holaOS Quick Start Docs](https://www.holaos.ai/docs/getting-started/quick-start)