A command comes back as unknown because the installed plugin is older than the CLI. From plugin 1.13.0 and CLI 2.16.0 the error names both versions and the fix. Check with cfa health_check or cfa check-updates, then bring everything to the same build with cfa self-update and cfa update-all.
A command you know exists comes back as unknown, or something behaves oddly after an update. Almost always the CLI and the installed plugin are on different builds. The CLI updates in seconds, the plugin needs the editor closed, so the plugin is the one that falls behind.
From plugin 1.13.0 and CLI 2.16.0 the tool spots this itself. An unknown command now names both versions and the fix instead of just handing back the command name, so you rarely have to diagnose it by hand:
Unknown command: set_bt_breakpoint That editor is running plugin v1.11.2, but this CLI (v2.16.1) ships against plugin v1.13.0. Commands added after v1.11.2 do not exist in that editor yet, which is why the name is unknown. Update the plugin, with the editor closed: cfa update-all
If you drive cfa through an AI assistant, it sees the same explanation and can pass it on. On an older plugin that cannot report its version you get a shorter hint pointing at cfa check-updates.
Both versions, what is published, and a warning if they do not match:
cfa health_checkEvery engine and project install, with what each one is missing:
cfa check-updatesJust the CLI:
cfa --versionClose the Unreal Editor first. If you forget, the update now refuses and names the editor to close rather than failing partway through.
Update the CLI itself:
cfa self-updateUpdate the plugin everywhere it is installed:
cfa update-allOr reinstall the newest build for one engine:
cfa install-plugin "E:/Unreal/UE_5.8"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.