Automatic Updates

cfu replaces its own executable with a newer release in the background. This page describes when that happens and the three ways to turn it off.

On every start cfu checks for new releases in the background, and when a newer release exists it downloads it and replaces its own executable after the command has finished. The running command is never interrupted by this, the new version applies to the next call. The check runs at most once every six hours, and it works inside the Vector network only.

It is best effort throughout: a failed download or an unreachable server never fails your command, and every request is bounded by a timeout.

The release server is Vector internal, so the automatic update works only from within the Vector network.

Turning It Off

Three independent switches turn the update off, any one of them is enough:

--no-auto-update

Skips the check for a single call, see the global options.

Env-Var CONFUGAMI_AUTO_UPDATE

Set to false, 0, or off, it skips the check for every cfu call in that environment. Any other value, and an unset variable, leaves the update enabled.

.confu next to the cfu executable

Pins one installation permanently:

{
    executableSettings: {
        autoUpdate: false,
    },
}

This is what the --pin option of the install scripts writes. executableSettings is read from the .confu file in the folder of the cfu executable only.

The MCP server registration that cfu mcp --install writes passes --no-auto-update.