# OpenClaw

## Purpose

Manage an independent OpenClaw agent runtime while keeping its configuration inside OpenClaw.

## Audience

MSO operators using OpenClaw agents and channels.

## Requirements

An installed MSO host with a working user systemd bus. OpenClaw’s own provider and channel setup is separate.

## First step

Verify the host backend, then follow the OpenClaw section before starting its own onboarding.

## Outcome

A supported management path and a clear handoff to OpenClaw’s own configuration.

## Availability and limits

External reference. External software installed through its reviewed adapter; consult the runtime guide for current requirements.

## Links

- Read the OpenClaw setup path: https://mso.manef.dev/docs/managed-apps#openclaw
- Read official OpenClaw docs: https://docs.openclaw.ai/
- Project overview: https://manef.dev/catalog/openclaw

## User story and flow

As an OpenClaw user, I want to separate MSO host management from OpenClaw provider and channel configuration. Flow: catalog → brief → first action → outcome. Acceptance: A supported management path and a clear handoff to OpenClaw’s own configuration.

## Source evidence

- External publisher
- manef-web: public/catalog/v1.json, managed id openclaw

Related listings are discovery recommendations, not proof of operational integrations. This brief grants no authority to install software, connect accounts, access hosts or make purchases.