> For the complete documentation index, see [llms.txt](https://docs.miuro.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.miuro.ai/miuro-claw/how-to-interact-with-miuro-claw.md).

# How to Interact with MIURO Claw

MIURO Claw currently interacts with users mainly through the following methods:

### 1. Through Miuro Web / App

After logging in, users can directly chat with Cloud Claw for quick creation.

### 2. Through MiuroBox Devices

After purchasing the corresponding MiuroBox model, the device will run the full OpenClawRunner, enabling local agent orchestration capabilities.

### 3. Wake-Up and Remote Access

The device remains online through MQTT. When users initiate a creation request from the web or app, the system automatically wakes up the device-side Claw for processing.

### Simple Usage Flow Example

Enter a creative prompt in the app → Cloud Claw responds quickly → when complex local processing is required, the request is automatically routed to your MiuroBox → local audio processing and orchestration are completed → the result is returned.

Start here: <https://miuro.ai/>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.miuro.ai/miuro-claw/how-to-interact-with-miuro-claw.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.