# What is still running after you close a window?

PerformanceDaddy · Significant Hobbies · 2026-09-19

Inspect background apps and helpers without treating every unfamiliar process as a problem.

## Start with the work, not the process name

A process you do not recognise is not automatically something to remove.
First check whether it belongs to an app you use and whether its resource
usage changes while you reproduce the slowdown.

PerformanceDaddy can show process duration, resource readings and matching
startup metadata. Those are useful clues. They do not establish why an app
launched a helper, or prove that stopping it will make your task faster.

## Check before stopping

Inspect the target and its role. A normal stop and a force stop are different
actions, and either can interrupt work. Force stopping can lose unsaved data.
PerformanceDaddy requires a review before either action.

## When something comes back

The app watches for matching executables after stops you request through it.
A matching executable is not proof of an automatic restart or its cause.
This observation history is bounded, stays in memory and clears when you quit.

PerformanceDaddy is a local development preview, without a public download yet.