> For the complete documentation index, see [llms.txt](https://docs.hello-robot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hello-robot.com/stretch4_docs/working-with-stretch/getting-started/demo-web-teleoperation.md).

# Demo - Web Teleoperation

This documentation is currently in beta. Please proceed carefully, and if you run into issues or need additional information, reach out to Hello Robot directly for support.

A common use case for Stretch is to operate the robot remotely, either on a local network or across the Internet. Hello Robot's Web Teleop software makes this possible, allowing an operator to control the robot while streaming the view through any of the robot's cameras. In the following demo, you will learn how to launch and use the Web Teleop demo that comes with Stretch.

### Launching the Demo

On the robot, Web Teleop can be launched in two ways.

{% stepper %}
{% step %}

### Command Line

Open a Terminal window and type the following to navigate to the correct folder:

```
colcon_cd stretch4_web_teleop
```

Then to launch the demo:

```
./launch_interface.sh
```

{% endstep %}

{% step %}

### Stretch Tray

Click the Hello Robot icon at the top right of the screen, then select "Launch Web Teleop" from the dropdown menu. A Terminal window will open and launch the demo.
{% endstep %}
{% endstepper %}

When the demo launches, the URL for connecting to the robot will be displayed at the bottom of the window (example: <https://192.0.2.1/operator>). Record this for use in the next step.

### Connecting over a local network

On a mobile phone or PC that is connected to the same Wi-Fi network as Stretch, open a web browser (Firefox recommended for best compatibility) and type in the URL as it appeared in the robot's Terminal window. This will connect you to the robot.

{% hint style="info" %}
You might receive an 'invalid certificate' error that asks you if you want to proceed with the connection - this is expected, and it is OK to proceed.
{% endhint %}

After a few seconds, you should see the Web Teleop interface display in your browser:<br>

\#Insert web teleop default image

{% hint style="info" %}
Add hint about homing the robot if unhomed?
{% endhint %}

Using this interface, you can directly control all of the robot's joints, switch between camera views, change speed settings, .

\#Labeled diagram of interface options

\#Insert video screengrab of \~ 1 minute of web teleop

### Advanced capabilities - autonomous navigation

{% hint style="info" icon="book-open" %}
Documentation Coming Soon
{% endhint %}

### Advanced capabilities - click-to-pregrasp

{% hint style="info" icon="book-open" %}
Documentation Coming Soon
{% endhint %}

### Connecting remotely over the Internet

It is possible to use Web Teleop entirely remotely over an internet connection, using a service like ngrok for secure tunneling. Instructions and tips can be found in the [stretch4\_web\_teleop](https://docs.hello-robot.com/stretch-4-web-teleop/) repository.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hello-robot.com/stretch4_docs/working-with-stretch/getting-started/demo-web-teleoperation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.