DOCUMENTATION
From selection to action.
Understand the workflow, the tools and the boundaries. These guides describe the current development direction, ahead of a public desktop release.
The everyday workflow
PowerTrove matches typed selections. Detecting an application does not automatically mean that all of its content is supported. An action also needs its pack and a compatible local engine.
- Select files in File Explorer, or content in an app with a supported context provider.
- Invoke PowerTrove using the shortcut configured in the desktop application.
- Search the compatible actions and navigate with the keyboard.
- Review parameters and planned outputs before confirming a file-changing operation.
Actions live in packs
Files covers archive and checksum workflows. Images covers conversion, resizing and metadata. PDF covers page operations. Media covers supported audio and video conversions. Tables exports supported selections to common data formats.
Format support varies by engine and installed codecs. Optional packs are designed to be downloaded on explicit request. Worker protocol v1 currently supports file selections; a built-in table action is not automatically compatible with an external worker.
Keep your content local
Core actions run on your computer. Selected file paths, content and desktop search queries do not need to be sent to the web platform. Online marketplace browsing and pack downloads are separate from those workflows.
This website’s demo only simulates a workflow. It does not run the desktop application, read files or upload content.
Community packs
The marketplace is being developed as a curated distribution channel. Its editorial directory will complement a separately signed executable pack catalog. Ratings or descriptions must never make a pack executable.
The current SDK example is repository-local and is not a published NuGet package. The developer guide links directly to the inspected revision.