> 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/close-all-tabs.md). # Close all tab Close all tab is an action that instructs the browser to clean up and close multiple open tabs, keeping only the first tab (the tab with index = `0`) on the navigation bar. This action does not have any accompanying configuration parameters. 🎥 Watch the tutorial video: [Here](https://youtu.be/a9qNt96X1SM). #### Practical example: Reset the browser before switching accounts or ending a workflow During the automation process, your script may open many additional tabs due to clicking on advertisement links, popups, or pages to check mail or wallets. Having too many tabs running in the background will consume your computer's RAM resources and make it easier for subsequent workflows to confuse the interface. * How to apply: Place the Close all tab action at the end of the script (before the block of commands that completely closes the browser) or at the beginning of the script to ensure the browser is always in the cleanest state before starting a new workflow cycle. --- # 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/navigation/close-all-tabs.md?ask=&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.