LIFEHUBBER
Theme

AI Resources

holaOS

GitHub stars: 11.2K GitHub forks: 723 Last pushed August 21, 2026: Pushed 21d ago
Stats from GitHub

holaOS is a local-first desktop workspace where you and coding agents can work from the same projects, memory, files, tools, skills, and apps.

It can run Claude Code, Codex, or the built-in holaOS agent, connect to more than 100 documented integrations, and use built-in model access or your own provider keys. Local-first describes the workspace, not every connection: selected models and integrations can still send content to outside services. The shared workspace keeps project context and tools that would otherwise be scattered across separate chats and apps. Use this as a first read, not a recommendation. Open the original project before trusting details like terms, limits, privacy, cost, setup, or safety.

What it is

One workspace for you and your agents

Projects can keep their files, memory, tools, skills, apps, and working history together, so a later session does not have to begin from an empty chat.

Why it stands out

Memory, workspaces, and sub-agents together

Claude Code, Codex, and the built-in agent can work inside the same local-first environment, with integrations and model choices available from one place.

Availability

Public desktop repository and enterprise paths

The public repository includes desktop setup and development instructions. holaOS also describes an enterprise path, so check which edition and model-access route fit before committing work to it.

Why it matters

What makes it useful

Agent work often loses its context when the chat ends. holaOS keeps projects, memory, files, tools, and apps in one workspace that both a person and supported coding agents can use.

Notable points

What stands out

The project currently documents Claude Code, Codex, and its built-in agent, more than 100 integrations, built-in frontier-model access, bring-your-own-key options, desktop installation, and an enterprise offering.

Before using

What to review

Which desktop edition, operating system, model-access route, and setup steps fit the intended work.

What stays in the local workspace and what selected models or integrations may send to outside services.

Whether the work needs a shared home for several agents or only a narrower coding assistant or automation.

Reader fit

Who may find it relevant

People who want ongoing projects, memory, tools, skills, and apps available to more than one coding agent.

Builders comparing local-first desktop workspaces with separate agent applications.

Less relevant for readers looking mainly for a model checkpoint, a small chatbot, or a narrow browser automation helper.

Editorial note

Why LifeHubber lists it

LifeHubber lists holaOS for its unusually complete shared-workspace idea: people and several coding agents can use the same projects, memory, tools, skills, and apps. That helps readers decide whether their work needs a continuing desktop home or a narrower agent in its own window.

Source links

Source materials

Reader note

Before relying on this entry

LifeHubber lists entries to help readers inspect AI projects, not to endorse them or prove they are safe, suitable, accurate, maintained, or right for a specific use. We do not verify every entry in depth. Before relying on anything listed, review the original materials, terms, privacy practices, limits, and risks that matter for your situation.

What to explore next

Compare where ongoing agent work should live.

holaOS brings people, coding agents, memory, files, skills, apps, and integrations together in one local-first desktop workspace, while selected models and integrations may still call outside services.

Advertisements

Advertisements

For project maintainers

Listed here? You can use the badge.

If you maintain a project with a current LifeHubber listing, you may add the optional “Listed on LifeHubber AI Resources” badge to its README, docs, or website. No introduction or permission request is needed.

See what’s moving