Fix cfa reporting that the bridge is unreachable or the Unreal Editor is not responding. Check with cfa health_check, then work through the usual causes: editor not open, still compiling, plugin disabled, or the plugin failed to load at startup.
A cfa command reports that the bridge is unreachable, or that the editor is not responding. Almost always this means the editor is not running, or it is still starting up.
Run the health check first. It tells you whether an editor answered and which one:
Confirm the bridge is up and see which editor you reached:
cfa health_check.uproject path, the engine version, the pid, and the port. A "status": "error" means no editor answered.The editor is not open. The bridge lives inside the editor process, so nothing is listening until your project is open. Open it and re-run.
The editor is still loading or compiling. On a cold open, shaders and modules compile before the bridge starts accepting connections. Wait for the editor to settle and try again.
The plugin is not enabled in this project. Check Edit, Plugins, search CodeFizz. If it is off, enable it and restart the editor.
The plugin failed to load at startup. If the editor showed an error about the module not loading, the bridge never started. See plugin failed to load (GetLastError 126).
See what is installed where and whether it is current:
cfa plugin statusReinstall the newest build for an engine:
cfa install-plugin "E:/Unreal/UE_5.8"health_check succeeds but names a different project than you expected, the bridge is fine and you are simply reaching another editor. See wrong editor targeted.