> ## Documentation Index
> Fetch the complete documentation index at: https://docs.reconnect-tool.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating & Managing Scripts in the Dashboard

> Write, upload, and store scripts that auto-execute on your Termux devices — manage everything from the dashboard without touching device files.

The **Scripts** tab lets you create, edit, and store scripts that automatically execute on your Termux devices. Instead of manually placing files on each device, you manage everything from the dashboard and Reconnect handles delivery. Any script you save here is automatically run on your connected Termux devices — no SSH session or file manager required.

<Info>
  The Scripts tab stores **custom scripts** you write or upload. This is separate from the auto-generated `reconnect.txt` autoexec script configured through the [Add Scripts](/termux/add-scripts) section of the device menu. Use this tab for your own Lua automation or shell scripts.
</Info>

## Storage Quota

Your account has a **shared storage quota** across all scripts. The current usage is displayed at the top of the Scripts tab (for example, **184 B / 5.00 MB**), along with the total number of scripts stored. Individual scripts are capped at **512 KB** each.

Keep an eye on your quota if you're storing large or numerous scripts — deleting unused scripts frees up space immediately.

## Creating a Script

<Steps>
  <Step title="Click New Script">
    Click the **New Script** button in the top-right corner of the Scripts tab to open the script editor.
  </Step>

  <Step title="Name your script">
    Enter a name for the script including its file extension (for example, `auto_rejoin.lua` or `setup.sh`). The extension is displayed as a **color-coded badge** next to the script name so you can tell file types apart at a glance.

    Supported extension badges: `.lua`, `.py`, `.sh`, or a generic badge for other extensions.
  </Step>

  <Step title="Add your content">
    Either **paste your script directly** into the editor, or click **Upload file** to import an existing file from your computer. Uploading auto-fills the name field from the filename if it's still empty.

    <Note>
      Only `.txt` and `.lua` files can be uploaded. If you want to store a `.py` or `.sh` script, paste the content directly into the editor instead.
    </Note>

    A **live byte counter** updates as you type or paste, so you can track your usage against the 512 KB per-script limit in real time.
  </Step>

  <Step title="Click Create Script">
    Click **Create Script** to save. Your new script appears immediately at the top of the list and will begin auto-executing on your connected Termux devices.
  </Step>
</Steps>

## Viewing, Editing, and Deleting Scripts

Each script in the list has three actions available:

| Action     | Description                                                                                                                                                                      |
| ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **View**   | Opens a read-only preview of the script's contents. Use the **Copy** button inside the viewer to copy the full content to your clipboard.                                        |
| **Edit**   | Opens the same editor used during creation, pre-filled with the current script content. Make your changes and save to update the script on all connected devices.                |
| **Delete** | Permanently deletes the script and immediately frees the storage it occupied. This action cannot be undone — make sure you have a local copy if you might need the script again. |

## Auto-Execution on Termux Devices

Every script stored in this tab is automatically executed on your Termux devices when the Reconnect client starts or when a new script is pushed. You don't need to trigger execution manually — Reconnect handles it as part of the normal device startup flow.

<Tip>
  Name your scripts descriptively (for example, `anti_idle_v2.lua` rather than `script1.lua`) so you can tell them apart as your library grows. The color-coded extension badges also help you quickly identify what type of script each entry is.
</Tip>