Upgrade
driverforge keeps itself, the Anvil Agent, and your embedded SDK current. Here's how
the pieces fit.
The driverforge CLI is in preview. Commands and flags documented here may change
before the stable release. Follow along or share feedback on our
roadmap.
Update notices
After a command runs, the CLI checks — at most once a day, cached — whether a
newer driverforge release is available, and prints a one-line notice if so. It's quiet
by design: the notice goes to stderr, never stdout, and never appears in CI or
non-interactive shells. Turn it off with --no-update-check.
Upgrading the CLI
driverforge is installed by a package manager, which owns the binary — so you upgrade
it the same way you installed it:
brew upgrade driverforge # macOS
scoop update driverforge # Windows
# Linux / WSL: re-run the install script
driverforge upgrade shows everything upgradable in one place — the CLI
(advisory: it prints the exact command for how you installed it) and the agent —
and applies them interactively.
Upgrading the Anvil Agent
driverforge agent upgrade updates the Anvil Agent on
the selected controller to the latest release.
Upgrading the SDK
The Anvil SDK is embedded in your driver. Re-run
driverforge init --sdk-version <x.y.z> to re-embed a different SDK build.