Field validation

Wisely is looking for people to tell it what doesn't work

Nobody except its maintainer has used this tool yet. That is the single most important problem the project has right now, and no amount of extra documentation will fix it.

So we are not looking for users. We are looking for people who can tell us where it breaks, where it is confusing, and where the numbers on screen mean nothing. “I didn't understand the output” is more useful to us than “looks great”.

Five minutes
One clone, one command. You can delete the folder straight afterwards.
Read-only
The diagnostic writes nothing: not to your .wslconfig, not to disk.
No installation
No scheduled task, no system change, no alias to set up.

Try it

Windows 10 (build 19041+) or Windows 11, WSL2 installed, PowerShell 5.1 or later. Nothing else.

git clone https://github.com/Thurxm09/Wisely.git
cd Wisely
pwsh ./wisely.ps1 -Diagnose

Reading inside your Linux distributions is off by default: the diagnostic works without it, and tells you what it would add if you allow it.

What the command answers, in this order

1What is happening? .wslconfig validity, autoMemoryReclaim state, sparseVhd, running distributions, VHDX size.
2Why? The RAM ceiling read from .wslconfig, expressed as a share of your machine's RAM.
3Is it dangerous? Memory attribution per process, with its unattributed remainder shown explicitly.
4What can I do? And, very often, why nothing you could change would help.

Tell us what happened

Three paths, shortest first. The first one has a single required field, and that is deliberate: a thirty-second report beats a thorough one you never send.

Quick feedbackOne dropdown, everything else optional. Including if you gave up before trying.30 s Detailed feedbackWhat you were trying to find out, what you didn't understand, what you did next.5 min Security problemPrivate channel, never a public issue. No redaction needed: the channel is confidential.private

Before pasting any output

The diagnostic output contains your distribution and process names. Those often carry a client, project or employer name. Never paste them as-is into a public issue.

pwsh ./wisely.ps1 -Diagnose -Redact

This option replaces those names with pseudonyms (distro-1, proc-1) and strips absolute paths, while keeping every figure, unit and confidence level intact. Read it over anyway: it covers the fields Wisely knows about, not what you type yourself.

What Wisely doesn't do yet

Saying so now is cheaper than disappointing you in ten minutes.

No consumption history — it reads the current state; it doesn't know what your machine did last week.
No sized recommendation — it won't tell you “set 6 GB” until it can prove that number from a measurement. A deliberate constraint, not a gap.
No disk reclamation — it explains the gap between real usage and VHDX size; it compacts nothing.
No package to install — neither PowerShell Gallery nor Winget. Packaging comes after the tool is proven useful, not before.

What happens to your feedback

It is triaged on severity, frequency and how much the signal can be trusted — a single report opens a question, it does not trigger a fix.
If it leads to a change, it is cited in the changelog and you are thanked by name, unless you ask otherwise.
You are notified when it ships, not only when it is fixed.
If it leads to nothing, we tell you why. Feedback we set aside is set aside with a reason, never in silence.

And if nobody uses this tool, that is a result too. It would be recorded as such — more useful than carrying on building a product without knowing who it is for.

See the code and the documentation