Beta Status
The Chrome extension does not provide a browser-native tool library or result viewer.
Its Tools tab is a desktop launcher. When TF Desktop integration is enabled and connected, the tab can:
- Open the desktop Tool Dashboard
- Open desktop SK Memory Search
- Configure a project folder whose text documents appear in Chrome's context menu
The browser tab does not let you select a tool, submit captured content to it, and read the returned result.
What the Extension Can Start
Extension code can start a tool by ID or name with supplied text content, along with the page URL and title. The desktop finds the tool, builds a web-page context, and runs it headlessly.
This is fire-and-forget. The immediate response confirms that execution started and names the tool. It does not wait for completion and does not return the tool's output to the extension.
Listing tools from the extension is not implemented.
Browser Content and Power Strip
Power Strip's Browser Agent and Run Automation commands can request the active Chrome page, receive the captured content, and then run a tool or deployed automation on the desktop.
That workflow starts from Power Strip. It is separate from the extension's Tools tab.
Current Limitations
- The extension cannot list tools.
- The Tools tab does not expose a run action.
- A run started from the extension does not stream status or return final output to Chrome.
- Headless execution auto-confirms interaction requests.
- Browser Agent results appear through desktop and Power Strip feedback. Reference sources and output-document presentation have their own beta limitations.
- Tool execution through ThinkForge MCP is not implemented.