Skip to content
Menu

Installing and updating modules

How the bot installs the modules, checks them every day, and moves to a new version.

On this page

How modules are installed

You do not install anything by hand. The template includes an installer skill that the bot runs in the first chat and at the start of every routine.

  • The template carries a lock file that pins each module to one exact version, with its download address and checksum.
  • The bot downloads the release file and the release's SHA256SUMS file.
  • It computes the SHA-256 checksum of the download and installs only when it matches both the lock file and the SHA256SUMS line.
  • Files go into /workspace/ambitious/bin on the bot's computer. Each module is a single file that runs on Node 24 or Python 3.13; no package manager is used.

If the lock file pins no releases, the bot says so plainly: no modules are installed and no module checks ran. It still writes the first audit Page from what it can see.

The daily selfcheck

A routine named ambitious-selfcheck runs once a day. It runs the installer and then each module's selfcheck command. It sends nothing outside the bot's computer.

A selfcheck reports the runtime version, the checksum of the installed file, the health of the module's database and its data version. It applies any pending database updates and lists problems in plain words.

A module counts as ready only when its checksum matches the pinned one and the problem list is empty. The bot tells you about anything else.

Reinstalling

Ask the bot to run the installer again. Running it is always safe.

  • If the installed file already matches the pin, nothing is written.
  • If the file is missing or does not match, the bot downloads it again.
  • If a download or checksum check fails, the existing install is left as it was.

Grok Bot can reset a bot's computer when you update it. The installer runs again at the next routine start, and your module data stays in the Ambitious folder.

Upgrades

A module changes version only when its pin in the lock file changes. The bot never picks the newest version on its own and never edits the pins.

When a pin changes, the new version is installed beside the old one and the bot switches to it once the checksum matches. The next selfcheck applies any database updates the new version needs.

Installing from a local mirror

The installer can read releases from a folder instead of the network. Download the release files and their SHA256SUMS files into a folder the bot can read, then ask the bot to install from that folder.

The same checksum checks apply, so a file that does not match its pin is refused whether it came from the network or from the folder.