![](data:image/svg+xml,<svg display="block" id="1524428453" role="presentation" viewBox="0 0 32 32" xmlns="http://www.w3.org/2000/svg"><path d="M 15.987 0.494 C 16.832 0.005 17.837 -0.127 18.78 0.126 C 19.723 0.379 20.527 0.996 21.014 1.843 C 22.03 3.604 21.427 5.856 19.667 6.875 C 17.441 8.161 13.549 6.583 11 8.056 C 10.96 8.078 10.936 8.121 10.938 8.166 C 10.94 8.212 10.968 8.252 11.01 8.271 C 12.385 8.901 20.21 12.489 20.271 12.505 C 21.861 12.93 22.976 14.36 23.001 16.006 C 23.027 17.652 21.957 19.116 20.381 19.591 C 18.112 20.519 14.511 19.191 12.104 20.582 C 9.554 22.056 8.974 26.219 6.749 27.506 C 5.904 27.994 4.899 28.126 3.956 27.873 C 3.013 27.62 2.21 27.003 1.723 26.157 C 0.707 24.395 1.309 22.143 3.069 21.125 C 5.619 19.651 9.187 21.417 11.736 19.944 C 12.009 19.786 11.955 19.387 11.666 19.262 L 2.727 15.427 C 1.301 15.043 0.242 13.845 0.036 12.383 C -0.17 10.921 0.517 9.477 1.781 8.714 C 1.841 8.674 1.902 8.636 1.965 8.599 C 4.515 7.126 8.083 8.892 10.632 7.418 C 13.182 5.944 13.438 1.968 15.987 0.494 Z" fill="rgb(255, 255, 255)" height="27.99884804175999px" id="vO3ypKHss" transform="translate(4 2)" width="23.00194688367269px"/></svg>)
Debug
Explore your fleet. Understand what went wrong.
Ask questions about your devices, running models, and hardware. Investigate failed tasks, low model confidence, and motor issues—all in one conversation.
Explore every device and model.
Find out what each machine is running, how it’s performing, and where problems appear. Narrow your investigation by device, model version, hardware, or task.
Follow the investigation.
Start with a failed task and ask what changed. Explore model confidence, sensor inputs, motor responses, and recent updates with suggested follow-up questions.
![](data:image/svg+xml,<svg display="block" role="presentation" viewBox="0 0 32 32" xmlns="http://www.w3.org/2000/svg"><g d="M 0 0 L 24 0 L 24 24 L 0 24 Z M 7.858 12.212 L 10.576 13.469 L 10.228 16.592 L 5.369 22.097 C 2.487 20.245 0.533 17.249 0 13.865 Z M 15.11 15.564 L 18.745 21.827 C 16.728 23.245 14.322 24.004 11.856 24 C 11.04 24 10.227 23.918 9.428 23.754 L 10.228 16.591 L 12.286 14.259 Z M 23.462 8.929 C 23.72 9.909 23.858 10.938 23.858 11.999 C 23.858 14.469 23.112 16.764 21.833 18.673 L 15.11 15.564 L 13.533 12.848 L 15.515 10.602 Z M 12.08 0 C 15.56 0.061 18.841 1.633 21.069 4.307 L 15.514 10.602 L 12.587 11.218 L 11.111 8.674 Z M 11.111 8.675 L 10.785 11.596 L 7.859 12.212 L 0.309 8.721 C 1.26 5.386 3.603 2.623 6.739 1.141 Z" fill="transparent" height="24.000015083383285px" id="kqrJ4gA6m" transform="translate(4 4)" width="24px"><path d="M 0 0 L 24 0 L 24 24 L 0 24 Z" fill="transparent" height="24px" id="DuhZHebCq" width="24px"/><path d="M 7.858 0 L 10.576 1.257 L 10.228 4.38 L 5.369 9.885 C 2.487 8.033 0.533 5.037 0 1.653 Z" fill="rgb(21, 227, 255)" height="9.885000000000002px" id="JJEAJseCd" transform="translate(0 12.212)" width="10.576px"/><path d="M 5.682 1.305 L 9.317 7.568 C 7.3 8.986 4.894 9.745 2.428 9.741 C 1.612 9.741 0.799 9.659 0 9.495 L 0.8 2.332 L 2.858 0 Z" fill="rgb(52, 141, 252)" height="9.74101525885936px" id="rQgESjQWF" transform="translate(9.428 14.259)" width="9.316999999999997px"/><path d="M 9.929 0 C 10.187 0.98 10.325 2.009 10.325 3.07 C 10.325 5.54 9.579 7.835 8.3 9.744 L 1.577 6.635 L 0 3.919 L 1.982 1.673 Z" fill="rgb(253, 72, 115)" height="9.744px" id="oy2ZO1kid" transform="translate(13.533 8.929)" width="10.325px"/><path d="M 0.969 0 C 4.449 0.061 7.73 1.633 9.958 4.307 L 4.403 10.602 L 1.476 11.218 L 0 8.674 Z" fill="rgb(255, 199, 0)" height="11.218px" id="Am8Bk4LNT" transform="translate(11.111 0)" width="9.957999999999998px"/><path d="M 10.802 7.534 L 10.476 10.455 L 7.55 11.071 L 0 7.58 C 0.951 4.245 3.294 1.482 6.43 0 Z" fill="rgb(0, 231, 185)" height="11.071px" id="gQ5F0q2E4" transform="translate(0.309 1.141)" width="10.802px"/></g></svg>)
See the evidence behind the answer.
Open the model traces, device logs, and hardware signals behind each finding. See what happened and investigate the possible causes.
From a fleet-wide question
to a specific machine, model, or motor.
Ask in plain language
Ask which devices are struggling, what models they run, or what changed after an update.
Connect models and hardware
Investigate how model decisions relate to camera inputs, sensor readings, motor responses, and software events.
Explore what changed
Focus on a failed task, a recent deployment, or a specific time window to reconstruct what happened.
Inspect running models
Explore model versions, confidence signals, inputs, outputs, and inference latency on each device.
Compare across your fleet
Compare affected machines with similar devices running the same task to uncover differences worth investigating.
Debug remotely
Inspect device logs, system state, and model traces without being next to the machine.
Your intelligence fleet,
finally connected
Connect
© 2026 Physicalfleet. All rights reserved.