Application Runners
About Application Runners
Application Runner can be seen as an application template (based on JSON schema) that allows end-users create individual logical instances each with its own configuration. Quick Apps, Code Apps and Mind Maps are application runners available in DIAL platform out of the box.
Refer to Schema-rich Applications to learn more.
Application Runners List
In Application Runners, you can add and manage Application Runners you have in your DIAL instance.
Application Runners Grid
| Column | Description |
|---|---|
| Display Name | A user-friendly label for the application runner (e.g. "Python Lambda Runner", "NodeJS App Service"). Helps you pick the right runner when creating a new application based on it. |
| ID | A unique identifier for this runner—typically the base URL of the service (e.g. https://my-runner.example.com). DIAL Core uses this endpoint to POST orchestration payloads. |
| Description | Free-text notes about the runner’s capabilities, cluster location, version, or SLA (e.g. "v2 on GKE, 2 vCPU, 8 GB RAM"). |
| Topics | Tags associated with the runner for identification and filtering on Admin UI (e.g. "finance", "support"). |
| Updated time | Timestamp of the last update to this runner's configuration. Useful for tracking recent changes. |
Create
On the main screen, you can add new Application Runners.
-
Click + Create to invoke the Application Runner modal.
-
Define key parameters for the new application runner:
Field Required Definition ID Yes A unique identifier for this runner—typically the base URL of a specific service. Display name Yes A user-friendly name of the Application Runner that will be displayed on UI. Description No Free-text notes about the runner’s capabilities. Completion endpoint Yes The base URL or a unique identifier of the runner's service hosting (e.g. https://my-runner.example.com/v1/execute). DIAL Core will POST orchestration payloads to this endpoint for any Application bound to this runner. -
Once all required fields are filled, click Create. The dialog closes and the new runner configuration screen is opened. A new runner will appear immediately in the listing once created. It may take some time for the changes to take effect after saving.
Configuration
Click any Application Runner on the main screen to open its configuration page.
Top Bar Controls
- Create: Create an application with the current app runner.
- Application: Create a new custom application deployment in DIAL based on this runner. Created application can be found in Entities -> Applications.
- Assets Application: Create a new application based on this runner and place it in the public folder where all users with corresponding permissions can access it. Created application can be found in Assets -> Applications
- Delete: Permanently removes the selected runner. All related applications still bound to it will be deleted as well.
- JSON Editor (Toggle): Switch between the form-based UI and raw JSON view of the runner’s configuration. Use JSON mode for copy-paste or advanced edits.
- Save: Commits any unsaved changes to the runner’s configuration. Changes may take some time to propagate and take effect.
- Discard: Reverts any unsaved changes made to the runner’s configuration since the last save.
Properties
In the Properties tab, you can define identity and metadata of application runners. DIAL Core uses this information to send orchestration payloads and display application runners on UI.
| Field | Required | Definition |
|---|---|---|
| ID | - | The base URL or a unique identifier of the runner's service hosting (e.g. https://my-runner.example.com/v1/execute). DIAL Core will POST orchestration payloads to this endpoint for any Application bound to this runner. |
| Updated Time | - | Date and time when the app runner's configuration was last updated. |
| Creation Time | - | Date and time when the app runner's configuration was created. |
| Display name | Yes | A user-friendly name assigned to the selected application runner (e.g. "Python Lambda Runner" or "NodeJS Service Worker"). |
| Description | No | Free-text notes about the runner: its environment (staging vs. prod), resource profile (2 vCPU, 8 GB RAM), or any special instructions. |
| Icon | No | An optional icon representing the runner visually in the UI. Select from predefined icons. |
| Title | No | Optional title of the application runner. |
| Type | Yes | The Parameters object app runner expects in its payload. |
| Bucket copy | Yes | Determines whether files stored in the application's bucket should be copied when the application is copied, moved, or published. |
| Topics | No | Use tags to associate runner with specific topics or categories (e.g. "finance", "support") for identification and filtering on UI. |
| Completion endpoint | Yes | The base URL or a unique identifier of the runner's service hosting (e.g. https://my-runner.example.com/v1/execute). DIAL Core will POST orchestration payloads to this endpoint for any Application bound to this runner. |
| Configuration endpoint | No | A URL to fetch dynamic app-specific settings. Use this to drive runtime overrides from a remote config store. |
| Rate endpoint | No | A URL to call a custom rate-estimation API. Use this to compute cost or quota usage based on your own logic (e.g. grouping by tenant, complex billing rules). |
| Truncate prompt endpoint | No | A URL to call your own prompt-truncation API. Handy if you implement advanced context-window management (e.g. dynamic summarization) before the actual application call. |
| Tokenize endpoint | No | A URL to call a custom tokenization service. |
| Viewer URL | No | A URL of the custom viewer UI. A custom UI, if enabled, will override the standard DIAL Chat UI for applications built based on this application runner. |
| Editor URL | No | A URL of the custom builder UI. Application builder allows DIAL Chat end-users to create instances of apps using a UI wizards. |
| Application properties header | No | This setting determines how the apps configuration is handled during a chat completion request. If enabled, DIAL will append the apps configuration to the chat completion request headers. |
| Playback support | No | Playback allows to simulate a conversation without any engagement with models. This allows to review and analyze the conversation flow without invoking any model responses. |
Parameters
By editing the JSON configuration in the Parameters tab, you define the input parameters that must be completed to successfully create a new Application from this Runner.
Refer to Schema-rich Applications to learn more.
Interceptors
In the Interceptors tab, you can add interceptors that will process requests and responses for applications built on this runner.
Interceptors Grid
| Column | Description |
|---|---|
| Order | Execution sequence. Interceptors run in ascending order (1 → 2 → 3...). A request will flow through each interceptor's in this order. Response interceptors are invoked in the reversed order. |
| Display Name | The interceptor's alias, matching the Name field in its definition. |
| Description | Free-text summary from the interceptor's definition, explaining its purpose. |
| ID | Unique identifier of the interceptor, as defined in its configuration. |
Add
You can add one or more interceptors to the application runner.
- Click + Add (top-right of the Interceptors Grid).
- In the modal, select one or more interceptors from the list of available options.
- Click Apply to insert them into the table.
Remove
- Click the actions menu in the interceptor’s line.
- Choose Remove in the menu.
Applications
In the Applications tab, you can see which DIAL Applications are bound to this runner. By assigning applications here, you tell DIAL Core to dispatch orchestration payloads for those apps to this specific runner endpoint.
Applications List
| Column | Definition |
|---|---|
| ID | The unique identifier of the application. |
| Display Name | A user-friendly name of the application (e.g. "Data Clustering Application"). |
| Description | A free-text description of the application |
Add
You can add applications defined in the Entities section.
- Click + Add (top-right of the Applications Grid).
- Select one or more applications in the modal.
- Click Apply to insert them into the table.
Remove
- Click the actions menu in the application’s line.
- Choose Remove in the menu.
App Routes
In the App Routes tab, you can manage application runner-specific routes. Here you can create, view, edit, and delete routes.
Create
- Click + Add (top-right of the App Routes pane).
- Enter the route Display name in the modal.
- Click Create to confirm creation.
Properties
In the Properties sub-tab you can configure route's identity and requests-handling behavior.
TIP: Configuration of this tab is similar to routes. See Routes documentation for more information.
Attachments
In the Attachments sub-tab you can configure attachment paths for both requests and responses.
Roles
In the Roles sub-tab you can define route-specific role assignments, allowing administrators to control access to each individual route.
TIP: Configuration of this tab is mostly similar to routes. See Routes documentation for more information.
Use Inherit Application Roles toggle to apply roles assigned to an application which is built based on the selected application runner.
Audit
In the Audit tab, you can monitor activities related to the selected app runner.
Activities
The Activities section provides detailed visibility into all changes made to the selected app runner. This section mimics the functionality available in the global Audit → Activities menu, but is scoped specifically to the selected app runner.
JSON Editor
For advanced scenarios of bulk updates, copy/paste between environments, or tweaking settings not exposed in the form UI—you can switch to the JSON Editor in any application runners configuration page.
Switching to the JSON Editor
- Navigate to Builders → Application Runners, then select the application runner you want to edit.
- Click the JSON Editor toggle (top-right). The UI reveals the raw JSON.
TIP: You can switch between UI and JSON only if there are no unsaved changes.