A tool reports progress as its steps run and shows the final result or error.
Run and Cancel
Select Run in the tool inspector to start with the deployment's saved context and settings.
While the run is active, Run becomes Cancel. Cancel requests that the tool stop. A step that has already begun may need to reach a cancellation point before it stops.
What Appears in the Inspector
The Tools page can show:
- Step status and messages.
- Streamed AI text.
- The final output.
- Failure information.
- A path and actions for a file created by a step.
Clear output removes the displayed step cards and output text from the inspector. It does not delete created files, undo a run, or remove stored history.
Created-File Actions
When a step creates a local file, its step row can provide actions for opening or copying the result.
Open Document
Open document opens the created local file in ThinkForge.
Copy File
Copy file puts the file itself on the clipboard for pasting elsewhere and adds it to Smart Clipboard history. It does not copy only the file path or text contents.
Copy Content
Copy content copies the text inside the created file and adds it to Smart Clipboard history. This action appears only for file types that ThinkForge can copy as text.
Where Files Are Saved
If the tool supports a configurable destination, use Save New Files To in its inspector.
- Choosing a folder creates a new file in that folder.
- Some run surfaces can supply an existing document; the tool may append a new section instead of replacing it.
- A tool step with its own fixed destination takes priority over the deployment destination.
- With no configured destination and a project open, output normally falls back to the project's
_capturedfolder.
When Process each input file separately is enabled, a file-writing tool creates one output for each input file and avoids overwriting an existing name.
Open-document warning: if a tool appends directly to a document that is also open in the editor, the editor may still hold an older copy. Saving that older copy can overwrite the appended section. Prefer a document that is not currently open.
Results on Other Surfaces
Power Strip — shows run feedback and may show only a summary when the result is written to a file.
Mobile Dashboard — shows status, messages, output documents, cancellation, and approval requests.
Chrome extension — confirms that execution started but does not return the final result.
Trigger — records its last run time and success or error state.
Automation — passes each result to the next connected tool and reports the final result.
ThinkForge MCP — does not run user-created tools.
Errors and Partial Results
In a normal run, a failed step prevents later steps from running.
When processing files separately, one file can fail while later files continue unless the run is cancelled. The result preserves each file's success or error.
There is no resume-from-failed-step action. Correct the input, settings, credentials, or tool, then run it again.
Execution History
Trigger runs have durable history. Manual runs from every surface are not yet recorded consistently, so stored history is not a complete audit trail.