Keep a restore skill for when your Bot's computer is updated

How this helps you

A computer update becomes a two-minute restore instead of an afternoon of figuring out what broke.

✦ Try it

List everything you have installed on your computer that isn't part of a fresh machine: command line tools, packages, background services and anything you set up for me. For each, give the install command, what uses it, and a one-line check that proves it works. Save this as a skill called restore-after-update. Don't include passwords or keys; note where I need to sign in again instead.

Fill in: No placeholders. Rename the skill if you like, but keep the name easy to say after an update.

What they did

A commenter asked Kacper Rutkiewicz what happens when the Bot's cloud computer is updated. His answer: your files and logins stay, but anything you installed is removed. He found this out with Tailscale, which disappears after an update and has to be reinstalled. His fix is a restore note or skill: after an update, the Bot reads it, reinstalls everything listed and signs back in where needed. He keeps it separate from his house rules and only points the Bot at it after an update. The changelog says the same thing in the app: updating or recreating the computer explains that files and logins stay while installed apps and packages are removed.

Who it's for: Anyone whose Bots rely on installed tools, especially coding, Tailscale or local-model setups.

Before you start

A Bot that has installed tools on its computer (a CLI, Tailscale, Python packages, and so on).
Settings, Computer, where updates are offered.

How to try it

Before your next update, send the prompt below so the Bot lists what it has installed.
Check the list. Remove anything you no longer use.
Ask it to save the result as a skill called restore-after-update, with exact install commands and a check for each tool.
Update the computer from Settings, Computer.
Afterwards, say: run restore-after-update. Approve any cards it raises.
Ask it to add to the skill whenever it installs something new (we haven't verified this step).

What to expect

A skill listing, say, Tailscale, the GitHub CLI and a few Python packages, each with its install command and a test, and a note on what needs you to sign in.

Common mistakes

Putting the restore steps in your always-on rules. Kacper keeps them separate and only uses them after an update.
Saving secrets in the skill. List where to sign in, not the password.
Updating the night before something important without checking the restore list first.

Related tips

Back up your whole Bot setup: Have each Bot document its job, rules, skills and routines into a recovery doc, kept current monthly.
Check usage and update your Bot's computer in Settings: Where to see how much of your weekly usage is left, and when to update or reset the Bot's cloud computer.
Run Claude Code or Codex on your Bot's computer with your own plan: Your Bot's computer has a terminal, so it can install a coding CLI, you sign in once, and your Bots can use that subscription from anywhere.