> For the complete documentation index, see [llms.txt](https://docs.gpmautomate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gpmautomate.com/automate-en/action-guide/mouse/mouse-release.md).

# Mouse release

Mouse release is the action of commanding the mouse, which is in a pressed state, to immediately release (let go of) the left mouse button. This action does not have complex configuration parameters and is always a mandatory final step for a sequence of drag-and-drop data operations.

🎥 See more instructional video: [Here](https://youtu.be/kQZWs1I76Zo).

#### Practical application in command sequences:

This action combines with previous commands to fully complete a simulated task:

* Step 1: `Mouse press and hold` to press and hold onto the captcha slider or an interface element.
* Step 2: `Mouse move` to drag that element to the target position.
* Step 3: `Mouse release` to let go of the mouse, completing the drop of the element at the new position for the website system to register the result.


---

# 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.gpmautomate.com/automate-en/action-guide/mouse/mouse-release.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.