Skip to main content

Embedding Files

Automation Agent supports two script file formats:

  • normal script documents are JSON files
  • bundle-capable scripts are .abscript files, which can carry extra files with them

Those extra files are what this page is about.

What You Usually See In The Panel​

From the user perspective, there are two common cases:

1. A normal script document​

This is usually a JSON-based Automation Agent document.

You will often use these in the Library, especially when the script itself is the important part and there are no extra files that need to travel with it.

These saved JSON documents can also include user-facing metadata such as a title and description, which is why they are a good fit for library entries.

2. A bundled script​

This is an .abscript file.

Use this when the script should carry one or more files with it, for example:

  • a media file
  • a .mogrt
  • an .epr export preset
  • a .sqpreset
  • a .prproj

So the practical difference is:

  • JSON script: script only
  • .abscript: script plus optional bundled files

Why Bundled Files Exist​

Bundled files solve a portability problem.

Without them, a script may depend on a file path that only exists on the machine where the script was created. With bundled files, the script can carry the required file with it.

That makes bundled scripts useful when:

  • you move scripts between machines
  • you share scripts with teammates
  • you want a script to stay usable even when local file paths differ

The Bundled Files Tab​

The Bundled Files tab is the main user-facing place for this feature.

There you can:

  • see which files are currently bundled with the open document
  • add files that should belong to the script
  • replace or remove bundled files
  • understand which external files the current bundled workflow depends on

So if you are working in the panel and want to understand or change the files attached to the current script, Bundled Files is the place to look.

Two Common Bundle States​

From the user perspective, bundled scripts usually appear in one of these states:

Already complete​

The .abscript file already contains everything it needs.

You can move it, store it, share it, and run it as a bundled package.

Still waiting for one or more files​

Sometimes an agent or saved document gives you a bundle-capable script that is not finished yet because one or more files still need to be chosen first.

In that case, Automation Agent can prompt you for the missing file or folder and then continue from there.

So the mental model should be:

  • some bundled scripts are already self-contained
  • others are more like a prepared bundle recipe that still needs you to choose the actual file once

What The Agent Usually Does For You​

In normal use, you usually do not hand-author these file types yourself. Instead, an agent or the Custom GPT typically generates the script for you.

Custom GPT workflow​

When you work with the Custom GPT, it is usually unattractive to upload files into ChatGPT just so they can later be downloaded again into Automation Agent.

Because of that, the Custom GPT is generally guided toward creating bundle-capable ABScript workflows with placeholders for the files instead of trying to carry the real files through ChatGPT itself.

In practice that means:

  • the Custom GPT can prepare the bundled workflow
  • the actual media, preset, MOGRT, or project file is still chosen locally later
  • when you first run that workflow in Automation Agent, the panel will ask you for the missing file and then continue from there

So in the Custom GPT case, the model usually works with placeholders rather than with the real embedded file payload itself.

Local agent workflow​

Locally running agents are different.

If the agent runs on your machine and has access to your local files, then it can often do more:

  • it can generate a bundle-capable script with placeholders
  • or, if you explicitly want the files embedded right away, it can often prepare the bundle using the real local files directly

So with local agents you usually have the full range of options:

  • placeholder-based bundled workflows
  • already-complete bundled workflows
  • or plain JSON scripts when no bundled files are needed

That means you mostly only need to recognize the result:

  • if you see JSON, it is a regular script document
  • if you see .abscript, it may contain bundled files

And if a bundled workflow still has missing files, Automation Agent will ask for those files locally when you attempt to run it the first time.

Technical Background​

If you want a simple mental model for what happens during execution, think of it like this:

  1. Automation Agent opens the .abscript package.
  2. Any bundled files inside it are unpacked into an Automation Agent-managed local cache folder.
  3. Whenever the script refers to one of those bundled files, Automation Agent uses the path of that unpacked local file instead.

So by the time the actual script logic runs, those bundled files behave like normal local files with normal local paths.

The important practical point is that you do not need to manage that extraction yourself. Automation Agent handles it before the script starts running.

When To Choose A Bundled Script​

Choose a bundled script when the automation should travel together with required files.

Choose a normal JSON script when:

  • the workflow does not need extra files
  • or the file paths are already known and staying local is fine

Good Starting Examples​

If you want to see typical bundled-file workflows, start with these examples: