A script is the core unit of automation in Script.it. It defines a sequence of steps — called blocks — that the platform runs in order. You describe what you want to automate in plain English, and the AI agent builds the script for you: it creates the blocks, writes the source files, and connects the pieces.
What a script is
Every script has a name, description, ordered blocks, source files, and any reusable files it needs. You can open a script in your workspace to review what it does, run it, or ask the agent to change it.
Scripts are reusable — you can run the same script many times, in many sessions, without the results of one run affecting another. They are also version-tracked: any change the agent makes to a script is captured as a version snapshot, so you can revert to a previous state at any time.
How the agent builds scripts
When you describe an automation in the session, the agent figures out what blocks are needed and creates the script automatically. It writes the code for executable blocks, adds documentation where useful, connects any required tools, and prepares the script so you can run it.
You don’t need to manage the underlying files directly. But because the script is inspectable, you can read the source files, copy them, share them, or restore an earlier version when needed.
You can ask the agent to modify a script at any time — add a step, change the logic of a block, or restructure the whole workflow. Just describe what you want in the chat.
What scripts can contain
A script can contain any number of blocks. Blocks come in two types:
- Executable blocks — run Python or shell code to perform an action, such as fetching data, calling an API, transforming a file, or sending a notification.
- Markdown blocks — contain plain text for documentation and notes, helping you and your team understand what the script does.
Blocks run in the order shown in the script view. The agent handles the wiring — you just describe the workflow you need.
Scripts can also contain assets: persistent files such as templates, reference data, configuration, and small memory files that survive across sessions. See Assets for details.
Agent context
Scripts also have context settings that control how much of the script the agent can use in chat. See Agent context for details.
You do not need to edit these settings for normal use, but they are useful when a script should behave like persistent context rather than an automation the agent should run.
Where to go next
The pages in this section cover how blocks are structured, how reusable files work, and how to start from ready-made templates. 
