Most people's first worry about letting an AI near their computers is the same: what if it deletes something. So don't start there. Spend the first week on questions that only need looking.
Here are three. Each one comes with the manual way first, because you should be able to do it without any tool, and then what it looks like when your AI does it for you.
Why is my disk full?
By hand. On Windows, open PowerShell and list the biggest top-level folders:
Get-ChildItem C:\ -Force -Directory | ForEach-Object {
$s = (Get-ChildItem $_.FullName -Recurse -Force -File -ErrorAction SilentlyContinue | Measure-Object Length -Sum).Sum
[pscustomobject]@{Folder = $_.Name; GB = [math]::Round($s/1GB, 2)}
} | Sort-Object GB -Descending | Select-Object -First 8On a Mac or Linux machine, du -xsk ~/* | sort -rn | head does the same for your home folder.
Two things catch people out. First, a full scan of a big disk takes minutes, not seconds; on my Windows machine it took about two and a half. Second, on a Mac the obvious command lies: df -h / shows only the small system volume. Your files live on a separate one, so check df -h /System/Volumes/Data instead. The folder sizes also never add up to the used space, because of system files and folders you don't have rights to read. Expect a gap.
With your AI. Ask: "Why is the disk on my work PC almost full? Show me the ten biggest folders and tell me what each one is. Don't delete anything." You get a ranked list in plain words ("this is an app cache, that is your photo library, that is old installers") instead of a wall of numbers. The deleting, if any, is a separate step that starts only after you say yes.
Why is it slow, or why did it restart?
By hand. How long has it been on, what is using the memory, how many programs start with it, and did it restart by itself. On Windows:
$os = Get-CimInstance Win32_OperatingSystem
"Uptime hours: " + [math]::Round(((Get-Date) - $os.LastBootUpTime).TotalHours, 1)
Get-Process | Sort-Object WS -Descending | Select-Object -First 5 Name, @{n='MB'; e={[math]::Round($_.WS/1MB)}}
(Get-CimInstance Win32_StartupCommand | Measure-Object).Count
Get-WinEvent -FilterHashtable @{LogName='System'; Id=41,1074,6008; StartTime=(Get-Date).AddDays(-7)}On a Mac, uptime, last reboot | head and ps -Aceo rss,comm -m | head cover the same ground.
A quiet answer is still an answer. If the restart log is empty, nothing restarted it, and your slow day has another cause. One of my machines had been running for 53 days without a reboot, which explained more than any single program did.
With your AI. Ask: "My laptop feels slow. Check how long it has been on, what uses the memory, what starts at login and whether it restarted recently, then tell me the most likely cause." The useful part is the last sentence. You get one conclusion, or an honest "I didn't find a clear cause", and you can ask for the evidence behind it.
Did my backup copy everything?
By hand. Compare the original and the copy. On a Mac or Linux machine diff -rq source backup lists files that are missing or differ. On Windows, hash both folders and compare:
$s = (Resolve-Path .\source).Path; $d = (Resolve-Path .\backup).Path
$a = Get-ChildItem $s -Recurse -File | ForEach-Object { [pscustomobject]@{P=$_.FullName.Substring($s.Length); H=(Get-FileHash $_.FullName).Hash} }
$b = Get-ChildItem $d -Recurse -File | ForEach-Object { [pscustomobject]@{P=$_.FullName.Substring($d.Length); H=(Get-FileHash $_.FullName).Hash} }
Compare-Object $a $b -Property P, HI tried this on a test folder where I had deleted one file and edited another in the copy. Both showed up straight away: one missing, one changed. A comparison by size and date is faster; one by content is slower but catches more. Say which one you want.
With your AI. Ask: "Compare the Photos folder on my desktop with the copy on the external drive. List what is missing or different. Don't copy or fix anything." You get a short list of exceptions instead of a feeling that it probably worked.
Why start here
None of these changes a file. If the AI misreads something, the worst result is a wrong sentence, and you can check it against the commands above. After a week of that, you know how it answers, how it explains itself and how often it says "I'm not sure". That is a better basis for the day you let it change something.
I build Local Commander, so this is the setup I tried it with: a small agent on each computer, and your ChatGPT or Claude chat connects to it. Every example above ran on my own Windows PC and my own Mac. It works through commands and files, not through the screen, so it won't click a dialog for you, and the computer has to be on. You choose what each computer allows, and you can switch any of them off.
If you try the three questions on your own machines, I'd like to hear which one gave a useful answer and which one didn't.