Updates

At most every twelve hours, ArcFlare checks GitHub in the background, in a separate process with a four-second timeout, so nothing you're doing waits on it. When something newer exists, the menu, chat and agent show one line:

  ↑ Update available: 1.1.0 → 1.2.0 · /update or arcflare update

A git clone also compares commits, so changes pushed without a version bump still show up. A clone that is ahead of main is never told to update backwards.

In a session, type /update. From a shell:

A session that runs /update keeps running the code it started with. Restart arcflare to use the new version. Check right now, without installing, with arcflare update --check.

Offline, the background check fails without a word. That's a normal state, not an error, and nothing waits on it. To update a machine that never sees the internet, carry the update over. ArcFlare has no dependencies, so one tarball is the whole program:

1. On a connected machine

  ✓ D:\arcflare-1.2.0.tgz
  carry it to the offline machine and run: arcflare update --from "arcflare-1.2.0.tgz"

--pack <folder> writes it somewhere else, such as a USB stick.

2. On the offline machine

• --from also takes a folder: a git clone on the stick is pulled from, exactly as from GitHub.
• A plain folder is packed first and then installed, because npm install -g <folder> links rather than copies, and that link breaks when the stick comes out.
• Nothing in this path contacts a package registry.
• The source is checked first. A folder that isn't ArcFlare is refused before anything runs.

arcflare update --on turns them back on. For one environment, set ARCFLARE_NO_UPDATE_CHECK=1. Checks are skipped automatically when CI=true, and never run for arcflare mcp, whose output is a protocol.