← All guides

Update Halo with your agent

Keeping Halo current is one sentence: tell your agent to update Halo to the latest version. It refreshes the CLI, restarts services, and verifies — wallet untouched.

If your agent runs Halo for you, updating is one sentence:

Update Halo to the latest version

That’s it. Your agent handles the mechanics and reports back.

What your agent does under the hood

  1. Refreshes the CLI — removes the old global link and re-runs the installer from warden-protocol/run-halo (the installer skips itself if halo is already on PATH, so the removal step is what makes it an update).
  2. Restarts any always-on service it installed (halo service uninstall + install for serve or consume), so the daemon actually runs the new code.
  3. Verifies with halo doctor --json — install state, wallet, provider, and relay health in one call.

Prefer to run these steps yourself? They’re spelled out in update the halo CLI and update your operator.

Refresh the skill too

The Halo skill your agent follows is fetched from the web, so it can go stale independently of the CLI. Point your agent at it again to pick up the latest instructions:

Read https://app.runhalo.xyz/skill.md and follow the instructions

The skill lives separately from ~/.halo/ — re-reading or reinstalling it never touches your wallet.

Your identity is safe

Updates never touch ~/.halo/ (wallet, config): the wallet address, earnings, League points, and dashboard pairing all carry over. A well-behaved agent will never rotate your wallet during an update — --rotate-wallet is only for an explicit “start over with a fresh identity” request, and it’s irreversible.