Local-first Windows utility

Cut the busywork.

Run repeatable file workflows from Explorer. Knife keeps heavy tools isolated, visible, and one right-click away.

13isolated plugins
21catalog tools
3quality gates

The Hub

Useful detail. No ceremony.

The interface separates discovery, execution history, diagnostics, and global preferences. Native-only actions stay explicit in browser preview mode.

How it works

One file. One tool. A clear result.

Knife puts a strict contract around every plugin, so setup, execution, progress, and output stay inspectable.

Discover

The Hub reads the local plugin catalog and shows supported file types, setup state, and Explorer availability.

Validate

`knife-cli` verifies the manifest, prepares an isolated environment, and streams a small status protocol.

Execute

The selected workflow runs beside the file, while the Hub records progress, failures, and output locations.

Architecture

Small parts. Hard boundaries.

The desktop surface, Rust runner, and plugin catalog stay separate so a heavyweight dependency cannot destabilize the entire toolbox.

hub/

Knife Hub

Tauri 2 and React provide discovery, configuration, diagnostics, and execution feedback.

crates/knife-cli/

Runner

Rust validates manifests, prepares plugin sandboxes, and connects Explorer actions to local tools.

plugins/

Workflows

Each plugin owns its contract, requirements, user interface, and execution environment.

Keep local tools close to the files they change.