Use Power Strip's browser commands to save or capture content from the active Chrome tab and run a configured Tool or automation with that page as input.
Visibility and Connection
Keep ThinkForge running and connect the desktop companion extension. Browser commands appear while Chrome is the foreground application:
- Chrome in the foreground makes the buttons visible.
- An active extension connection is required to execute them.
- A visible button can therefore return "Chrome not connected."
The buttons carry a browser badge to distinguish them from desktop-only commands.
Command Catalog
Save Chat
Saves the active tab's conversation into the current ThinkForge project. Each Save Chat button has its own save settings and optional metadata fields.
Tag Page
Runs the save-with-tag flow for the active page or conversation.
Capture Page
Captures the active page. Its per-slot settings include:
- Capture mode: clean scrape, snapshot, or metadata only
- Save mode: Markdown, Markdown plus JSON, or metadata only
- Optional metadata fields
On supported chat sites, capture can use the platform's conversation structure rather than treating the page as a generic article.
Capture Selection
Captures the current browser selection and imports it into the active ThinkForge project.
Capture Page and Capture Selection can trigger an after agent hook once the imported document is available.
Previous Q&A and Next Q&A
Moves through question-and-answer pairs, using platform-specific navigation where available.
When invoked from Power Strip these still require the extension connection, to reach the active tab.
Personas
Opens the extension's Personas surface.
Template
Opens the extension's Forge Doc template surface.
Dockit
Not functional in this version. The button is present, but the desktop-triggered action reports "Dockit module not yet available."
Browser Agent
Opens a Power Strip sidecar for selecting and configuring an agent. At run time, the desktop requests content from the current browser page and runs the bound agent without further input.
AI actions can use the deployment's saved local text references as supporting guidance. See Context and Input for accepted files and limits.
The output folder saved in this sidecar is not applied to browser execution. Check the produced file's location in the result.
Run Automation
Requests current-page context from Chrome and runs it through the bound automation.
Per-Slot Settings
Save Chat and Capture Page expose a browser settings sidecar, stored against that individual command slot. Other browser commands do not use that panel.
Wait for the capture to finish
A browser capture must reach ThinkForge before its preview or after hook can use the saved document. Starting the command does not mean the file has finished saving.
Preview on Save opens the saved document after it arrives. An after hook on Capture Page or Capture Selection can then run with that document.
Requirements
Browser Commands require:
- ThinkForge desktop running
- The Think Forge Extension desktop companion installed
- A connected extension
- An active browser tab that supports the requested operation
Content extraction and navigation quality depend on the active site and its current page structure.