What you can use now
FlyBrain Robot Bridge uses a hand-designed model without connectome data. Its eight activity groups represent engineering signals, not identified biological neurons. The current MaleCNS backend checks a local dataset path and exits with Not implemented yet; it does not load a graph.
The useful starting point is the synthetic dry-run. The README describes deterministic frames, fixed simulation time steps and an independent synthetic IMU waveform. Terminal output exposes motion, looming, IMU freshness, commands and watchdog state. This lets a reader follow the software's signal path before introducing camera or hardware variables. It is not a robot physics simulation, and its displayed synthetic frequency is not a runtime benchmark.
What our sandbox established
Our run on 2026-10-03 tested commit 966e541 in our sandbox. The recorded container had 3 CPUs and 8 GB RAM and used the Python 3.12 Bookworm image. No new execution was performed for this correction.
Our harness stores each step's success flag, exit code, elapsed time and timeout status, alongside parsed test counts and log tails. Install, build and test each returned exit code zero without a recorded timeout. The attached durations are 39 seconds for installation, 7 seconds for the build step and 10 seconds for the test step. A zero exit code establishes the recorded command outcome; it does not establish that a deployment or physical workload ran. The supplied build tail is empty and does not identify a hardware build.
The stored parser summary and raw pytest footer both report 26 passed. The footer's repeated appearance in the attached tail is not another suite to add to the total. These records do not establish exhaustive unique coverage or test quality.
Pip-audit recorded 0 advisories. Scan coverage is unknown: the record supplies a packages value of 0 but no scannedPackages value establishing coverage. This result is not a security assessment.
The MrKeyoor testing methodology explains the publisher's approach to command outcomes and measurement limits. That page was fetched on 2026-10-31; it does not establish which methodology revision governed our earlier October run.
What remains between the demo and a robot
The architecture describes optical flow feeding a model and then a decoder that limits, smooths and optionally inverts motor commands. Looming can trigger reverse motion, but the README calls it a camera-sensitive heuristic rather than collision avoidance.
The firmware is deliberately disarmed until board-specific servo and IMU hooks are implemented. The README says it has not been compiled or tested on a board and that no hardware test has been performed. Our sandbox results do not fill that gap: webcam behavior, the physical UDP link and actual motion were not established by the supplied run.
The decoder returns zero when read after 500 ms without an update, but it cannot stop hardware if Python hangs. Normal shutdown sends a best-effort stop packet. UDP delivery is not guaranteed, and the protocol has no authentication. Before enabling motion, follow the project's instructions to implement an independent receiver watchdog, use a motor power cutoff and calibrate with the robot lifted off the ground.
Which alternative answers your question?
ROS 2 provides libraries and tools for building robot applications. Its repository describes drivers, algorithms and developer tools. Consider it for the surrounding robot application architecture; the supplied extract does not demonstrate integration with FlyBrain Robot Bridge or make it a replacement for the mock model.
DOOMFLY connects a fly-connectome simulation to a Doom-engine arena. It is an alternative experiment for readers interested in connectome-driven game control, rather than a replacement for physical robot firmware. Its README says that the current v6 candidate failed its visual, conditioning and survival validation gates. Changing weights or running longer rounds is not evidence of learned survival.
How to read the scores
These are editorial assessments, not benchmarks. The rubric is 1 for substantial obstacles or missing fundamentals, 2 for limited evidence or unfinished core paths, 3 for a usable baseline with material gaps, 4 for strong evidence within a stated scope, and 5 for thorough support of that dimension. Dimensions without sufficient evidence remain unassessed.
Setup ease is 4 for the local software path: our recorded installation and software checks succeeded, while hardware setup remains manual. Documentation is 5 for its explicit explanation of the model, protocol, watchdog limits and integration stub; this does not rate the implementation as complete. Community support is unassessed because the supplied primary evidence does not establish support responsiveness or sustained contributor activity. Maturity is 2 because the mock demonstration exists while the connectome and physical hardware paths remain unfinished.
Start by inspecting the synthetic outputs and decoder behavior. If your project depends on real neural dynamics or physical motion, define and validate that missing path before adopting the bridge.

