Run v5x doctor to check Bun, platform support, installed toolchains, and visible serial ports before troubleshooting a specific project or hardware command. Use v5x doctor --json when sharing details for support.
Run the command from the directory containing project.pros, the vexide Cargo.toml, or the VEXcode vex Make files. Alternatively, pass that directory as path.
Install the toolchain and check that Cargo, PROS, Python, or Make is on your PATH.
Turn on the brain, reconnect its USB cable, close competing serial applications, and verify operating-system permissions.
Pass --port <path-or-id> to hardware commands such as upload, run, devices, programs, dir, and screenshot. Set V5X_PORT to reuse the same selector across commands.
Build the project first. When using --no-build, pass the intended .bin file with --file.
Use a terminal implementing the Kitty graphics protocol. The command writes graphics escape sequences rather than an image file.
CLI troubleshooting - v5x