> For the complete documentation index, see [llms.txt](https://docs.guideflow.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guideflow.com/help/sandbox/how-to-edit-a-sandbox.md).

# How to edit a sandbox

### Auto-linking screens

During HTML recording, the screens you capture are automatically linked to their respective buttons by default. 

### How to edit a Sandbox/Clickable demo

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/er5z501f6r>" %}

* Choose an element in the captured screen.
* Click the 'link' icon and choose the target screen.
* Click the "Apply to all steps" button to create links for the selected element across all steps. This is useful if you have the same element repeating on different screens and want to apply the same link to all of them.

{% hint style="info" %}
Click on an empty space in the demo to instantly highlight all clickable links in blue color.
{% endhint %}

### HTML editor&#x20;

The [HTML editor](broken://pages/vN0iAltMVTLtQ2d4Zv5p) allows you to edit the elements of your demo like text, graphs, images, etc.&#x20;


---

# 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.guideflow.com/help/sandbox/how-to-edit-a-sandbox.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.