> For the complete documentation index, see [llms.txt](https://docs.paragontruss.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paragontruss.com/layout/layout-overview-1/interface-overview/left-sidebar.md).

# Left Sidebar

<figure><img src="https://2476274629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4iMKVYkWjHD3vmbybWf%2Fuploads%2F8NnrPPolvem64ijUqEIT%2Fimage.png?alt=media&amp;token=29f81062-279b-44ab-9556-189d4332f6d6" alt=""><figcaption></figcaption></figure>

## Explorer Subpanel

All components within the project are displayed in the list.

### Component Search

Search for components within the list to quickly filter based on the search criteria.

### Linked Component Indicator

For component designs that have been designed from or linked to a [Truss Envelope](https://docs.paragontruss.com/layout/how-to/truss-envelopes.md), this icon will appear next to the Component Name. It is possible to have component designs in a project that are not linked to a truss envelope in a layout.

### Component Filter

The Component Filter lets you filter components in the left sidebar including options for: All, Analysis Status, Passing or Failing, Visible or Hidden Levels, and via Linked or Unlinked components.

{% hint style="info" %}
Tip

If you'd like to delete all Unlinked components, use the filter to only display Unlinked components.

Multi-select components using Ctrl + Select, then press Delete.
{% endhint %}


---

# 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.paragontruss.com/layout/layout-overview-1/interface-overview/left-sidebar.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.
