Use Power Strip's Agent and Automation buttons to run configured workflows without opening the full Tools page. Each button keeps its own settings and saved input.
Choose and run a Tool
Choose a Tool for an Agent button. Power Strip opens that button's configuration panel.
Under Input, choose Choose Files... or drop files or folders into the input area. This selection applies to the current run. Choose Save as default input when it appears to use the selection next time. Reopening the panel restores the saved default; cancelling the file picker leaves your current selection in place.
The footer runs with the input shown in the panel. Its label may still say “no input” after you select files, but the run uses your selection.
You can also drop files, folders, or text directly on the Agent button to run with that material instead of saved input.
Configure a Tool button
Use Tool Configuration for the selected Tool's settings. Changes apply to this button's placement.
AI-backed Tools show AI Reference Rules and reference-file controls. Their saved local text files supply supporting guidance without replacing the main input. See Context and Input for accepted files and limits.
Save New Files To appears when the Tool can use a configurable destination. Otherwise, Save Location explains why there is no folder picker.
Separate buttons can use the same Tool with different settings. They still use the shared Tool workflow: editing or deleting that workflow affects every placement that uses it.
Run Tools attached to a folder
Open a Folder button's panel to see the Tools attached to that project folder. Run a listed Tool with the folder as input, or choose Manage Folder Tools... to attach, configure, reorder, enable, disable, or remove placements and manage their triggers.
This is the same folder Tool list used by Project Navigator and linked Project Map nodes. Changes appear everywhere that folder's Tools are shown.
A folder Tool is separate from a before or after hook on the Folder button.
Choose and run an automation
Use Change Automation on an Automation button to choose from the shared library. You can also choose an automation for an Agent button.
Each button gets its own placement and connected Tool settings. Replacing or removing a button removes its private placement.
The panel provides:
- Documents or folders for saved input.
- Optional guidance for local text references read by AI-backed Tools.
- Save New Files To when the connected Tools can use a shared destination.
- Tools in this automation, which expands to each Tool's Settings.
Choose Run Automation to use saved input. If none is saved, the run starts with empty input. Dropping files, folders, or text directly on the button supplies input for that run instead.
The panel has no Stop control. Closing it or the Activity cards does not stop execution. See Running Automations.
Run with the active Chrome page
Browser Agent and Run Automation request content from the active Chrome tab and run the chosen workflow on the desktop. They need a connected desktop companion extension and a page that can supply the requested content.
Browser Agent's AI actions can use saved reference text. Its saved output-folder choice is not currently applied to browser runs; check where any generated file was saved.
See Browser Commands.
Attach a before or after hook
A hook is a Tool that runs around a supported Power Strip action. Use the command's right-click menu to choose a before hook, an after hook, or both. The choice belongs to that button.
A before hook runs first. It does not rewrite, cancel, or replace the command's action.
An after hook runs after the action reaches its completion point. A capture after hook can use the saved document.
When both are present, the order is before hook, command action, after hook. A successful command does not prove that its hook succeeded.
Actions that support hooks
Hooks run for:
- Quick Note after the note is saved.
- Save Clipboard when selected.
- Drop File and Folder drops.
- Folder footer capture actions after content is created.
- Agent and Automation runs or drops.
- Capture Page and Capture Selection after the browser capture is saved.
- Browser Agent and browser automation runs.
Create Doc From Clipboard may offer a Content Created hook, but that hook does not run.
What a hook receives
Drop hooks receive the dropped files, folders, or text. Quick Note's after hook receives the saved note. Browser capture after hooks receive page information and the saved document.
A Folder button supplies its bound folder. Agent and automation runs use available saved input when there is no drop. After hooks can receive output paths when the main action saved files.
Save Clipboard click hooks receive information about the action and its result rather than the clipboard contents. Saved reference files in hook configuration are not supplied to hook runs.
Before and after hooks on button drops and Folder-panel drops use their configured output folder. Attaching a Tool to an input folder does not automatically make that folder its output destination.
Check progress and results
Select Power Strip's fixed Activity bell to see progress, outputs, and errors. Select a run's card to expand its details. Closing the cards hides them without stopping work.
Each concurrent run keeps its own card. The command button may also show status, and Power Strip glows while work is active.