A careful workflow for computer maintenance
Keep your computer moving. Use your AI assistant to understand what needs attention, review the choices, and coordinate supported work you approve.
Developed by Michael
Codex is the primary workflow. Claude Code and OpenCode require capability checks.
Your first run
Start in your assistant Open the source folder in a capable local assistant, then use this request.
Use these commands in your assistant’s conversation, not as operating-system shell commands.
Follow the guide step by step → Start in your assistant
Open the source folder in a capable local assistant, then use this request:
Read AGENTS.md and .agents/skills/pc-maintenance/SKILL.md from this project.
PatchCairn: start
Show the menu and explain my choices.
Wait until I choose a job and authorize its
scope before collecting information.This is an example request, not a live session.
Choose the job that fits Each job begins with agreed scope and an explanation of the next useful step.
How a session works Assessment, approval, an attempted action, and a verified result are separate steps.
An assessment can end after findings without making changes. Ask for the findings, remaining uncertainty, and the next useful choice.
Choose a job. Start with the menu and select the kind of help you need.Agree scope. Select exact information or folders, exclusions, and privacy limits, then authorize assessment.Investigate. Gather bounded evidence and relevant official information.Explain findings. Understand meaning, confidence, unknowns, and the next useful check.Review a concrete plan. See targets, benefits, drawbacks, costs, recovery limits, and verification. Two independent reviews examine a change plan.Approve supported work. Choose the clearly identified actions you authorize in ordinary language.Verify and finish. Check actual results, explain remaining concerns, and choose what evidence and recovery material to retain.Follow your first run step by step
Choose control and timing separately Guided assessment now is a useful starting point. Settings do not expand earlier approval.
How work proceeds
Guided Review explanations at selected checkpoints. More opportunities to decide, with more pauses for your attention.
Automatic within an approved policy Continue unchanged routine work within exact authorized boundaries. This needs clear limits and stop conditions. When work begins
Now Begin agreed work while you are available. An interruption or restart may need a separate decision.
Scheduled Propose a later time. Actual schedule creation requires supported host capabilities and your authorization. Some decisions always need attention. Authentication, OS consent, missing required recovery, stale evidence, unknown outcomes, unsupported capabilities, and material scope changes never become automatic. A schedule grants no new permission and cannot silently resume paused work.
Commands you can use in chat Use ordinary language or the PatchCairn: prefix. The assistant handles technical records; you do not need to edit JSON or transcribe identifiers.
PatchCairn: startOpen the menu without creating a session or collecting host information.
PatchCairn: helpUnderstand the workflow and available commands.
PatchCairn: statusSee completed work, active work, holds, and the next step.
PatchCairn: optionsReview meaning, benefits, drawbacks, cost, reversibility, and a recommendation.
PatchCairn: costRequest supported estimates and explicit unknowns.
PatchCairn: settingsReview scope, checkpoints, control, and timing without widening old approval.
PatchCairn: pausePrevent new actions and bring active work to a safe checkpoint.
PatchCairn: resumeReconcile actual outcomes and freshness before continuing. Text alone cannot clear a hold.
PatchCairn: stopEnd the session while preserving records and unresolved work. A late receipt does not reopen it.
PatchCairn: resolveInspect a pending item and explain the evidence or choice it needs, without a blind retry. Read the command and session reference
Understand the boundaries The workflow coordinates supported tools. It is not an antivirus, an operating-system sandbox, or a guarantee that every issue is found.
Private records stay local Selected scope excludes browser data, passwords, saved chats, credentials, and unrelated projects from cleanup and broad discovery. Private records remain under owned work/ paths. This website has no computer access or maintenance controls.
Security and privacy Recovery before permanent loss Same-volume quarantine frees no disk space. Integrated purge requires exact verified original backup and restoration coverage, plus a separate permanent-loss decision. Unbacked quarantine can be reviewed for restoration.
Recovery and cleanup Selected backup and update routes The content-backup route is bounded to 16 MiB per file, 48 MiB selected content, and a 64 MiB archive. A ZIP is not encrypted or system rollback. Current update handoffs accept exact reviewed local MSI, PKG, or DEB artifacts; package-manager updates and OS/application repair routes remain held.
Current integration scope What to do after an interruption, failed check, or unknown result
Documentation Start with the walkthrough. Open any guide for grouped navigation to the full documentation library.
Get started Safety and requirements Technical reference Project