# Launchers

1. [Home](https://www.agilicus.com/)
2. [Agilicus AnyX Administrative Web Interface](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/)
3. [Resources](https://www.agilicus.com/anyx-guide/agilicus-anyx-administrative-web-interface/resources/)
4. Launchers

![](https://www.agilicus.com/www/ea7c934f-featured-anyx-admin-resourceslaunchers.png)## Launchers

[CONTACT](/contact-us/)

The **Launchers** pages (routes `/launcher-overview` and `/launcher-new`) manage launcher resources. A launcher is the configuration for launching a program on a user's desktop via a connector, so the program's requests are proxied through Agilicus to the corresponding backend resources. When a user has permission for a launcher, a shortcut is configured automatically on their desktop. See [Resources (concepts)](/anyx-guide/agilicus-anyx-administrative-web-interface/concepts/resources/) and [End-user experience](/anyx-guide/agilicus-anyx-administrative-web-interface/concepts/end-user-experience/) for where launchers fit.

## Purpose

A launcher resource defines a command that runs on the user's machine and which resources that program may reach. The launcher signs the user in once, and each resource is then one click away. This is how users reach resources that do not fit in a browser: SSH services, databases, desktops through a remote desktop client, and other TCP-based resources.

The Launchers overview lists every launcher, its command path, arguments and the resources it can reach, and lets you create, edit and delete launchers. The New Launcher wizard steps through the name, resource members, advanced configuration, a review and a done step.

## Why use it

- Give users access to desktop applications that talk to resources inside your network, without a virtual private network and without exposing those resources. See [Zero trust architecture](/anyx-guide/agilicus-anyx-administrative-web-interface/concepts/zero-trust-architecture/).
- Automate the shortcut: a user with permission automatically gets the launcher shortcut on their desktop.
- Bundle several resources behind one launcher so a single program (for example a database client) can reach everything it needs.
- Tune the launcher for unusual applications: interceptor behaviour, hidden console windows, elevated privileges, or multiple cooperating processes.

## When to use it

- When a resource is not reachable in a browser, such as an SSH service, a database or a remote desktop, and the user needs a desktop application to reach it.
- When a user's application needs to reach several resources, and you want one launcher to cover them all.
- Whenever you add, change or remove a launcher, or change which resources it can reach.

**Prerequisite**: permission to administer launchers (an owner or administrator role). Without it, the page shows a *no permissions* message.

## How to use it

### Launchers overview

1. Open **Resources > Launchers > Overview** from the left navigation.

![Launchers overview](https://www.agilicus.com/www/4d4b1baf-launchers-overview.png)    The table lists every launcher with its name, command path, command arguments, the resources it reaches, its diagnostic mode and an actions menu. The name and command path cells are editable inline. Use the search box to filter the table, and the toolbar buttons to **ADD LAUNCHER** or delete selected rows.

1. Open the **more** menu on a launcher row for the row actions:

![Launchers overview row actions](https://www.agilicus.com/www/46c38ae0-launchers-overview-row-actions.png)    - **Search in Audits**: jumps to the audit subsystem filtered to this launcher.
- **Configure Resource Members**: opens the resources dialog to choose which resources the launcher can reach.

### Creating a launcher with the wizard

1. Open **Resources > Launchers > New**. The wizard has five steps: **Launcher name**, **Resource members (optional)**, **Advanced configuration (optional)**, **Apply**, and **Done**.

\#### Step 1: Launcher name

1. Enter the **launcher name**. The tooltip explains that this name must be unique across all launchers and must be a valid hostname. Enter the **command path**: the program the launcher starts on the user's desktop.

![Launcher wizard: step 1, name](https://www.agilicus.com/www/aeabf6cf-launchers-new-step1-name-filled.png)    \#### Step 2: Resource members (optional)

1. Optionally select the resources this launcher can reach. This step is optional; you can add resource members later from the overview's **Configure Resource Members** action.

![Launcher wizard: step 2, resource members](https://www.agilicus.com/www/e72f9d26-launchers-new-step2-resource-members.png)    \#### Step 3: Advanced configuration (optional)

1. Answer whether the launcher has additional options and whether the application requires multiple processes.

![Launcher wizard: step 3, advanced](https://www.agilicus.com/www/02389c03-launchers-new-step3-advanced.png)    Choosing **Yes** for additional options reveals:

- the **command arguments** and **start directory** for the main command;
- the **associated applications** chiplist (the applications the launcher opens);
- toggles for DNS interception (*My launcher requires DNS (name service) interception*), hiding the launcher command window, running with elevated privileges, custom delayed initialisation, and ending an already-running instance.

![Launcher wizard: step 3, advanced options expanded](https://www.agilicus.com/www/02389c03-launchers-new-step3-advanced-expanded.png)    Choosing **Yes** for multiple processes reveals a process table where each row defines an extra process with its **program name**, **command arguments** and **start directory**, plus per-process options such as treating the program name as a regular expression, starting the process only if it is not running, ending it when the launcher exits, and attaching to it if it is already running. Use **+ Add process** to add rows and **DELETE** to remove them.

![Launcher wizard: step 3, processes](https://www.agilicus.com/www/02389c03-launchers-new-step3-processes.png)    \#### Step 4: Apply

1. Review the summary, which restates the launcher name, command path and any options you configured. Select **APPLY** to create the launcher. Creation runs asynchronously; the wizard advances to Done automatically when it succeeds.

![Launcher wizard: step 4, apply](https://www.agilicus.com/www/17afe53e-launchers-new-step4-apply.png)    \#### Step 5: Done

1. The Done step confirms the launcher was created and offers to add it to resource groups and assign permissions.

![Launcher wizard: step 5, done](https://www.agilicus.com/www/ad44ebac-launchers-new-step5-done.png)    ## Fields and controls reference

| Control | Purpose | Required | Default | Valid values | Notes |
|---|---|---|---|---|---|
| Name | The launcher's unique name | Yes | n/a | A valid hostname | Unique across all launchers |
| Command path | The program the launcher starts | Yes | n/a | A path on the user's machine |  |
| Resource members | Resources the launcher can reach | No | n/a | One or more resources | Set in the wizard or from the row menu |
| Command arguments | Arguments for the main command | No | n/a | Any text | Advanced configuration |
| Start directory | Working directory for the main command | No | n/a | A path | Advanced configuration |
| Associated applications | Applications the launcher opens | No | n/a | One or more applications | Advanced configuration |
| DNS interception | Intercept name service traffic | No | Off | On, Off | For applications that need it |
| Hide console | Hide the launcher command window | No | Off | On, Off |  |
| Run as administrator | Run elevated | No | Off | On, Off |  |
| Custom delayed initialisation | Fork then attach behaviour | No | Off | On, Off |  |
| End existing if running | Terminate an already-running instance | No | Off | On, Off |  |
| Extra processes | Additional processes to manage | No | None | One or more process rows | Each with program name, arguments, start directory |

## Dialogs and popups

- **Configure Resources dialog**: opened from the row menu's **Configure Resource Members**. The two-pane dialog lists available resources on the left and assigned resources on the right; select options to move them between tables. The available resources show their type in parentheses, for example *efs-liveline-poc-share (share)* or *hr (application)*.

![Launcher resources dialog](https://www.agilicus.com/www/14e56832-launchers-resources-dialog.png)    - **Confirmation dialog**: deleting a launcher confirms before acting.

## Configuration versus diagnostics versus confirmation

- **Configuration**: creating launchers, editing the name and command path inline, resource members, and the advanced options are persistent configuration.
- **Diagnostics**: the diagnostic mode column on the overview reflects the launcher's current state; use **Search in Audits** from the row menu to see access attempts.
- **Confirmation**: deleting a launcher is permanent and removes the shortcut from users' desktops. Confirm before proceeding.

## Pagination and async behaviour

- The Launchers overview pages at **25 rows per page**; the paginator shows the current page and totals. The demo organisation had no launchers when captured.
- Launcher creation runs asynchronously. After selecting **APPLY**, wait a few seconds; the wizard advances to Done automatically. New launchers appear on the overview shortly after creation.
- Inline cell edits save when you blur the field; wait a few seconds and reload to confirm the change.
- Resource member changes apply asynchronously; after moving resources in the dialog, wait a few seconds and reload to confirm.

## Troubleshooting

- **The launcher will not create**: check the name is a valid hostname and the command path is present. Validation errors appear on the relevant step.
- **Users do not see the shortcut**: the launcher shortcut appears on a user's desktop only after they are granted permission and sign in again. Check [Resource permissions](/anyx-guide/agilicus-anyx-administrative-web-interface/access/resource-permissions/).
- **The program starts but cannot reach its resources**: confirm the resource members include everything the program needs, and that the resources themselves are configured and healthy.
- **The launcher shows problems in diagnostics**: use **Search in Audits** from the row menu to see what failed, and check the [diagnose-launcher](https://www.agilicus.com/diagnose-launcher) guide.

## See also

- [Resources (concepts)](/anyx-guide/agilicus-anyx-administrative-web-interface/concepts/resources/)
- [Zero trust architecture](/anyx-guide/agilicus-anyx-administrative-web-interface/concepts/zero-trust-architecture/)
- [End-user experience](/anyx-guide/agilicus-anyx-administrative-web-interface/concepts/end-user-experience/)
- [Resource permissions](/anyx-guide/agilicus-anyx-administrative-web-interface/access/resource-permissions/)
- [Resource groups](/anyx-guide/agilicus-anyx-administrative-web-interface/access/resource-groups/)
- [Policies](/anyx-guide/agilicus-anyx-administrative-web-interface/access/policies/)
- [Connectors](/anyx-guide/agilicus-anyx-administrative-web-interface/resources/connectors/)
- [Databases](/anyx-guide/agilicus-anyx-administrative-web-interface/resources/databases/)
- [SSH](/anyx-guide/agilicus-anyx-administrative-web-interface/resources/ssh/)
- [Desktops](/anyx-guide/agilicus-anyx-administrative-web-interface/resources/desktops/)
- [Getting started: expose a resource](/anyx-guide/agilicus-anyx-administrative-web-interface/getting-started/expose-resource/)

## Web guide

- [Launchers](https://www.agilicus.com/product-guide/launchers)
- [Launcher (desktop) install](https://www.agilicus.com/product-guide/launcher-install-desktop)
- [Diagnose launcher](https://www.agilicus.com/diagnose-launcher)