> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloud.red/llms.txt
> Use this file to discover all available pages before exploring further.
# Script Runner
> The ScriptRunner feature allows users to run scripts in various languages (Bash, Python, Node.js, TCL) against one or more F5 devices.
ScriptRunner enables users to have a larger level of control while performing actions against their entire fleet.
Warning: This feature has the potential to negatively impact devices. When running scripts through script runner, make sure that all potential impacts are properly evaluated.
### Key Concepts
* **Script:** A standalone code block not tied to any specific device.
* **Task:** A script that is associated with one or more F5 devices for execution. Tasks can also have predefined arguments if the script requires them.
* **Repositories:**\
**Customer Repository:** Contains scripts that the customer creates and manages.\
**Cloud.Red Repository:** A curated collection of scripts provided by the Cloud.Red engineering team, available for customers to use in their environments.
### Arguments
Scripts in ScriptRunner can accept arguments, allowing for dynamic and flexible execution. The nomenclature for passing arguments in various scripting languages is as follows:
**Bash**
```
#!/bin/bash
echo "Argument 1: $1"
echo "Argument 2: $2"
```
**Python**
```
import sys
arg1 = sys.argv[1]
arg2 = sys.argv[2]
print(f"Argument 1: {arg1}")
print(f"Argument 2: {arg2}")
```
**Node.js**
```
const args = process.argv.slice(2);
console.log(Argument 1: ${args[0]});
console.log(Argument 2: ${args[1]});
```
**TCL**
```
set arg1 [lindex $argv 0]
set arg2 [lindex $argv 1]
puts "Argument 1: $arg1"
puts "Argument 2: $arg2"
```
These examples illustrate how to handle arguments in the different supported scripting languages, making your scripts adaptable to various requirements and contexts within the Cloud.Red environment.
### Using Script Runner
In Script Runner users have the ability to run a script, save it to their repository, or save a script as a task to be run at a later time.
* Select your interpreter and insert the script intended to be run.
* Add any necessary arguments that are required for the script below.
* Save scripts to the account repository so that they are available at a later date.
* When planning to run the script immediately, select the devices that the script is intended to be run on.
* Users can use the task feature to attach devices to a script that is saved to the repository in preperation of running the script at a later time.
* When saving a script to the repository, provide a name and description for the script.
* When saving a task to the repository, provide the name, description, the script and the devices that the script is intended to be run on.
