Context and Input

Give a Tool the material it needs before running it. On the Tools page, select a deployment, then choose Documents or folders, Optional guidance, or Save New Files To to open its context editor.

Tools do not automatically read every open document, the clipboard, or the active browser page. The place you run a Tool determines what input it receives.

Choose the work to process

Documents or folders is the primary input. Drag supported documents or folders from Project Navigator into Input Sources in the context editor.

A folder supplies files directly inside it, without its subfolders. By default, several input files are combined and the Tool runs once.

In Tool settings, enable Process each input file separately when you want the complete workflow to run once for each file. This mode accepts up to 50 files. Leave it off if the Tool already handles the collection as a whole.

Add supporting guidance for AI

Use Optional guidance for a style guide, directive, or other supporting text. In the context editor, add existing local files to Reference files.

AI actions read these files as supporting context. References do not replace the primary input or become extra documents to combine.

Use local UTF-8 text files. A run accepts up to 12 reference files, with a maximum of 32 KiB per file and 96 KiB in total. A missing, unreadable, unsupported, or oversized file stops an AI run; remove or replace the affected reference before retrying.

A Tool without an AI action warns and continues without using its references.

Choose where new files go

Save New Files To appears when the Tool supports a configurable output folder. Drop a folder from the open project into that section, or select Choose Save Folder....

Other Tools show Save Location with an explanation instead of an editable destination.

Choosing a save folder does not make a Tool create a file. The Tool still needs an action that saves output.

Preview or remove a saved source

Select a saved row to preview it. This does not run the Tool or change its input.

Use the row's remove action to remove it from the deployment. The original file or folder is left in place.

Adds and removals save immediately. Close the context editor when finished; there is no separate Save button.

Understand input from other places

  • A project-file Tool uses the file you clicked.
  • A project-folder Tool uses its attached folder.
  • A Ribbon Tool uses the current selection followed by saved input, with duplicates removed.
  • A Power Strip Agent uses derived or saved input, or the files, folders, or text you drop on it.
  • A Browser Agent captures the active Chrome page.
  • A schedule uses saved input.
  • An Added or Modified file watch uses the affected file. A Deleted watch supplies its former path and event information, without file contents.

See Tool Surfaces and Triggers for the corresponding workflows.