RustWTM
GitHubDownload
RustWTM/Documentation

Get your bearings.
Then go deeper.

A practical starting point, with direct links to the maintained product documentation.

START HERE

See first. Decide second.

Install the latest release.

Use the x64 installer on Windows 10 1809+ or Windows 11. The installer includes the background service. Prefer no installation? Choose the portable ZIP.

Choose a download

Start with the system overview.

Check resource gauges and busy apps, then open Processes for a searchable list, process tree or grouped Apps view. Pause process-list updates with F6 to inspect a stable snapshot while monitoring continues.

Review what protection would do.

In the default dry-run mode, the service logs its automatic decisions. Read Events, adjust the configuration and review exclusions before turning on enforcement.

Your rules. Your responsibility.

RustWTM separates read-only observation, automatic policy enforcement and explicit manual actions. The service’s dry_run setting controls automatic decisions. It does not turn manual process actions into previews.

config.toml · Illustrated excerpt
dry_run = true

[governor]
high_cpu_percent = 90.0
sustain_secs = 5
recover_cpu_percent = 70.0

An excerpt, not a complete configuration. Validate your file and review the full reference before applying it.

Rules can match process names or paths, including wildcards, and optionally require sustained CPU, memory or GPU conditions. Actions include priority changes, efficiency mode, caps and termination. CPU percentages use the whole machine as their scale.

App limits share CPU and memory budgets across matching app instances and their children. Foreground protection exempts the active app and its descendants by default. Critical and core Windows processes, and RustWTM itself, remain protected.

Use an elevated client to validate and apply service configuration. Automatic process adjustments are tracked by source and restored when the service stops; shared power-plan settings persist until separately restored. Hardware fan control has additional requirements and validation limits.

Complete configuration reference

Go where the question leads.

Process workspace

List, Tree and Apps views, the adaptive inspector and stable-row behavior.

PRODUCT DOCUMENTATION ↗

Column layouts

Choose profiles, reorder columns and keep your preferred process workspace.

PRODUCT DOCUMENTATION ↗

Performance timelines

Shared cursors, pinning, zoom, live mode and explicit sampling gaps.

PRODUCT DOCUMENTATION ↗

Resource measurements

CPU tiers, GPU engines, resource units and measurement boundaries.

PRODUCT DOCUMENTATION ↗

Local Docker monitoring

Supported contexts, health, logs, sampling limits and read-only behavior.

PRODUCT DOCUMENTATION ↗

Display preferences

Appearance, scale, compact layouts, charts and remembered settings.

PRODUCT DOCUMENTATION ↗

Sensors & cooling

Optional provider setup, hardware support and fan-control validation limits.

PRODUCT DOCUMENTATION ↗

CPU & power controls

Hybrid CPU tiers, affinity and the separate restore behavior of shared power policies.

PRODUCT DOCUMENTATION ↗

Another way into the same system.

The wtm command-line tool exposes process inspection, JSON output and explicit controls. These first commands are read-only:

PowerShell · Read-only inspection
wtm list --sort mem -n 20
wtm list --json
wtm info chrome
wtm ports --known
wtm history --hours 24

Validate before applying.

PowerShell · Configuration inspection
wtm config show
wtm config check my.toml

An MCP server, on your terms.

Run wtm mcp to connect an MCP client over standard input/output. Read-only is the default, and nothing listens on the network. Starting with --allow-control explicitly adds control tools. Elevation requirements still apply.

MCP client configuration · Read-only
{
  "mcpServers": {
    "rustwtm": {
      "command": "C:\\Program Files\\RustWTM\\wtm.exe",
      "args": ["mcp"]
    }
  }
}
All CLI commands & MCP tools

Local tools. Explicit permissions.

RustWTM’s service runs as LocalSystem. It accepts control requests only from elevated administrators over a local named pipe, rejects remote clients and protects its data directory. Read-only requests are available to interactive users.

Usage history and configuration live in %ProgramData%\RustWTM. Optional Telegram functionality communicates externally when configured. Update checks and installer downloads contact GitHub. See the product’s security policy for the actual trust boundaries.

Security model Privacy & data handling

Help make the tool better.

RustWTM is MIT licensed. Report reproducible bugs through GitHub Issues, include the version and steps, and follow the contribution guide for source changes. Report vulnerabilities privately through the security policy.

Report an issue Contribution guide Report a vulnerability privately

The roadmap documents future work separately. A roadmap item is not a promise that a feature is available in your installed release.