> For the complete documentation index, see [llms.txt](https://tmediadocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmediadocs.telcobridges.com/other-pages/applications/viewing-the-list-of-installed-applications.md).

# Viewing the List of Installed Applications

#### ***Applies to version(s): v2.5, v2.6.***

The Toolpack application server is designed to run a large variety of applications. Before you can run an application, you must first be able to view it from a list of applications.

**To view the selection of applications:**

* Select **Instances** from the navigation panel.

![Toolpack v2.5 Navigation Panel Instances](https://docs.telcobridges.com/w/images/f/f2/Toolpack_v2.5_Navigation_Panel_Instances.png)

* The **Application Instance List** is displayed in the information panel.

![Toolpack v2.5 Application Instances](https://docs.telcobridges.com/w/images/f/f9/Toolpack_v2.5_Application_Instances.png)

### Application states

Applications are displayed in one of three states:

* Run (application is operating)
* Management (application is installed but not in operation)
* Fault (application has an operation fault)


---

# 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://tmediadocs.telcobridges.com/other-pages/applications/viewing-the-list-of-installed-applications.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.