Claude Code notifications and PC health

A notification when a session asks something, needs permission, finishes, stops midway or hits its limit, and when an account reaches 80 or 95 percent. Click it to open the session. You choose which kinds you want for each project, and how much detail they show, down to no names at all. The background engine sends them even when the window is closed. Built and tested, but we have not yet seen one appear on screen: Windows on our test PC showed no notices from any program.

Critical alerts in red, then warnings, good news in green and plain notes, with new critical ones first. An alert closes itself once its cause has gone. Alerts from all your computers land in the same column.

By default only critical alerts make a sound, and you can set quiet hours. A few urgent kinds still get through, such as a budget that has run out.

Short notes go to a Telegram bot you own: the project, the session and what happened. Never the conversation itself, and the bot takes no commands. Each message is checked letter by letter after it is sent and retried without duplicates. If Telegram has been unreachable for five minutes, you are told. So far this has only run in tests: no real message has been sent to a bot yet.

Today Telegram gets the notes about sessions. Sending every kind of alert there as well is the next step.

Write down the jobs no agent can do for you, with a date and a project if you like. Due ones turn into alerts. You can paste in a whole list at once. Built and tested in the engine, but not yet tried on screen with real reminders.

A chip on each project card turns red when the project uses far more than it usually does. Click it to see which program of which session is using what. GPU use is read from Windows' own performance counters.

Programs that kept running after their session ended are listed with their project, their age and what they use. They are closed only when you click, one at a time or all together.

You get an alert when a session goes past a memory limit (4 GB unless you change it), or starts too many copies of the same program.

Scheduled tasks, Run keys, the Startup folder, pm2 processes and programs started by nothing known, grouped by the project they belong to. For each one you see how it starts, when it last ran and how that went. One that nobody registered is marked unknown. On one development PC it found 57 of them in 3.4 seconds.

Run a job, stop it, turn it off, take it out of autostart or put it back. Before anything changes you see, in words, what will happen, how to undo it and the exact command that will run. Tested on a task that the test makes and removes. A first real stop of one of your own jobs has not happened yet.

Five minutes after boot, AigoPilot checks that the jobs that should have started really did, and tells you about any that did not. Built and tested, but not yet seen after a real Windows start.

Turn this on and sessions are told to register any background job they create, so you always know which project a job belongs to.

Each computer stays awake while a session is working, plus ten minutes, or however long you set for that computer. Built for Windows and for macOS. It has not yet been checked in Windows' own list of power requests, and a Mac with its lid closed goes to sleep regardless.

Once a day, while nothing is running, Claude Code and Codex update themselves on each of your computers. A Codex install that cannot update itself gets OpenAI's own installer.

With the window closed, AigoPilot used about 0.1 percent of one CPU core, and its background engine about 35 MB of memory. Nothing on screen animates unless you are using the window.

A picture, a few words and a button that opens a link are shown once when the studio starts. They come from a single file on aigopilot.com, and nothing is shown if the file cannot be reached.

A warning for a job that reports it finished but is still running, and for output nobody has opened in 15 days. Reading LaunchAgents and crontab on a Mac.