A command behaves oddly, reports an unknown flag, or a command is missing after updating. Check cfa plugin status and cfa --version, then bring the CLI and every engine install to the same build with cfa self-update and cfa update-all.
A command behaves oddly after an update, reports an unknown flag, or a command you know exists is missing. Usually the CLI and the installed plugin are on different builds, or one engine still has an older plugin than the others.
Check what is installed where
This lists every engine and project install with its version, and flags any that are behind:
See what is installed where and whether it is current:
bash
cfa plugin status
Check the CLI version too:
bash
cfa --version
Bring everything to the same build
Close the Unreal Editor first. The plugin file is locked while it runs, and an update that cannot write leaves the old build in place.
Update the CLI itself:
bash
cfa self-update
Update the plugin everywhere it is installed:
bash
cfa update-all
Or reinstall the newest build for one engine:
bash
cfa install-plugin "E:/Unreal/UE_5.8"
Per engine, not per machine
The plugin is installed per engine or per project, so UE 5.6, 5.7 and 5.8 each carry their own copy. Updating one leaves the others where they were, which is why cfa update-all exists. If you only ever see the problem in one project, check that project's engine specifically.
Note
After updating, reopen the project and confirm the panel reports the new version. If it still shows the old one, the editor was open during the update.