Tools process the context supplied by the surface where they run. They do not automatically read the clipboard, active document, browser page, or every open project file.
Documents or Folders
Documents or folders contains the deployment's primary input.
A local project file or folder also identifies which project's SK Memory is available during the run.
Optional Guidance
Optional guidance stores secondary reference entries such as a style guide or directive.
Current beta limitation: these entries are saved and displayed, but their contents are not read during a run. Put anything the tool must use in Documents or folders or in the tool's instructions.
Save New Files To
Save New Files To appears when the tool can use a configurable output folder. Choose a folder inside the open project.
If the tool does not use a configurable destination, the inspector shows Save Location with a read-only explanation. A previously saved destination is not deleted.
Use the Context Editor
Select Documents or folders, Optional guidance, or Save New Files To to open the context editor. The editor shows all context roles together while leaving Project Navigator available.
Drag supported documents or folders from Project Navigator into Input Sources or Reference. Drop a project folder into Save New Files To, or select Choose Save Folder....
Changes are saved as they are made. There is no separate Save button. Adding the same source to the same section twice is rejected.
Preview Saved Context
Select a saved document or folder row to preview it. Previewing does not change the saved context or run the Tool.
Remove Saved Context
Select the remove action on a saved row to remove that entry from this deployment's context. Removing context does not delete the original file or folder.
Close the editor with the close action or by selecting the shaded area around it.
Several Input Files
By default, a folder or multi-file selection is combined and the tool runs once.
Enable Process each input file separately in Tool settings when the complete workflow should run once per file. Separate mode accepts up to 50 files. Folder input includes files directly in the selected folder, not its subfolders.
Leave separate mode off when the tool or script already handles the complete collection itself.
Input from Other Surfaces
Power Strip Agent — runs without input from its sidecar, or uses files, folders, or text dropped on the command.
Browser Agent — captures the active Chrome page.
Schedule trigger — uses the deployment's saved Documents or folders.
File-watch trigger — uses the newly created matching file instead of saved primary input.
Mobile Dashboard — uses saved context or temporary overrides.
Automation — uses explicit caller input first, then any saved binding, then empty input.
ThinkForge MCP — does not currently run user-created tools.