> For the complete documentation index, see [llms.txt](https://docs.dextoros.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dextoros.app/fleet-and-console/console-commands.md).

# Console commands

Every command the console accepts, what it replies and the errors to expect.

{% hint style="warning" %}
**Draft.** Some details on this page are still being confirmed and may change. Questions? Email <info@dextoros.app>.
{% endhint %}

Select a robot, type a command and press **Send**. Type `help` to see what a robot accepts. Use the up and down arrow keys to cycle through your last 20 commands.

Commands aren't case-sensitive, and extra spaces are ignored.

## Commands by robot type

A robot only accepts commands its body supports.

| Command                          | Arms | Mobile robots | Legged robots |
| -------------------------------- | ---- | ------------- | ------------- |
| `help`                           | Yes  | Yes           | Yes           |
| `status`                         | Yes  | Yes           | Yes           |
| `pause` / `resume`               | Yes  | Yes           | Yes           |
| `home`                           | Yes  |               |               |
| `gripper open` / `gripper close` | Yes  |               |               |
| `move_to <bay>`                  |      | Yes           | Yes           |
| `dock`                           |      | Yes           | Yes           |

## Command reference

<details>

<summary><code>help</code></summary>

Lists the commands the selected robot accepts.

```
> help
AMR-11 accepts status, move_to B3, dock, pause, resume
```

Works even when the robot is offline.

</details>

<details>

<summary><code>status</code></summary>

Reports the robot's current activity and key telemetry.

```
> status
Moving to B3. Battery 64%, bay b3, 38 ms
```

For an arm, status reports motor temperature, cycle time and gripper state instead. Works even when the robot is offline, in which case it shows when the robot was last seen.

</details>

<details>

<summary><code>pause</code> and <code>resume</code></summary>

`pause` stops the robot where it is and replies `Paused`. `resume` continues and replies `Resumed`.

If the robot is already paused, `pause` replies `Already paused`. If it isn't paused, `resume` replies `Nothing to resume`.

</details>

<details>

<summary><code>home</code> (arms)</summary>

Returns every joint to its home position. Replies `Homing all joints`, then logs `Reached home position`.

Robots without an arm reply `<robot> has no arm to home`.

</details>

<details>

<summary><code>gripper open</code> and <code>gripper close</code> (arms)</summary>

Opens or closes the gripper. Replies `Gripper open` or `Gripper closed`.

Any other argument replies `Use gripper open or gripper close`. Robots without an arm reply `<robot> has no gripper`.

</details>

<details>

<summary><code>move_to &#x3C;bay></code> (mobile and legged)</summary>

Drives or walks the robot to a bay. Replies `Moving to bay B3`, then logs `Arrived at bay B3`.

A bay is a row letter and a column number. In the demo fleet, bays run from `A1` to `D9`.

| Problem           | Reply                                              |
| ----------------- | -------------------------------------------------- |
| No bay given      | `Add a bay, for example move_to B3`                |
| Bay doesn't exist | `Unknown bay "E4". Bays run from A1 to D9`         |
| Sent to an arm    | `<robot> is a fixed arm and cannot drive to a bay` |

</details>

<details>

<summary><code>dock</code> (mobile and legged)</summary>

Sends the robot to its dock to charge. Replies `Heading to the dock`, then logs `Docked. Charging` and later `Fully charged`.

If the robot is already charging it replies `Already on the dock`. Arms reply `<robot> is a fixed arm with no dock`.

</details>

## Replies and errors

Every accepted command replies with what the robot is doing and how quickly it accepted the command:

```
Moving to bay B3. Accepted in 38 ms
```

| Situation        | Reply                                                          |
| ---------------- | -------------------------------------------------------------- |
| Unknown command  | `Unknown command "jump". Type help to see what AMR-11 accepts` |
| Robot is offline | `HUM-03 is offline, so nothing was sent. Last seen 14 min ago` |

{% hint style="info" %}
Only `help` and `status` work while a robot is offline. Other commands are not queued; send them again once the robot reconnects.
{% endhint %}


---

# 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.dextoros.app/fleet-and-console/console-commands.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.