> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/developer-guide/troubleshooting-and-common-errors/navigation-to-tabs.md).

# Navigation to tabs

The preview is not restricted to being done in the same web browser instance as the server-side preview window (you can open the website's URL with the preview parameters on any other browser or even device). When a page is opened to be previewed, only this browser's tab will be part of the preview. Navigating to a different page (clicking a link) that opens in a different tab will not transport the session parameters, as they are only stored in the browser's sessionStorage, which is not shared between browser tabs.

This means you must remain in the same window and tab during a session, OR you must append the URL-query parameters from the preview again on the next tab.


---

# 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.jentis.com/developer-guide/troubleshooting-and-common-errors/navigation-to-tabs.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.