> For the complete documentation index, see [llms.txt](https://docs.intrepidcs.com/vspy-3-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intrepidcs.com/vspy-3-documentation/vehicle-spy-tutorials/tabs-in-the-user-interface.md).

# Tabs in the User Interface

To help increase productivity, Vehicle Spy 3 has the ability to tear tabs from the main workspace. With this feature, views can be placed where they will be the most useful.

#### Tearing and Docking Tabs (Figure 1):

Tabs in Vehicle Spy can be "torn off" or removed from the main window. This comes in handy when needing to see a number of different views at the same time or if different windows on different parts of the screen would be helpful. Tabs are removed from the main window by clicking on the tab or view and dragging it away. To dock a tab, move selected tab toward desired view. A dock option will appear. Placing the mouse over the desired dock option and releasing will snap it to the other view. The highlighted blue area is where the view will go after the mouse button is released. To prevent docking the view, but allow it to move it elsewhere, hold **Ctrl** on the keyboard while dragging.

![Figure 1: Tearing and docking a tab.](https://3170208387-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL6lcovCpkhoS9uTOFtEp%2Fuploads%2FQM8K1WctDWiLj2UIYDt2%2FIntrp2.2.gif?alt=media\&token=9fa83791-7990-4eab-b53e-dd4eb8d40762)


---

# 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.intrepidcs.com/vspy-3-documentation/vehicle-spy-tutorials/tabs-in-the-user-interface.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.