Skip to main content

# Task Templates

Task templates are reusable task definitions with parameters. Define a template once, then run it with different inputs—whether for a single item or hundreds at once.

## What Are Templates?​

A template combines:

- Instructions: The task description agents will follow
- Parameters: Variables that customize the task for specific inputs (like which file to process)
- Prompts: UI elements that let you select parameter values (file browsers, dropdown lists, etc.)

Templates are configured per environment by administrators. When you run a template, you provide values for its parameters, and the system creates tasks with those values filled in.

## Running a Template​

1. Open the Templates section from the home page
2. Select your environment and template
3. Fill in the required parameters using the provided prompts
4. Click Run to create a task

The template renders with your parameter values and launches as a normal task. You can monitor progress, review results, and approve changes just like any other task.

## Batch Processing​

Templates become especially powerful when you need to process many items. Select multiple values for a parameter and run the template against all of them at once—turning weeks of manual work into overnight batch operations.

See Batch Processing for details on multi-select parameters, cartesian products, and workflow best practices.

## Common Use Cases​

Templates are commonly used for code modernization, refactoring, testing, and documentation tasks.

See Template Examples for specific use cases including RPG modernization, language migration, and batch refactoring patterns.

## Configuration​

Templates are defined in your environment's configuration. Administrators create templates with:

- Markdown instructions containing parameter placeholders
- Parameter definitions specifying prompts and validation
- Multi-select settings for batch processing

Boolean parameters (`type: "boolean"`) render as checkboxes. A required boolean parameter still allows either checked (`true`) or unchecked (`false`) values, so templates can branch on the user's explicit choice.

See Environments in the Administration section for configuration details.