Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.script.it/llms.txt

Use this file to discover all available pages before exploring further.

When your scripts run, they often produce files — downloaded data, generated reports, transformed datasets, or any other output written to disk. These files are stored in your session’s workspace and are available to browse, preview, and download from the session files panel.

​
The session files panel

The files panel sits alongside the chat in your session view. It shows everything inside your session’s data_files/ folder — the directory where scripts write their runtime outputs. To open a file, click its name in the panel. A preview pane opens below the file list, where you can read the file’s contents inline. You can resize the preview by dragging its bottom edge. To close the preview, click the X in the resize handle. If you have many files, use the search icon in the panel header to filter by name.

​
What gets stored as a session file

Any file your script creates during a run ends up in data_files/. Common examples include:
  • CSV or JSON files produced by a data-fetching block
  • Reports or summaries generated by an AI step
  • Images, PDFs, or other documents downloaded from external services
  • Intermediate files written by one block and consumed by the next
The agent can also reference session files directly in chat — if a file tag appears in a message, clicking it opens that file in the panel automatically.

​
Session files vs. script source files

Session files and script source files are stored separately and serve different purposes.
Script source files are part of the saved script. They contain the code that runs, and any change to them is visible across all sessions. Session files in data_files/ are runtime outputs produced when the script runs. They belong to the session that created them and are not shared with other sessions.
This separation keeps scripts clean and reusable. You can run the same script dozens of times, in different sessions, without the outputs from one run interfering with another.

​
Downloading files

To download a file from your session, right-click it in the files panel and choose Download, or open the file preview and use the download option there. You can also ask the agent to help you find or organize session files through chat — for example, “What files were created during the last run?” or “Show me the output from the fetch block.”

​
Exporting a session

You can export an entire session as a zip archive for backup or sharing. The export includes:
  • Your chat history
  • All files in data_files/
  • Block execution artifacts
Saved scripts are exported separately from sessions, since they’re shared across sessions.
To export a session, use the export option in the session menu. Script source files can be exported independently from the script’s own export option.
Script exports contain the complete script definition, all source files, and any static data files. Exporting a script gives you a portable zip you can import into another workspace or keep as a backup.