The boardto name
Watch load, name what is wrong, talk to an agent that uses tools, and run allowlisted fixes only after you say so.
Name what is wrong.
Fix it only after you say so.
Color from a diagnosis
Green, yellow, and red come from an investigation, not a CPU threshold. Gauges can sit high during real work and the board can still be green.
An agent on this PC
Not a generic chatbot. It looks at a snapshot, disk busy vs disk full, top processes, and open incidents — then names one problem.
Consent is the product
That’s fine, I’m busy, Fix this, Looks Good, Grant Admin Permission. Typing in chat is not approval. Deep system never runs unattended.
Sensors stay here
The board binds loopback only. A billed turn may send a snapshot to the hosted model. The OpenRouter key never sits on this PC.
Three steps.
One machine.
1LaptopHealthSetup.exe23Start Menu → AIOS Agent4Optional: start hidden in the tray56Binds loopback only
Local by
default.
Not a fleet dashboard. Not a remote admin console. The unit of product is one signed-in human on one Windows PC.
What this board
does not fake.
What actually
sits on the path.
Sign-in, sensors, the local window, and a hosted model that never stores its key on this PC. Not two hundred logos.
Nothing silent
on first run.
This is privileged software on your PC. The latch is the product, not a policy overlay. We do not claim SOC 2 or HIPAA.
Loopback only
The board is served on localhost. There is no remote view of your gauges.
Consent latch
That’s fine, I’m busy, Fix this, Looks Good, Grant Admin Permission. Typing is not approval.
Sensors stay local
A billed turn may send a snapshot to the hosted model. Live gauges do not leave this PC.
UAC for admin work
Access denied opens Grant Admin Permission. Dismissing UAC cancels. Deep system never runs unattended.
Investigator.
Then operator.
Eyes and hands on this PC, not a coding agent. If the allowlisted tools cannot do the ask, it may propose the exact command — still on the confirm card.
Allowlisted first
Known health fixes before a free-form command.
Confirm card
A host command still needs Looks Good.
Retries
Does not stop on the first tool error.
No dump into chat
Host output stays in the terminal pane.
snapshotdisk space vs disk busytop processesbaseline, open incidentsrules, recent trend
Color from a diagnosis, not a threshold. High CPU is not always a problem.
Board
Lamp, this machine
Green during real work
What this product is not
Pay for turns,
not gauges
Packs show on Profile after Google sign-in. Gauges, confirms, and sensor ticks do not debit.
Board
Lamp, gauges, and feed. What’s wrong waits for credits.
- Live gauges on this PC
- Diagnosis color, not a threshold
- Feed cards: That’s fine / I’m busy / Fix this
- Confirms do not debit
- Sensor ticks stay local
Agent turns
Credits, bought on Profile after Google sign-in
- Ask in plain language
- Tools on this PC
- What’s wrong uses the same meter
- Local guess when the model is down: no debit
- Out of credits: Agent stops until you buy more
Hosted model
The key stays off this PC
- The hosted proxy holds OpenRouter
- Snapshot only on a billed turn
- Buy packs on Profile after Google
- Credits live on Profile, not Settings
- Packs appear after billing is up
Credits are the user-facing currency. Held credits are in-flight holds, not spendable. Read the terms draft
Ready to name
what’s wrong?
The Windows app is the product. There is no hosted board. Install it, sign in with Google, and keep the lamp quiet until this machine is struggling.
Windows only. Binds loopback.