> 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/navigation/active-tab.md).

# Active tab

This action helps the tool switch to another open tab in the browser.

It allows you to multitask easily. For example, you are in tab A to retrieve data, then use this command to switch to tab B and paste the data there.

🎥 Watch the tutorial video: [Here](https://youtu.be/a9qNt96X1SM).

### Important Note

After switching, all subsequent actions (click, input, scrape data) of the tool will only run on this newly selected tab.

### Configuration Parameters

* Type: Choose the method for the system to determine the tab to switch to:
  * By Index: Switch the tab based on the position index (from left to right, starting from 0).
  * By Prefix URL: Switch the tab based on the beginning of the URL. The system will scan through the open tabs, and any tab with a URL starting with the string you enter will be activated.

#### 💡 User Advice

When using the tab switching feature, you should prioritize selecting the **By Prefix URL** method.

The reason is that the order of tabs (Index) can change unpredictably due to the return mechanism from the Remote Port, leading to using the index number being inaccurate and disrupting the script. Using Prefix URL will ensure the tool always finds the necessary tab regardless of its position in the browser.

*A little tip: After the browser opens popup windows (like Google login windows, MetaMask...), you can simply call the Active Tab action with index 0 to quickly return to the main browser screen.*

<figure><img src="/files/KGx8BeGmbuCFWPKGhqC7" alt=""><figcaption></figcaption></figure>


---

# 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.gpmautomate.com/automate-en/action-guide/navigation/active-tab.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.