Choose input and a place to run your Tool that match the workflow. These limits affect what you can rely on during a run.
Connect Tools with an automation
A single Tool runs its actions in a fixed order. It cannot branch between its actions or call another Tool as an action.
Use an automation when several Tools need to work together, choose paths with rules, or bring results together. See Automations Overview.
Check settings before unattended runs
A desktop run does not check every credential and service setting before starting. Missing configuration can be discovered when the affected action runs.
Run a small test with representative input before enabling a schedule or file watch. Copied triggers start paused so you can review them.
Power Strip and triggers automatically confirm interaction requests. They will not wait for you to review a guided AI result.
Recover from a failed run
A failed action stops the workflow. There is no automatic retry or resume from that action.
Cancellation usually takes effect after the current action finishes. Python processes and active webpage requests can be stopped sooner. Check existing output before repeating a task that writes files.
Displayed and recent runs are not a complete, permanent history of every execution.
Choose reference files an AI Tool can use
AI actions read supported local text references as guidance. Invalid or oversized files stop the run. A Tool without an AI action warns and continues without using references.
See Context and Input for accepted files and limits.
Capture a page that needs your browser
A webpage-retrieval Tool can read public static pages. It does not use your signed-in browser session, run a site's JavaScript, interact with page controls, or bypass access restrictions.
Use Chrome capture through the desktop companion extension when you need the content of an open page.
Configure local scripts yourself
A Python Tool needs an installed interpreter, an existing script, its required packages, and your approval for the selected script version. ThinkForge does not install packages, repair the script, or sandbox it.
The script runs with your user-account permissions. See Python Script Tools.
Use the desktop to run user Tools
ThinkForge MCP does not currently list or run user-created Tools. The Chrome extension's Tools tab opens the desktop Tools page rather than providing a browser Tool library or completed results.
Use the Tools page or a configured desktop placement.