# How to Get Support for holaOS: Community and Hosted Options Explained

> Find holaOS support solutions. Use GitHub issues for open-source bugs and runtime problems. Contact Holaboss AI directly for authentication, billing, and backend services.

- Repository: [holaboss.ai/holaOS](https://github.com/holaboss-ai/holaOS)
- Tags: how-to-guide
- Published: 2026-08-15

---

**To get support for holaOS, use GitHub issues for open-source bugs and runtime issues, or contact Holaboss directly for authentication, billing, and backend service problems.**

When working with holaOS, the open-source operating system from holaboss-ai, knowing which support channel to use ensures your issue reaches the right team quickly. The repository maintains clear boundaries between community-driven assistance for the codebase and proprietary support for hosted services. Understanding how to get support for holaOS starts with identifying whether your problem involves the local runtime or Holaboss backend infrastructure.

## Support Channels for holaOS

According to the [`SUPPORT.md`](https://github.com/holaboss-ai/holaOS/blob/main/SUPPORT.md) file in the holaboss-ai/holaOS repository, the project maintains two distinct support tracks designed to route issues to the appropriate maintainers.

### Open-Source Community Support

For problems involving the OSS codebase—such as the desktop application, runtime, packaging systems, or workspace flows—open a **GitHub issue** in the [holaOS repository](https://github.com/holaboss-ai/holaOS/issues). The issue template requires specific diagnostic information including the exact command executed, host platform details, relevant logs or stack traces, and whether the flow was local-only or required Holaboss services. This track covers pure open-source concerns where the community can inspect and modify the code.

### Hosted Holaboss Support

For issues requiring access to Holaboss back-end services—including sign-in problems, authentication-protected features, or billing inquiries—**contact Holaboss support directly** through their Discord server, X account, or the "Help Center" within the hosted product. The OSS repository explicitly does not handle these cases, as they involve proprietary infrastructure outside the open-source codebase.

## Filing an Effective GitHub Issue

When submitting to the community support channel, following a systematic workflow increases the likelihood of a rapid resolution.

1. **Search existing issues** – Verify the problem hasn't already been reported in the GitHub tracker.
2. **Gather diagnostic data** – Execute the failing command and copy the exact output, noting your operating system and Node.js/NPM versions (`node --version`, `npm --version`).
3. **Create a new issue** – Use the provided template, paste your collected data, and describe precise steps to reproduce the behavior.
4. **Provide a minimal reproducible repo** – For complex bugs, create a small repository that demonstrates the issue to help maintainers triage faster.

You can streamline issue creation using the **GitHub CLI** to ensure all required fields are populated programmatically:

```bash

# Install the GitHub CLI if you don't have it

brew install gh   # macOS

sudo apt install gh   # Debian/Ubuntu

# Authenticate (you'll need a GitHub token)

gh auth login

# Create a new issue with a title and body

gh issue create \
  --title "Desktop app crashes on start on Windows 11" \
  --body-file - <<'EOF'
**Command run**

```bash
npm run desktop:dev

```

**Platform**  
Windows 11, Node v20.12.0, npm v10.5.0

**Logs / stack trace**  
<paste the console output>

**Is this a local-only flow?**  
Yes – no external Holaboss services are involved.

**Steps to reproduce**  
1. Clone the repo
2. Run `npm install`
3. Run `npm run desktop:dev`
EOF

```

## Key Support Documentation Files

The holaOS repository contains several critical files that define the support process and provide troubleshooting context:

- **[`SUPPORT.md`](https://github.com/holaboss-ai/holaOS/blob/main/SUPPORT.md)** – Defines the dual support tracks and specifies required information for GitHub issues.
- **[`README.md`](https://github.com/holaboss-ai/holaOS/blob/main/README.md)** – Provides project overview, quick-start commands, and links to documentation as noted in lines 27-35.
- **[`INSTALL.md`](https://github.com/holaboss-ai/holaOS/blob/main/INSTALL.md)** – Contains the complete installation run-book covering prerequisites, one-line bootstrap, and manual setup steps.
- **[`SECURITY.md`](https://github.com/holaboss-ai/holaOS/blob/main/SECURITY.md)** – Outlines the process for responsibly disclosing security vulnerabilities.
- **`docs/` directory** – Houses design documents and reference material that may clarify architectural questions.

When filing community issues, include direct links to relevant source files (e.g., `runtime/api-server/src/...`) so maintainers can immediately locate the code under discussion.

## Summary

- **holaOS provides two support channels**: GitHub issues for open-source code problems and Holaboss direct contact for hosted service issues.
- **Community support covers** the desktop app, runtime, packaging, and local workspace flows via the GitHub issue tracker.
- **Hosted support handles** authentication, billing, and backend service problems through Holaboss Discord, X, or the Help Center.
- **Required issue data includes** exact commands, platform details, Node/NPM versions, and stack traces.
- **Key files**: [`SUPPORT.md`](https://github.com/holaboss-ai/holaOS/blob/main/SUPPORT.md), [`README.md`](https://github.com/holaboss-ai/holaOS/blob/main/README.md), [`INSTALL.md`](https://github.com/holaboss-ai/holaOS/blob/main/INSTALL.md), and [`SECURITY.md`](https://github.com/holaboss-ai/holaOS/blob/main/SECURITY.md) contain definitive support policies.

## Frequently Asked Questions

### What's the difference between community and hosted support for holaOS?

Community support via GitHub issues handles problems with the open-source codebase itself, including the desktop application, runtime, and packaging systems. Hosted support manages issues requiring Holaboss backend infrastructure, such as user authentication, billing systems, and proprietary cloud services. The [`SUPPORT.md`](https://github.com/holaboss-ai/holaOS/blob/main/SUPPORT.md) file explicitly directs users to the appropriate channel based on whether the issue is local-only or service-dependent.

### Where do I report security vulnerabilities in holaOS?

Security-related concerns should never be filed as public GitHub issues. Instead, consult the [`SECURITY.md`](https://github.com/holaboss-ai/holaOS/blob/main/SECURITY.md) file in the repository root for responsible disclosure procedures. This document provides specific contact information and protocols for privately reporting vulnerabilities to the holaOS security team.

### What information should I include in a GitHub issue?

According to the [`SUPPORT.md`](https://github.com/holaboss-ai/holaOS/blob/main/SUPPORT.md) template, you must provide the exact command you ran, your host platform (OS and version), relevant logs or stack traces, output from `node --version` and `npm --version`, and clarification on whether the workflow requires Holaboss services or runs locally. Including links to specific source files (e.g., within `runtime/` or `desktop/`) helps maintainers locate the relevant code immediately.

### How do I get help with installation problems?

For installation support, first consult [`INSTALL.md`](https://github.com/holaboss-ai/holaOS/blob/main/INSTALL.md), which contains detailed prerequisites and bootstrap instructions referenced in [`README.md`](https://github.com/holaboss-ai/holaOS/blob/main/README.md) lines 27-35. If the installation guide doesn't resolve your issue and the problem involves local setup (not hosted service authentication), file a GitHub issue including the output of your installation commands and your environment details.